www.wikipedia.org speed test — 20 Oct 2026

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

https://www.wikipedia.org/

20 October 2026 at 14:00 UTC · Free test · report pt_32ab0652819e
Grade
B
82/100
Performance78/100
Structure88/100

13 audit(s) passed, 3 need work

First byte (TTFB)433 msmeasured from this server
Fully loaded5.57 sfirst byte + slowest asset
Requests16document + assets
Page weight241.7 KBcompressed transfer
HTML document28.2 KBgzip
ProtocolHTTP/3mw-web.eqiad.main-977dcd544-xc8xd
Third-party126.3 KBother hosts

Where the first byte went

  • DNS lookup 74 ms 17%
  • TCP connect 104 ms 24%
  • Server wait 255 ms 59%

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 52% of 4,999 pages tested here433 ms against a median of 449 ms
Page weightlighter than 76% of 4,999 pages tested here241.7 KB against a median of 650.5 KB
Fully loadedslower than 93% of 4,999 pages tested here5.57 s against a median of 1.84 s
Requestssends fewer requests than 83% of 4,999 pages tested here16 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 433 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 241.7 KB over 16 request(s). Images files are 84% 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.
  • 52% 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

Images 13 requests
203.9 KB 84%
Javascript 2 requests
9.6 KB 4%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 433 ms. Of that, 255 ms was the server thinking and 178 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.

Cache static assets

medium impact

6 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.

Waterfall

Slowest requests

IMAGESwww.wikipedia.org/portal/wikipedia.org/assets/img/Wikipe…
5.13 s
IMAGESupload.wikimedia.org/wikipedia/donate/4/4f/Badge-monthly.png
5.13 s
IMAGESupload.wikimedia.org/wikipedia/donate/7/73/Badge-daf.png
5.13 s
IMAGESupload.wikimedia.org/wikipedia/donate/4/43/Badge-one-time.png
5.13 s
IMAGESupload.wikimedia.org/wikipedia/donate/d/de/Badge-workplace-…
5.13 s
IMAGESwww.wikipedia.org/portal/wikipedia.org/assets/img/Wikipe…
5.13 s
IMAGESupload.wikimedia.org/wikipedia/donate/6/6a/Badge-cga.png
5.13 s
IMAGESwww.wikipedia.org/portal/wikipedia.org/assets/img/sprite…
5.13 s
JAVASCRIPTwww.wikipedia.org/portal/wikipedia.org/assets/js/index-8…
5.13 s
IMAGESwww.wikipedia.org/portal/wikipedia.org/assets/img/Wikine…
5.13 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.wikipedia.org/portal/wikipedia.org/assets/img/[email protected]images2005.13 s36.6 KB
https://upload.wikimedia.org/wikipedia/donate/4/4f/Badge-monthly.png 3rd partyimages2005.13 s26.7 KB
https://upload.wikimedia.org/wikipedia/donate/7/73/Badge-daf.png 3rd partyimages2005.13 s22.8 KB
https://upload.wikimedia.org/wikipedia/donate/4/43/Badge-one-time.png 3rd partyimages2005.13 s22.6 KB
https://upload.wikimedia.org/wikipedia/donate/d/de/Badge-workplace-giving.png 3rd partyimages2005.13 s16.8 KB
https://www.wikipedia.org/portal/wikipedia.org/assets/img/Wikipedia-logo-v2.pngimages2005.13 s15.5 KB
https://upload.wikimedia.org/wikipedia/donate/6/6a/Badge-cga.png 3rd partyimages2005.13 s13.1 KB
https://www.wikipedia.org/portal/wikipedia.org/assets/img/sprite-e49fbf32.svgimages2005.13 s17.8 KB
https://www.wikipedia.org/portal/wikipedia.org/assets/js/index-8dfbdb3a7a.jsjavascript2005.13 s9.0 KB
https://www.wikipedia.org/portal/wikipedia.org/assets/img/[email protected]images2005.13 s3.3 KB
https://www.wikipedia.org/portal/wikipedia.org/assets/img/Wikinews-logo_sister.pngimages2005.13 s2.0 KB
https://www.wikipedia.org/static/apple-touch/wikipedia.pngimages2005.13 s1.3 KB
https://www.wikipedia.org/static/favicon/wikipedia.icoimages2005.13 s1.0 KB
https://www.wikipedia.org/portal/wikipedia.org/assets/js/gt-ie9-507b16b6be.jsjavascript2005.13 s580 B
https://upload.wikimedia.org/wikipedia/donate/8/81/Badge-endowment.png 3rd partyimages200646 ms24.3 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.