www.coindesk.com speed test — 20 Oct 2026

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

https://www.coindesk.com/

20 October 2026 at 13:44 UTC · Free test · report pt_466a952a7f13

Re-test this page Test your own site

Grade

82/100

Performance82/100

Structure83/100

11 audit(s) passed, 5 need work

First byte (TTFB)702 msmeasured from this server

Fully loaded2.75 sfirst byte + slowest asset

Requests26document + assets

Page weight910.4 KBcompressed transfer

HTML document118.1 KBbr

ProtocolHTTP/3Vercel

Where the first byte went

DNS lookup 59 ms 8%
TCP connect 28 ms 4%
Server wait 616 ms 88%

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 70% of 4,999 pages tested here702 ms against a median of 448 ms

Page weightheavier than 60% of 4,999 pages tested here910.4 KB against a median of 650.3 KB

Fully loadedslower than 78% of 4,999 pages tested here2.75 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 702 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 910.4 KB over 26 request(s). Images files are 87% 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.

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

Images 25 requests

792.3 KB 87%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 702 ms. Of that, 616 ms was the server thinking and 87 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.

Total page weight

medium impact

The page transfers 910.4 KB across 26 request(s), with the document itself at 118.1 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

HTML document size

medium impact

The document transfers 118.1 KB. A bloated document delays every other request, because nothing else can start until it is parsed.

Fix: Paginate long listings, move repeated markup into a template, and stop inlining large data URIs into the HTML.

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.