wmo.int speed test — 20 Oct 2026

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

https://wmo.int/

20 October 2026 at 14:45 UTC · Free test · report pt_ebda31856ef6

Re-test this page Test your own site

Grade

63/100

Performance59/100

Structure70/100

12 audit(s) passed, 4 need work

First byte (TTFB)1.78 smeasured from this server

Fully loaded2.94 sfirst byte + slowest asset

Requests26document + assets

Page weight1,017.0 KBcompressed transfer

HTML document24.5 KBgzip

ProtocolHTTP/3nginx

Where the first byte went

DNS lookup 75 ms 4%
TCP connect 45 ms 3%
Server wait 1.66 s 93%

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 96% of 4,999 pages tested here1.78 s against a median of 448 ms

Page weightheavier than 63% of 4,999 pages tested here1,017.0 KB against a median of 650.3 KB

Fully loadedslower than 81% of 4,999 pages tested here2.94 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 1.78 s. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
The page transfers 1,017.0 KB over 26 request(s). Images files are 93% 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 1.46 s, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.016), so nothing jumps under the reader's cursor.
The main thread was blocked for 66 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 wmo.int — **Mobile** 390 × 844 · 256.3 KB · page is 4746 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.46 sgood is under 2.5 s

Cumulative layout shift0.016under 0.1 is stable

Total blocking time66 mslong tasks during load

First contentful paint1.14 sfirst content on screen

Browser page weight1.53 MB58 request(s), scripts included

Largest contentful paint1.46 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.016

Goodgood under 0.1, poor over 0.25

Total blocking time66 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 20 requests

941.5 KB 93%

Javascript 5 requests

51.0 KB 5%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1782 ms. Of that, 1662 ms was the server thinking and 120 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.

Image delivery and format

high impact

1 image(s) over 200 KB and 2 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Render-blocking resources

high impact

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

Total page weight

medium impact

The page transfers 1,017.0 KB across 26 request(s), with the document itself at 24.5 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.