www.esri.com/en-us/home speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 14:50 UTC. Grade A (90/100), with the screenshots, the timings and the fixes that matter.

https://www.esri.com/en-us/home

20 October 2026 at 14:50 UTC · Free test · report pt_9101ba1e5c0d

Re-test this page Test your own site

Grade

90/100

Performance100/100

Structure76/100

11 audit(s) passed, 5 need work

First byte (TTFB)196 msmeasured from this server

Fully loaded1.46 sfirst byte + slowest asset

Requests26document + assets

Page weight759.5 KBcompressed transfer

HTML document11.7 KBgzip

ProtocolHTTP/3server not sent

Third-party462.8 KBother hosts

Where the first byte went

DNS lookup 77 ms 39%
TCP connect 26 ms 13%
Server wait 93 ms 47%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First bytefaster than 93% of 4,999 pages tested here196 ms against a median of 449 ms

Page weightheavier than 55% of 4,999 pages tested here759.5 KB against a median of 650.3 KB

Fully loadedfaster than 73% of 4,999 pages tested here1.46 s against a median of 1.84 s

Requestssends more requests than 100% of 4,999 pages tested here26 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

The server answered in 196 ms, which is fast: almost all of the wait is the page itself, not the host.
The page transfers 759.5 KB over 26 request(s). Javascript files are 61% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
61% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element painted at 2.00 s, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.004), so nothing jumps under the reader's cursor.
The main thread was blocked for 57 ms in total, which is not enough to feel.

Fix first: Render-blocking resources - Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint2.00 sgood is under 2.5 s

Cumulative layout shift0.004under 0.1 is stable

Total blocking time57 mslong tasks during load

First contentful paint2.00 sfirst content on screen

Browser page weight11.94 MB243 request(s), scripts included

Failed requests2blocked or unreachable

Largest contentful paint2.00 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.004

Goodgood under 0.1, poor over 0.25

Total blocking time57 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 4 requests

461.8 KB 61%

Images 6 requests

232.9 KB 31%

Html 15 requests

53.2 KB 7%

Transfer size, compressed as sent. 26 request(s) in total, 759.5 KB across all of them.

Top issues

Render-blocking resources

high impact

9 render-blocking resource(s) in the document head (4 script(s), 5 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Cache static assets

medium impact

7 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

Third-party weight

medium impact

4 third-party host(s) serve 462.8 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: launch-EN26af1ee4ef084984926fd80d1cb93835.min.js (284.3 KB)

Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.

Avoid extra redirects

medium impact

2 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

Waterfall

Slowest requests

HTMLwww.esri.com/en-us/home/etc.clientlibs/esri-sites/c…

1.27 s

JAVASCRIPTjs.arcgis.com/calcite-components/1.8.0/calcite.esm.js

1.19 s