www.fussball.de/homepage speed test — 20 Oct 2026

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

https://www.fussball.de/homepage

20 October 2026 at 15:08 UTC · Free test · report pt_b3cef303a990
Grade
B
88/100
Performance93/100
Structure80/100

11 audit(s) passed, 5 need work

First byte (TTFB)402 msmeasured from this server
Fully loaded1.85 sfirst byte + slowest asset
Requests26document + assets
Page weight878.6 KBcompressed transfer
HTML document21.4 KBgzip
ProtocolHTTP/3server not sent
Third-party204.1 KBother hosts

Where the first byte went

  • DNS lookup 56 ms 14%
  • TCP connect 40 ms 10%
  • Server wait 305 ms 76%

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 56% of 4,999 pages tested here402 ms against a median of 449 ms
Page weightheavier than 59% of 4,999 pages tested here878.6 KB against a median of 650.3 KB
Fully loadedfaster than 50% of 4,999 pages tested here1.85 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 402 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 878.6 KB over 26 request(s). Javascript files are 81% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 23% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.

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.

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

Javascript 11 requests
713.5 KB 81%
Images 14 requests
143.7 KB 16%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 402 ms. Of that, 305 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

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

Image delivery and format

medium impact

0 image(s) over 200 KB and 1 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

JavaScript weight

medium impact

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

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

JAVASCRIPTwww.fussball.de/static/por/8.91.1.1/js/script.js
1.45 s
IMAGESwww.fussball.de/static/por/8.91.1.1/icon/favicon.ico
1.45 s
JAVASCRIPTwww.fussball.de/static/layout/fbde2/por/8.91.1.1/js/go…
1.44 s
JAVASCRIPTwww.fussball.de/static/layout/fbde2/por/8.91.1.1/js/tr…
1.44 s
JAVASCRIPTwww.fussball.de/static/layout/fbde2/por/8.91.1.1/js/op…
1.43 s
IMAGESwww.fussball.de/static/layout/fbde2/por/8.91.1.1/font/…
1.41 s
JAVASCRIPTwww.fussball.de/static/layout/fbde2/por/8.91.1.1/js/tr…
1.41 s
IMAGESwww.fussball.de/static/layout/fbde2/por/8.91.1.1/image…
1.40 s
IMAGESwww.fussball.de/static/layout/fbde2/por/8.91.1.1/image…
1.40 s
IMAGESwww.fussball.de/static/layout/fbde2/por/8.91.1.1/image…
1.40 s

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.fussball.de/static/por/8.91.1.1/js/script.jsjavascript2001.45 s506.1 KB
https://www.fussball.de/static/por/8.91.1.1/icon/favicon.icoimages2001.45 s1.7 KB
https://www.fussball.de/static/layout/fbde2/por/8.91.1.1/js/google-remarketing.jsjavascript2001.44 s209 B
https://www.fussball.de/static/layout/fbde2/por/8.91.1.1/js/tracking-facebook.jsjavascript2001.44 s323 B
https://www.fussball.de/static/layout/fbde2/por/8.91.1.1/js/open-app.jsjavascript2001.43 s204 B
https://www.fussball.de/static/layout/fbde2/por/8.91.1.1/font/logo.svgimages2001.41 s456 B
https://www.fussball.de/static/layout/fbde2/por/8.91.1.1/js/tracking-adobe.jsjavascript2001.41 s167 B
https://www.fussball.de/static/layout/fbde2/por/8.91.1.1/images/provider_logo_google.pngimages2001.40 s3.2 KB
https://www.fussball.de/static/layout/fbde2/por/8.91.1.1/images/partner/footer_partner_logo_zalando.pngimages2001.40 s4.1 KB
https://www.fussball.de/static/layout/fbde2/por/8.91.1.1/images/promateur/Promateur_Banner_380x250.jpgimages2001.40 s116.9 KB
https://www.fussball.de/static/layout/fbde2/por/8.91.1.1/js/tracking-amplitude.jsjavascript2001.39 s2.5 KB
https://www.fussball.de/static/layout/fbde2/por/8.91.1.1/images/partner/footer_partner_logo_vw.pngimages2001.38 s1.6 KB
https://www.fussball.de/static/layout/fbde2/por/8.91.1.1/images/partner/footer_partner_logo_spm.pngimages2001.37 s2.0 KB
https://www.fussball.de/static/layout/fbde2/por/8.91.1.1/images/provider_logo_fbde.pngimages2001.37 s1.4 KB
https://www.fussball.de/static/layout/fbde2/por/8.91.1.1/images/partner/footer_partner_logo_adidas.pngimages2001.35 s1.3 KB
https://www.fussball.de/static/layout/fbde2/por/8.91.1.1/images/FB-f-Logo__blue_58.pngimages2001.35 s1.0 KB
https://www.fussball.de/static/layout/fbde2/por/8.91.1.1/images/provider_logo_apple.pngimages2001.35 s1.3 KB
https://www.fussball.de/static/layout/fbde2/por/8.91.1.1/images/partner/footer_partner_logo_ergo.pngimages2001.35 s2.5 KB
https://www.fussball.de/static/layout/fbde2/por/8.91.1.1/images/provider_logo_dfbnet.pngimages2001.33 s5.8 KB
https://www.fussball.de/static/layout/fbde2/por/8.91.1.1/images/logo.svgimages2001.33 s456 B
https://cdn.eye-able.com/public/js/eyeAble.js 3rd partyjavascript200998 ms134.7 KB
https://cdn.eye-able.com/configs/www.fussball.de.js 3rd partyjavascript200968 ms778 B
https://app.eu.usercentrics.eu/browser-ui/latest/loader.js 3rd partyjavascript200931 ms10.4 KB
https://assets.adobedtm.com/97c422f768f3/28b81cdb5065/launch-9364d69cd4f0.min.js 3rd partyjavascript200924 ms17.6 KB
https://sdp.eu.usercentrics.eu/legacy/uc-block.bundle.js 3rd partyjavascript200880 ms40.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.