C — https://arcgis.com | BeaverCheck Audit

Site Health

Score: 70 / 100

Based on 8 categories, 0 sections

Room to improve — your 16.1s load time is above Google's 2.5s 'Good' threshold.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Solid infrastructure — fast server responses across the board.

Several regulatory requirements are not yet met.

Good content signals with minor gaps.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Amazon Route 53 sites average 72

At average

Better than 12% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Google Search Console sites average 73

At average

Better than 14% of Google Search Console sites See full Google Search Console benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

Page weighs 13.1 MB (4.7 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget

No <main> landmark found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Landmark Structure

177 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Farcgis.com)](https://beavercheck.com/results/06ab2730-551b-4f7f-910a-0aeadc3168ee)

HTML

<a href="https://beavercheck.com/results/06ab2730-551b-4f7f-910a-0aeadc3168ee"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Farcgis.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Farcgis.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 16.1s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.

Your LCP is 16.1s — fixing the 2 performance criticals could bring it under Google's 2.5s 'Good' threshold.

1 accessibility issue excludes users who rely on assistive technology.

Conversion Barriers

2 critical 6 warning

8 barrier(s) likely increasing bounce by ~30%.

Speed (2)

Page takes 16.1s to load

+12% bounce

Users abandon at ~3s — you're 13.6s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Page feels frozen for 838ms

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (1)

Viewport disables user zoom

+2% bounce

Visitors with low vision can't read the page — and some jurisdictions treat this as a legal risk

Fix: Remove user-scalable=no; drop maximum-scale if it's below 2

Content (2)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

$650 investment → $1.19/month returns + USD 157,500 risk avoided

Payback period: > 2 years First-year ROI: -98%

Investment

$650

6h · 5 findings

Monthly returns

$1.19 /mo

~$14 / year

Bandwidth savings $1.19

Regulatory risk avoided

USD 157,500

if kept compliant

ADA Title III USD 150,000
CCPA/CPRA USD 7,500

$100 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

$650

6.5 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins

$100 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,126 / month at risk

~$157,514 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA

No privacy policy link detected
CCPA/CPRA: USD 2,500 – USD 7,500
Trackers detected but no cookie policy found
CCPA/CPRA: USD 2,500 – USD 7,500
Trackers detected but no privacy policy found
CCPA/CPRA: USD 2,500 – USD 7,500

+5 more

Bandwidth Waste

$1.19 /mo

14869.3 MB/mo × 0.080 USD/GB

Optimize transfer: save ~1.5 MB per page load
Saves $1.19/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 4 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

100

Best Practices

SEO

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

8.91 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

16.13 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

838 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.060

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

12.32 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

23.37 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
/sharing/rest/content/items/3ebb42be9ba34ab0971a9b676dba2...	300.0 s	288.3 KiB
/sharing/rest/content/items/ba4a93e7ca714f70bab324e077cff...	300.0 s	287.5 KiB
/sharing/rest/content/items/2b25499dbfeb41d0bb734624e4d66...	300.0 s	280.1 KiB
/sharing/rest/content/items/dece90af1a0242dcbf0ca36d30276...	300.0 s	273.7 KiB
/sharing/rest/content/items/2c6661e50dc34b0cb31a2b3d6ad5e...	300.0 s	235.3 KiB
/sharing/rest/content/items/ff44f34d23ba466cb7da6b1707bcf...	300.0 s	198.7 KiB
/sharing/rest/content/items/0d19f3b462234657b4174b0153576...	300.0 s	170.5 KiB
www.arcgis.com/home/js/arcgisonline/img/homepage_background-public.png	1800.0 s	175.6 KiB
/sharing/rest/content/items/4cdbe664bc2049378d3a17c923f07...	300.0 s	145.8 KiB
/sharing/rest/content/items/80eb92ffc89b4086abe8cedd58ab1...	300.0 s	145.4 KiB
/sharing/rest/content/items/315e803e85b2420eb863a85d5aee7...	300.0 s	120.0 KiB
/sharing/rest/content/items/02a091c09e024481acabd49f47a90...	300.0 s	10.1 KiB
www.arcgis.com/home/js/arcgisonline/img/homepage_try-arcgis-online.png	1800.0 s	8.9 KiB
www.arcgis.com/home/js/arcgisonline/img/homepage_create-maps.png	1800.0 s	8.8 KiB
www.arcgis.com/home/js/arcgisonline/config.js	1800.0 s	6.8 KiB
www.arcgis.com/home/js/arcgisonline/img/homepage_share-and-collaborate.png	1800.0 s	6.8 KiB
/home/js/arcgisonline/img/homepage_discover-patterns-and-...	1800.0 s	5.2 KiB
www.arcgis.com/home/js/arcgisonline/img/arcgis-online-64.svg	1800.0 s	954 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-DIV

nodeLabel: ArcGIS Online

path: 1,HTML,1,BODY,0,DIV,0,DIV,2,DIV,0,DIV,0,DIV,0,DIV

selector: div.flex > div.home-page > div.home-page__content > div.home-page__header

snippet: <div class="home-page__header home-page__header-background-color--dark-gs home-page__h…" style="background-image: url("https://www.arcgis.com/home/js/arcgisonline/img/hom…");">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
cdn-a.arcgis.com/cdn/1C31855/js/esri-global-nav/dist/esri-global-nav.css	14.5 KiB	909 ms
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-app-components/arcgis-app/arcgis-app.css	1.3 KiB
cdn-a.arcgis.com/cdn/1C31855/js/calcite-components/cdn/main.css	3.4 KiB
cdn-a.arcgis.com/cdn/1C31855/js/calcite-fonts/fonts.css	1.2 KiB
www.arcgis.com/home/js/arcgisonline/config.js	6.8 KiB

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
/cdn/1C31855/js/calcite-fonts/fonts/09ab0626-bb45-4650-ac...	5.0 ms
/cdn/1C31855/js/calcite-fonts/fonts/0c8a5d21-8a14-4451-81...	5.0 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img `div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img`	/sharing/rest/content/items/3ebb42be9ba34ab0971a9b676dba2...	287.6 KiB	270.3 KiB
div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img `div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img`	/sharing/rest/content/items/ba4a93e7ca714f70bab324e077cff...	286.8 KiB	269.5 KiB
div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img `div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img`	/sharing/rest/content/items/2b25499dbfeb41d0bb734624e4d66...	279.4 KiB	262.1 KiB
div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img `div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img`	/sharing/rest/content/items/dece90af1a0242dcbf0ca36d30276...	273.0 KiB	255.7 KiB
div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img `div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img`	/sharing/rest/content/items/2c6661e50dc34b0cb31a2b3d6ad5e...	234.7 KiB	217.4 KiB
div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img `div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img`	/sharing/rest/content/items/ff44f34d23ba466cb7da6b1707bcf...	198.1 KiB	180.8 KiB
div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img `div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img`	/sharing/rest/content/items/0d19f3b462234657b4174b0153576...	170.0 KiB	152.6 KiB
div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img `div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img`	/sharing/rest/content/items/4cdbe664bc2049378d3a17c923f07...	145.3 KiB	128.0 KiB
div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img `div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img`	/sharing/rest/content/items/80eb92ffc89b4086abe8cedd58ab1...	144.9 KiB	127.6 KiB
div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img `div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img`	/sharing/rest/content/items/315e803e85b2420eb863a85d5aee7...	119.5 KiB	102.2 KiB
div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img `div.home-page__constraint-wrapper > div.flex > div.home-page__gallery-tile > div.home-page__gallery-tile-img`	/sharing/rest/content/items/02a091c09e024481acabd49f47a90...	9.8 KiB	5.4 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.5 s

URL	Time Spent
arcgis.com/	775 ms
www.arcgis.com/	771 ms
www.arcgis.com/home/index.html	0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 6.2 s 1.2 MiB

URL	Transfer Size	Est Savings
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-online-4.x/build/1565.js	534.2 KiB	355.2 KiB
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-online-4.x/build/42436.js	308.4 KiB	237.0 KiB
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-online-4.x/build/70362.js	272.3 KiB	156.9 KiB
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-online-4.x/build/47313.js	145.7 KiB	117.0 KiB
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-online-4.x/build/882.js	137.8 KiB	89.6 KiB
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-online-4.x/build/3050.js	63.5 KiB	49.8 KiB
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-online-4.x/build/87032.js	52.0 KiB	41.8 KiB
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-online-4.x/build/991.js	50.3 KiB	40.1 KiB
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-online-4.x/build/47209.js	29.4 KiB	28.2 KiB
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-online-4.x/build/88395.js	29.2 KiB	27.7 KiB
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-online-4.x/build/7315.js	38.4 KiB	23.5 KiB
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-online-4.x/build/64513.js	24.6 KiB	22.9 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-online-4.x/build/70362.js	2.6 s	2.5 s	8.8 ms
Unattributable	2.2 s	298 ms	0.0 ms
cdn-a.arcgis.com/cdn/1C31855/js/calcite-components/cdn/G7AHLVJ5.js	525 ms	434 ms	0.5 ms
www.arcgis.com/home/index.html	393 ms	3.9 ms	0.6 ms
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-online-4.x/build/42436.js	371 ms	254 ms	8.2 ms
cdn-a.arcgis.com/cdn/1C31855/js/calcite-components/cdn/M6MCECQO.js	181 ms	150 ms	0.2 ms
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-online-4.x/build/25611.js	156 ms	68 ms	1.8 ms
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-app-components/arcgis-app/p-0b9f6f3d.js	126 ms	110 ms	0.3 ms
cdn-a.arcgis.com/cdn/1C31855/js/calcite-components/cdn/TYCGDLK6.js	75 ms	69 ms	0.2 ms
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-online-4.x/build/7315.js	61 ms	0.2 ms	0.9 ms
cdn-a.arcgis.com/cdn/1C31855/js/calcite-components/cdn/SM2W3ZFF.js	60 ms	56 ms	0.1 ms
cdn-a.arcgis.com/cdn/1C31855/js/calcite-components/cdn/6V5DRX2T.js	59 ms	28 ms	0.3 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	4.2 s
Other	2.3 s
Style & Layout	459 ms
Garbage Collection	197 ms
Script Parsing & Compilation	88 ms
Parse HTML & CSS	60 ms
Rendering	53 ms

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 3.0 KiB

URL	Transfer Size	Est Savings
*, ::before, ::after { --tw-border-spacing-x: 0; --tw-border-spacing-y: 0; --tw-translate-x: …	13.4 KiB	3.0 KiB

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 43.9 KiB

URL	Transfer Size	Est Savings
/* color selection styles */ .home-page-overlay__left-panel .ob-colors .ob-colors { position: rel… } …	18.5 KiB	18.5 KiB
cdn-a.arcgis.com/cdn/1C31855/js/esri-global-nav/dist/esri-global-nav.css	14.1 KiB	13.1 KiB
*, ::before, ::after { --tw-border-spacing-x: 0; --tw-border-spacing-y: 0; --tw-translate-x: …	13.4 KiB	12.3 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-online-4.x/build/1565.js	534.9 KiB
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-online-4.x/build/42436.js	308.9 KiB
/sharing/rest/content/items/3ebb42be9ba34ab0971a9b676dba2...	288.3 KiB
/sharing/rest/content/items/ba4a93e7ca714f70bab324e077cff...	287.5 KiB
/sharing/rest/content/items/2b25499dbfeb41d0bb734624e4d66...	280.1 KiB
/sharing/rest/content/items/dece90af1a0242dcbf0ca36d30276...	273.7 KiB
cdn-a.arcgis.com/cdn/1C31855/js/arcgis-online-4.x/build/70362.js	272.9 KiB
/sharing/rest/content/items/2c6661e50dc34b0cb31a2b3d6ad5e...	235.3 KiB
/sharing/rest/content/items/ff44f34d23ba466cb7da6b1707bcf...	198.7 KiB
www.arcgis.com/home/js/arcgisonline/img/homepage_background-public.png	175.6 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
Home page logo `div.home-page__header > div.flex > div.flex > img.home-page__logo-img`	www.arcgis.com/home/js/arcgisonline/img/arcgis-online-64.svg

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●Avoid long main-thread tasks 14 long tasks found

●Avoid non-composited animations 4 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 0 ms

●Server Backend Latencies 20 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 10 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○User Timing marks and measures

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search `header.js-header-boundary > div.esri-header-wrap > div.esri-header > div.esri-header-inlineSearch`

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Edit home page `body > div.home-page__manager > calcite-dialog.home-page__manager-modal`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

100

Best Practices

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

100

SEO

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

648 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.30 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

36 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

753 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.30 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
www.arcgis.com/js/app/build/69fae41471ed9dcab967.jpg	1800.0 s	256.0 KiB
www.arcgis.com/js/app/build/15651.js	1800.0 s	204.9 KiB
www.arcgis.com/js/app/build/main.js	1800.0 s	55.6 KiB
www.arcgis.com/js/app/build/69a9213c8f93653cd59d.woff2	1800.0 s	32.3 KiB
www.arcgis.com/js/app/build/da35b5dac0012fb9049d.woff2	1800.0 s	32.2 KiB
www.arcgis.com/graphics/arcgis-online-icon.png	1800.0 s	8.2 KiB
www.arcgis.com/js/app/build/72152.js	1800.0 s	7.2 KiB
www.arcgis.com/js/app/build/82162.js	1800.0 s	7.1 KiB
www.arcgis.com/js/app/build/43305.js	1800.0 s	6.0 KiB
www.arcgis.com/js/app/build/66801.js	1800.0 s	5.9 KiB
www.arcgis.com/js/app/build/11547.js	1800.0 s	4.0 KiB
www.arcgis.com/js/app/build/79000.js	1800.0 s	3.6 KiB
www.arcgis.com/js/app/build/20307.js	1800.0 s	3.0 KiB
www.arcgis.com/js/app/build/19393.js	1800.0 s	2.5 KiB
www.arcgis.com/js/app/build/81896.js	1800.0 s	1.3 KiB
www.arcgis.com/js/app/build/runtime.js	1800.0 s	1.2 KiB
www.arcgis.com/js/app/config.js	1800.0 s	645 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
www.arcgis.com/js/app/build/da35b5dac0012fb9049d.woff2	5.0 ms
www.arcgis.com/js/app/build/69a9213c8f93653cd59d.woff2	5.0 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
div.row > div.arcgis-online-banner-main-text > div.intro-transition > img.arcgis-online-logo `div.row > div.arcgis-online-banner-main-text > div.intro-transition > img.arcgis-online-logo`	www.arcgis.com/graphics/arcgis-online-icon.png	8.3 KiB	6.9 KiB

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
www.arcgis.com/js/app/config.js	645 B

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 80 ms 107.7 KiB

URL	Transfer Size	Est Savings
www.arcgis.com/js/app/build/15651.js	204.4 KiB	107.7 KiB

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 23.7 KiB

URL	Transfer Size	Est Savings
/** * Global Nav - A centralized component for Esri's global navigation * @version v1.5.1 * @lin…	24.8 KiB	23.7 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 416 ms

URL	Time Spent
arcgis.com/	211 ms
www.arcgis.com/	205 ms
www.arcgis.com/index.html	0.0 ms

●Max Potential First Input Delay 120 ms

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 1.3 s

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 648 KiB

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.5 s

●Avoid long main-thread tasks 1 long task found

●Avoid non-composited animations 5 animated elements found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 0 ms

●Server Backend Latencies 20 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 10 ms

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid large layout shifts

Accessibility

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search Site `header.js-header-boundary > div.esri-header-wrap > div.esri-header > div.esri-header-inlineSearch`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta `head > meta`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
www.arcgis.com/js/app/build/main.js	`[object a]`
www.arcgis.com/js/app/build/20307.js line 1, col 313	`%ccalcite background: #007AC2; color: #fff; border-radius: 4px; padding: 2px 4px; arrow-right (s) icon failed to load`
/npm/@esri/calcite-components@5.0.0-next.21/dist/calcite/...	`Failed to load resource: the server responded with a status of 404 ()`
/npm/@esri/calcite-components@5.0.0-next.21/dist/calcite/...	`Failed to load resource: the server responded with a status of 404 ()`
www.arcgis.com/js/app/build/15651.js line 1, col 787350	`TypeError: Cannot redefine property: version at Object.defineProperty (<anonymous>) at https://www.arcgis.com/js/app/build/15651.js:2:787351`

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
www.arcgis.com/js/app/build/15651.js

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

100

SEO

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://arcgis.com

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (2)

Usability (1)

Content (2)

Navigation (1)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Best practices

Best Practices

General

SEO

Keyboard Shortcuts