www.thescore.com speed test — 20 Oct 2026

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

https://www.thescore.com/

20 October 2026 at 14:50 UTC · Free test · report pt_fb3b198eb070

Re-test this page Test your own site

Grade

87/100

Performance93/100

Structure79/100

11 audit(s) passed, 5 need work

First byte (TTFB)438 msmeasured from this server

Fully loaded1.73 sfirst byte + slowest asset

Requests26document + assets

Page weight618.8 KBcompressed transfer

HTML document19.3 KBbr

ProtocolHTTP/3cloudflare

Third-party598.2 KBother hosts

Where the first byte went

DNS lookup 64 ms 15%
TCP connect 13 ms 3%
Server wait 360 ms 82%

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 51% of 4,999 pages tested here438 ms against a median of 449 ms

Page weightlighter than 51% of 4,999 pages tested here618.8 KB against a median of 650.5 KB

Fully loadedfaster than 56% of 4,999 pages tested here1.73 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 438 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 618.8 KB over 26 request(s). Images files are 97% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
97% 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 760 ms, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.030), so nothing jumps under the reader's cursor.
The main thread was blocked for 95 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 www.thescore.com — **Mobile** 390 × 844 · 162.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 paint760 msgood is under 2.5 s

Cumulative layout shift0.030under 0.1 is stable

Total blocking time95 mslong tasks during load

First contentful paint612 msfirst content on screen

Browser page weight3.53 MB213 request(s), scripts included

Failed requests13blocked or unreachable

Largest contentful paint760 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.030

Goodgood under 0.1, poor over 0.25

Total blocking time95 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

599.4 KB 97%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 438 ms. Of that, 360 ms was the server thinking and 77 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

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

Third-party weight

medium impact

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

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.