www.livescore.cz speed test — 20 Oct 2026

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

https://www.livescore.cz/

20 October 2026 at 12:52 UTC · Free test · report pt_defe94112fb2
Grade
B
83/100
Performance80/100
Structure88/100

12 audit(s) passed, 4 need work

First byte (TTFB)368 msmeasured from this server
Fully loaded5.53 sfirst byte + slowest asset
Requests13document + assets
Page weight144.2 KBcompressed transfer
HTML document11.6 KBbr
ProtocolHTTP/3cloudflare
Third-party14.2 KBother hosts

Where the first byte went

  • DNS lookup 76 ms 21%
  • TCP connect 24 ms 7%
  • Server wait 268 ms 73%

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 62% of 4,999 pages tested here368 ms against a median of 449 ms
Page weightlighter than 84% of 4,999 pages tested here144.2 KB against a median of 650.5 KB
Fully loadedslower than 92% of 4,999 pages tested here5.53 s against a median of 1.84 s
Requestssends fewer requests than 85% of 4,999 pages tested here13 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 368 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 144.2 KB over 13 request(s), which is lean. 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 1.47 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 17 ms in total, which is not enough to feel.

Fix first: Render-blocking resources - 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.

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.livescore.cz
Mobile 390 × 844 · 75.7 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.47 sgood is under 2.5 s
Cumulative layout shift0.112under 0.1 is stable
Total blocking time17 mslong tasks during load
First contentful paint1.47 sfirst content on screen
Browser page weight1.07 MB55 request(s), scripts included
Failed requests2blocked or unreachable
Largest contentful paint1.47 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 time17 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 4 requests
118.2 KB 82%
Images 6 requests
11.8 KB 8%
Css 1 request
2.4 KB 2%
Other 1 request
189 B 0%

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

Top issues

Render-blocking resources

high impact

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

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

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

JAVASCRIPTwww.livescore.cz/res/_fs/build-mobi/initBannerHandlerLi…
5.16 s
JAVASCRIPTwww.livescore.cz/res/_fs/build-mobi/programaticStrip.Dp…
5.16 s
JAVASCRIPTwww.livescore.cz/res/_fs/build-mobi/oddsGeoRestrictions…
5.16 s
CSSstatic.flashscore.com/x/css/layout_317_1477000000.css
5.16 s
OTHERwww.livescore.cz/manifest/1/
5.16 s
JAVASCRIPTwww.livescore.cz/res/_fs/build-mobi/mobiVendor.PSsNU1f.js
551 ms
IMAGESstatic.flashscore.com/res/_fs/image/4_favicons/_mobi/favicon…
533 ms
IMAGESstatic.flashscore.com/res/_mobi/image/logo/livescore.png
508 ms
IMAGESstatic.flashscore.com/res/_fs/image/4_favicons/_mobi/touch-i…
507 ms
IMAGESstatic.flashscore.com/res/_fs/image/4_favicons/_fs/favicon.ico
507 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://www.livescore.cz/res/_fs/build-mobi/initBannerHandlerLite.Cate2TR.jsjavascript2005.16 s11.5 KB
https://www.livescore.cz/res/_fs/build-mobi/programaticStrip.DpNvTfr.jsjavascript2005.16 s933 B
https://www.livescore.cz/res/_fs/build-mobi/oddsGeoRestrictions.B5i1sPg.jsjavascript2005.16 s298 B
https://static.flashscore.com/x/css/layout_317_1477000000.css 3rd partycss2005.16 s2.4 KB
https://www.livescore.cz/manifest/1/?v=7other2005.16 s189 B
https://www.livescore.cz/res/_fs/build-mobi/mobiVendor.PSsNU1f.jsjavascript200551 ms105.5 KB
https://static.flashscore.com/res/_fs/image/4_favicons/_mobi/favicon-32x32.png?v=8 3rd partyimages200533 ms1.2 KB
https://static.flashscore.com/res/_mobi/image/logo/livescore.png?v=2 3rd partyimages200508 ms1.2 KB
https://static.flashscore.com/res/_fs/image/4_favicons/_mobi/touch-icon-180x180.png?v=8 3rd partyimages200507 ms6.5 KB
https://static.flashscore.com/res/_fs/image/4_favicons/_fs/favicon.ico?v=8 3rd partyimages200507 ms2.1 KB
https://static.flashscore.com/res/_fs/image/4_favicons/_mobi/favicon-16x16.png?v=8 3rd partyimages200507 ms810 B
https://static.flashscore.com/res/image/blank.gif 3rd partyimages200507 ms43 B
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.