openweathermap.org speed test — 20 Oct 2026

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

https://openweathermap.org/

20 October 2026 at 15:08 UTC · Free test · report pt_f13e0d91b240

Re-test this page Test your own site

Grade

87/100

Performance86/100

Structure88/100

13 audit(s) passed, 3 need work

First byte (TTFB)598 msmeasured from this server

Fully loaded2.42 sfirst byte + slowest asset

Requests26document + assets

Page weight235.4 KBcompressed transfer

HTML document23.9 KBgzip

ProtocolHTTP/2server not sent

Where the first byte went

DNS lookup 55 ms 9%
TCP connect 81 ms 14%
Server wait 462 ms 77%

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 63% of 4,999 pages tested here598 ms against a median of 448 ms

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

Fully loadedslower than 71% of 4,999 pages tested here2.42 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 598 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 235.4 KB over 26 request(s). Images files are 90% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives gzip-compressed.
It runs over HTTP/2, so the assets share a connection instead of opening one each.
The largest element painted at 892 ms, 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 32 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 openweathermap.org — **Mobile** 390 × 844 · 113.5 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 paint892 msgood is under 2.5 s

Cumulative layout shift0.002under 0.1 is stable

Total blocking time32 mslong tasks during load

First contentful paint892 msfirst content on screen

Browser page weight4.06 MB96 request(s), scripts included

Largest contentful paint892 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.002

Goodgood under 0.1, poor over 0.25

Total blocking time32 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 16 requests

211.4 KB 90%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 598 ms. Of that, 462 ms was the server thinking and 136 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.

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.