www.immutable.com speed test — 20 Oct 2026

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

https://www.immutable.com/

20 October 2026 at 13:53 UTC · Free test · report pt_787f77b7d4bf

Re-test this page Test your own site

Grade

94/100

Performance96/100

Structure91/100

13 audit(s) passed, 3 need work

First byte (TTFB)195 msmeasured from this server

Fully loaded2.56 sfirst byte + slowest asset

Requests26document + assets

Page weight427.4 KBcompressed transfer

HTML document67.9 KBgzip

ProtocolHTTP/3server not sent

Where the first byte went

DNS lookup 58 ms 30%
TCP connect 31 ms 16%
Server wait 107 ms 55%

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 here195 ms against a median of 449 ms

Page weightlighter than 63% of 4,999 pages tested here427.4 KB against a median of 650.5 KB

Fully loadedslower than 75% of 4,999 pages tested here2.56 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 195 ms, which is fast: almost all of the wait is the page itself, not the host.
The page transfers 427.4 KB over 26 request(s). Images files are 84% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
The largest element painted at 464 ms, inside the 2.5 s Google calls good.
The main thread was blocked for 391 ms, so taps and scrolling wait while scripts run.

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.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Mobile screenshot of www.immutable.com — **Mobile** 390 × 844 · 149.7 KB · page is 6000 px tall

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 paint464 msgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking time391 mslong tasks during load

First contentful paint368 msfirst content on screen

Browser page weight2.00 MB83 request(s), scripts included

Failed requests3blocked or unreachable

Largest contentful paint464 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking time391 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

359.5 KB 84%

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

Top issues

Render-blocking resources

high impact

3 render-blocking resource(s) in the document head (1 script(s), 2 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.

Avoid extra redirects

medium impact

1 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.

Strict-Transport-Security

low impact

HSTS is not set, so the first visit on a hostile network can still be downgraded to HTTP.

Fix: Send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains once every subdomain is HTTPS.