bitcoin.org/en speed test — 20 Oct 2026

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

https://bitcoin.org/en/

20 October 2026 at 15:25 UTC · Free test · report pt_bdef4aeb6ae2
Grade
B
89/100
Performance92/100
Structure85/100

13 audit(s) passed, 3 need work

First byte (TTFB)446 msmeasured from this server
Fully loaded1.80 sfirst byte + slowest asset
Requests26document + assets
Page weight6.7 KBcompressed transfer
HTML document6.7 KBzstd
ProtocolHTTP/3cloudflare

Where the first byte went

  • DNS lookup 85 ms 19%
  • TCP connect 36 ms 8%
  • Server wait 324 ms 73%

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 50% of 4,999 pages tested here446 ms against a median of 449 ms
Page weightlighter than 96% of 4,999 pages tested here6.7 KB against a median of 650.5 KB
Fully loadedfaster than 52% of 4,999 pages tested here1.80 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 446 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 6.7 KB over 26 request(s).
  • The HTML itself arrives zstd-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 680 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.017), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 129 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 bitcoin.org
Mobile 390 × 844 · 32.2 KB · page is 3707 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 paint680 msgood is under 2.5 s
Cumulative layout shift0.017under 0.1 is stable
Total blocking time129 mslong tasks during load
First contentful paint572 msfirst content on screen
Browser page weight787.6 KB37 request(s), scripts included
Failed requests1blocked or unreachable
Largest contentful paint680 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.017
Goodgood under 0.1, poor over 0.25
Total blocking time129 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 446 ms. Of that, 324 ms was the server thinking and 121 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

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

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.

Waterfall

Slowest requests

HTMLbitcoin.org/en/img/icons/ico_business.svg
1.35 s
HTMLbitcoin.org/en/favicon.png
1.35 s
HTMLbitcoin.org/en/img/animations/herecomesbitcoin/pos…
1.34 s
HTMLbitcoin.org/en/img/animations/herecomesbitcoin/pos…
1.33 s
HTMLbitcoin.org/en/img/animations/herecomesbitcoin/pos…
1.33 s
HTMLbitcoin.org/en/img/icons/logo-footer.svg
1.33 s
HTMLbitcoin.org/en/img/icons/ico_individuals.svg
1.33 s
HTMLbitcoin.org/en/img/icons/ico_developers.svg
1.32 s
HTMLbitcoin.org/en/js/cookieconsent/cookieconsent.js
1.32 s
HTMLbitcoin.org/en/img/animations/herecomesbitcoin/hun…
1.32 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://bitcoin.org/en/img/icons/ico_business.svg?1792398050html4041.35 s0 B
https://bitcoin.org/en/favicon.png?1792398050html4041.35 s0 B
https://bitcoin.org/en/img/animations/herecomesbitcoin/posters/fairy.svghtml4041.34 s0 B
https://bitcoin.org/en/img/animations/herecomesbitcoin/posters/flower_heads.svghtml4041.33 s0 B
https://bitcoin.org/en/img/animations/herecomesbitcoin/posters/hungry.svghtml4041.33 s0 B
https://bitcoin.org/en/img/icons/logo-footer.svg?1792398050html4041.33 s0 B
https://bitcoin.org/en/img/icons/ico_individuals.svg?1792398050html4041.33 s0 B
https://bitcoin.org/en/img/icons/ico_developers.svg?1792398050html4041.32 s0 B
https://bitcoin.org/en/js/cookieconsent/cookieconsent.js?1792398050html4041.32 s0 B
https://bitcoin.org/en/img/animations/herecomesbitcoin/hungry_left_hand.svg?1792398050html4041.32 s0 B
https://bitcoin.org/en/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.jshtml4041.32 s0 B
https://bitcoin.org/en/img/animations/herecomesbitcoin/hungry_right_hand.svg?1792398050html4041.31 s0 B
https://bitcoin.org/en/img/icons/main_ico_lowfee.svg?1792398050html4041.31 s0 B
https://bitcoin.org/en/js/jquery/jquery.qrcode.min.jshtml4041.31 s0 B
https://bitcoin.org/en/img/icons/main_ico_instant.svg?1792398050html4041.30 s0 B
https://bitcoin.org/en/img/icons/logotop.svg?1792398050html4041.30 s0 B
https://bitcoin.org/en/js/lazy-animations.js?1792398050html4041.29 s0 B
https://bitcoin.org/en/js/jquery/jquery-1.11.2.min.jshtml4041.29 s0 B
https://bitcoin.org/en/css/main.css?1792398050html4041.29 s0 B
https://bitcoin.org/en/js/main.js?1792398050html4041.28 s0 B
https://bitcoin.org/en/css/font-awesome-4.4.0/css/font-awesome.min.csshtml4041.28 s0 B
https://bitcoin.org/en/img/icons/main_ico_worldwide.svg?1792398050html4041.27 s0 B
https://bitcoin.org/en/img/animations/herecomesbitcoin/posters/cat.svghtml4041.27 s0 B
https://bitcoin.org/en/img/icons/ico_arrow_down.svg?1792398050html4041.26 s0 B
https://bitcoin.org/en/js/base.js?1792398050html4041.17 s0 B
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.