www.ilo.org speed test — 20 Oct 2026

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

https://www.ilo.org/

20 October 2026 at 13:21 UTC · Free test · report pt_3e06779868dc

Re-test this page Test your own site

Grade

87/100

Performance86/100

Structure89/100

13 audit(s) passed, 3 need work

First byte (TTFB)645 msmeasured from this server

Fully loaded1.99 sfirst byte + slowest asset

Requests26document + assets

Page weight500.7 KBcompressed transfer

HTML document14.3 KBzstd

ProtocolHTTP/3cloudflare

Where the first byte went

DNS lookup 97 ms 15%
TCP connect 68 ms 11%
Server wait 480 ms 74%

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 byteslower than 66% of 4,999 pages tested here645 ms against a median of 448 ms

Page weightlighter than 58% of 4,999 pages tested here500.7 KB against a median of 650.5 KB

Fully loadedslower than 57% of 4,999 pages tested here1.99 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 first byte took 645 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
The page transfers 500.7 KB over 26 request(s). Images files are 97% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives zstd-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
The largest element painted at 1.36 s, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.002), so nothing jumps under the reader's cursor.
The main thread was blocked for 89 ms in total, which is not enough to feel.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

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.ilo.org — **Mobile** 390 × 844 · 212.2 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 paint1.36 sgood is under 2.5 s

Cumulative layout shift0.002under 0.1 is stable

Total blocking time89 mslong tasks during load

First contentful paint1.34 sfirst content on screen

Browser page weight1.14 MB38 request(s), scripts included

Largest contentful paint1.36 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.002

Goodgood under 0.1, poor over 0.25

Total blocking time89 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 22 requests

485.2 KB 97%

Javascript 3 requests

1.2 KB 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 645 ms. Of that, 480 ms was the server thinking and 165 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

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.