www.wetteronline.de speed test — 20 Oct 2026

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

https://www.wetteronline.de/

20 October 2026 at 12:49 UTC · Free test · report pt_4ce48327b7c7

Re-test this page Test your own site

Grade

87/100

Performance92/100

Structure79/100

11 audit(s) passed, 5 need work

First byte (TTFB)292 msmeasured from this server

Fully loaded3.01 sfirst byte + slowest asset

Requests26document + assets

Page weight613.2 KBcompressed transfer

HTML document65.3 KBbr

ProtocolHTTP/3CloudFront

Third-party393.6 KBother hosts

Where the first byte went

DNS lookup 46 ms 16%
TCP connect 1 ms 0%
Server wait 245 ms 84%

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

Page weightlighter than 52% of 4,999 pages tested here613.2 KB against a median of 650.5 KB

Fully loadedslower than 82% of 4,999 pages tested here3.01 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 arrived in 292 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 613.2 KB over 26 request(s). Images files are 45% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
64% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.

Fix first: Compress text responses - Turn on brotli (preferred) or gzip for text/css, javascript and text/html in the web server. This is the cheapest win available on almost any site.

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.

No screenshot for this report.

The headless browser did not capture this page when the test ran, so only the server measurements are shown.

Page weight by type

What the page is made of

Images 18 requests

276.6 KB 45%

Javascript 1 request

170.9 KB 28%

Html 6 requests

100.4 KB 16%

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

Top issues

Compress text responses

high impact

2 text response(s) of 10 KB or more are sent uncompressed, and the document itself is not compressed. That is 89.5 KB of compressible text.

Fix: Turn on brotli (preferred) or gzip for text/css, javascript and text/html in the web server. This is the cheapest win available on almost any site.

Render-blocking resources

high impact

13 render-blocking resource(s) in the document head (7 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.

Third-party weight

medium impact

3 third-party host(s) serve 393.6 KB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

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.