www.windy.com speed test — 20 Oct 2026

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

https://www.windy.com/

20 October 2026 at 13:07 UTC · Free test · report pt_482b0b771060

Re-test this page Test your own site

Grade

91/100

Performance93/100

Structure88/100

12 audit(s) passed, 4 need work

First byte (TTFB)427 msmeasured from this server

Fully loaded1.69 sfirst byte + slowest asset

Requests16document + assets

Page weight503.1 KBcompressed transfer

HTML document2.3 KBbr

ProtocolHTTP/3nginx/1.22.1

Third-party61.4 KBother hosts

Where the first byte went

DNS lookup 99 ms 23%
TCP connect 76 ms 18%
Server wait 252 ms 59%

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 53% of 4,999 pages tested here427 ms against a median of 449 ms

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

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

Requestssends fewer requests than 83% of 4,999 pages tested here16 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 arrived in 427 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 503.1 KB over 16 request(s). Javascript files are 82% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
The largest element painted at 2.37 s, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.
The main thread was blocked for 335 ms, so taps and scrolling wait while scripts run.

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.windy.com — **Mobile** 390 × 844 · 312.9 KB · page is 844 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 paint2.37 sgood is under 2.5 s

Cumulative layout shift0.001under 0.1 is stable

Total blocking time335 mslong tasks during load

First contentful paint592 msfirst content on screen

Browser page weight1.42 MB223 request(s), scripts included

Failed requests293blocked or unreachable

Largest contentful paint2.37 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.001

Goodgood under 0.1, poor over 0.25

Total blocking time335 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 2 requests

411.2 KB 82%

Images 11 requests

72.4 KB 14%

Css 1 request

16.9 KB 3%

Other 1 request

287 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 427 ms. Of that, 252 ms was the server thinking and 175 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.

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: leaflet-gl.js (295.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

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.

Waterfall

Slowest requests

CSSwww.windy.com/v/51.3.2.ind.81aa/index.css

1.27 s

JAVASCRIPTwww.windy.com/v/51.3.2.ind.81aa/index.js

1.26 s

OTHERwww.windy.com/v/51.3.2.ind.81aa/manifest.json

1.26 s

JAVASCRIPTwww.windy.com/v/51.3.2.ind.81aa/leaflet-gl.js

825 ms