onefootball.com/en/home speed test — 20 Oct 2026

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

https://onefootball.com/en/home

20 October 2026 at 15:21 UTC · Free test · report pt_70c435f5671a

Re-test this page Test your own site

Grade

66/100

Performance55/100

Structure82/100

12 audit(s) passed, 4 need work

First byte (TTFB)1.37 smeasured from this server

Fully loaded4.94 sfirst byte + slowest asset

Requests26document + assets

Page weight120.6 KBcompressed transfer

HTML document51.8 KBgzip

ProtocolHTTP/3server not sent

Third-party68.8 KBother hosts

Where the first byte went

DNS lookup 80 ms 6%
TCP connect 55 ms 4%
Server wait 1.23 s 90%

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

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

Fully loadedslower than 90% of 4,999 pages tested here4.94 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.37 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 120.6 KB over 26 request(s). Images files are 57% 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.
57% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element took 2.60 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
Layout stayed still (CLS 0.037), so nothing jumps under the reader's cursor.
The main thread was blocked for 468 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.

Desktop screenshot of onefootball.com — **Desktop** 1366 × 768 · 132.1 KB · page is 6000 px tall

Mobile screenshot of onefootball.com — **Mobile** 390 × 844 · 52.6 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 paint2.60 sgood is under 2.5 s

Cumulative layout shift0.037under 0.1 is stable

Total blocking time468 mslong tasks during load

First contentful paint2.46 sfirst content on screen

Browser page weight3.41 MB143 request(s), scripts included

Failed requests9blocked or unreachable

Largest contentful paint2.60 s

Needs improvementgood under 2.5 s, poor over 4 s

Cumulative layout shift0.037

Goodgood under 0.1, poor over 0.25

Total blocking time468 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 24 requests

68.8 KB 57%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1369 ms. Of that, 1233 ms was the server thinking and 135 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

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

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.