livesportmedia.eu speed test — 20 Oct 2026

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

https://livesportmedia.eu/

20 October 2026 at 14:19 UTC · Free test · report pt_ca77942773a1
Grade
C
79/100
Performance77/100
Structure82/100

12 audit(s) passed, 4 need work

First byte (TTFB)830 msmeasured from this server
Fully loaded2.98 sfirst byte + slowest asset
Requests15document + assets
Page weight437.8 KBcompressed transfer
HTML document11.5 KBbr
ProtocolHTTP/3server not sent
Third-party253.9 KBother hosts

Where the first byte went

  • DNS lookup 238 ms 29%
  • TCP connect 179 ms 22%
  • Server wait 413 ms 50%

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 77% of 4,999 pages tested here830 ms against a median of 448 ms
Page weightlighter than 63% of 4,999 pages tested here437.8 KB against a median of 650.5 KB
Fully loadedslower than 82% of 4,999 pages tested here2.98 s against a median of 1.84 s
Requestssends fewer requests than 83% of 4,999 pages tested here15 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 830 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 437.8 KB over 15 request(s), which is lean. Javascript files are 77% 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.
  • 58% 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.76 s, inside the 2.5 s Google calls good.
  • The main thread was blocked for 78 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 livesportmedia.eu
Mobile 390 × 844 · 31.6 KB · page is 1282 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.76 sgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time78 mslong tasks during load
First contentful paint1.44 sfirst content on screen
Browser page weight1.41 MB47 request(s), scripts included
Largest contentful paint1.76 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time78 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 4 requests
335.0 KB 77%
Fonts 4 requests
83.1 KB 19%
Images 3 requests
4.1 KB 1%
Css 3 requests
4.0 KB 1%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 830 ms. Of that, 413 ms was the server thinking and 417 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

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

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

Third-party weight

medium impact

3 third-party host(s) serve 253.9 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.

Waterfall

Slowest requests

IMAGESlivesportmedia.eu/img/home/intro/line-1-2.svg
2.15 s
FONTSlivesportmedia.eu/fonts/LSDisplay-Variable.woff2
2.02 s
FONTSlivesportmedia.eu/fonts/LivesportFinderLatin-Bold.woff2
1.73 s
FONTSlivesportmedia.eu/fonts/LSDisplay-Variable.woff
1.00 s
IMAGESlivesportmedia.eu/favicon.png
995 ms
CSSlivesportmedia.eu/_nuxt/index.CkvU_VF1.css
942 ms
JAVASCRIPTlivesportmedia.eu/_nuxt/BPO6mJux.js
835 ms
CSSlivesportmedia.eu/_nuxt/index.Dn3H1acL.css
820 ms
IMAGESlivesportmedia.eu/img/home/intro/line-1-1.svg
813 ms
CSSlivesportmedia.eu/_nuxt/entry.BCiJ6Jkp.css
810 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://livesportmedia.eu/img/home/intro/line-1-2.svgimages2002.15 s177 B
https://livesportmedia.eu/fonts/LSDisplay-Variable.woff2fonts2002.02 s17.8 KB
https://livesportmedia.eu/fonts/LivesportFinderLatin-Bold.woff2fonts2001.73 s22.1 KB
https://livesportmedia.eu/fonts/LSDisplay-Variable.wofffonts2001.00 s21.0 KB
https://livesportmedia.eu/favicon.pngimages200995 ms3.8 KB
https://livesportmedia.eu/_nuxt/index.CkvU_VF1.csscss200942 ms1.8 KB
https://livesportmedia.eu/_nuxt/BPO6mJux.jsjavascript200835 ms81.1 KB
https://livesportmedia.eu/_nuxt/index.Dn3H1acL.csscss200820 ms249 B
https://livesportmedia.eu/img/home/intro/line-1-1.svgimages200813 ms178 B
https://livesportmedia.eu/_nuxt/entry.BCiJ6Jkp.csscss200810 ms2.0 KB
https://livesportmedia.eu/fonts/LivesportFinderLatin-Regular.woff2fonts200797 ms22.3 KB
https://www.googletagmanager.com/gtm.js?id=GTM-MCGDK4 3rd partyjavascript200628 ms128.4 KB
https://connect.facebook.net/en_US/fbevents.js 3rd partyjavascript200628 ms111.9 KB
https://cdn.cookielaw.org/scripttemplates/otSDKStub.js 3rd partyjavascript200628 ms13.6 KB
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.