www.krone.at speed test — 20 Oct 2026

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

https://www.krone.at/

20 October 2026 at 14:18 UTC · Free test · report pt_73df4cc40142

Re-test this page Test your own site

Grade

69/100

Performance69/100

Structure70/100

11 audit(s) passed, 5 need work

First byte (TTFB)1.23 smeasured from this server

Fully loaded2.34 sfirst byte + slowest asset

Requests26document + assets

Page weight210.6 KBcompressed transfer

HTML document106.9 KBgzip

ProtocolHTTP/3server not sent

Third-party60.9 KBother hosts

Where the first byte went

DNS lookup 85 ms 7%
TCP connect 11 ms 1%
Server wait 1.14 s 92%

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

Page weightlighter than 79% of 4,999 pages tested here210.6 KB against a median of 650.5 KB

Fully loadedslower than 69% of 4,999 pages tested here2.34 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.23 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 210.6 KB over 26 request(s). Images files are 49% 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.
29% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element painted at 1.78 s, inside the 2.5 s Google calls good.
Layout shift is 0.112 (good is under 0.1): something without a reserved size is loading late - an image, an ad, or a font swap.
The main thread was blocked for 358 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.krone.at — **Mobile** 390 × 844 · 207.4 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.78 sgood is under 2.5 s

Cumulative layout shift0.112under 0.1 is stable

Total blocking time358 mslong tasks during load

First contentful paint756 msfirst content on screen

Browser page weight7.05 MB311 request(s), scripts included

Largest contentful paint1.78 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.112

Needs improvementgood under 0.1, poor over 0.25

Total blocking time358 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

103.7 KB 49%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1231 ms. Of that, 1135 ms was the server thinking and 96 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

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

Cache static assets

medium impact

25 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

HTML document size

medium impact

The document transfers 106.9 KB. A bloated document delays every other request, because nothing else can start until it is parsed.

Fix: Paginate long listings, move repeated markup into a template, and stop inlining large data URIs into the HTML.

Avoid extra redirects

medium impact

2 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.

Waterfall

Slowest requests

IMAGESimgl.krone.at/scaled/4341757/ve4620e/630x356

1.11 s

IMAGESimgl.krone.at/2023/04/852cafd22f5e870be2a2b264342c2c…

1.03 s