www.wikimedia.org speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 12:36 UTC. Grade A (93/100), with the screenshots, the timings and the fixes that matter.

https://www.wikimedia.org/

20 October 2026 at 12:36 UTC · Free test · report pt_dfe090b30600
Grade
A
93/100
Performance93/100
Structure94/100

14 audit(s) passed, 2 need work

First byte (TTFB)463 msmeasured from this server
Fully loaded1.47 sfirst byte + slowest asset
Requests22document + assets
Page weight127.2 KBcompressed transfer
HTML document10.3 KBgzip
ProtocolHTTP/3ATS/9.2.15
Third-party2.5 KBother hosts

Where the first byte went

  • DNS lookup 135 ms 29%
  • TCP connect 85 ms 18%
  • Server wait 243 ms 52%

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 52% of 4,999 pages tested here463 ms against a median of 448 ms
Page weightlighter than 85% of 4,999 pages tested here127.2 KB against a median of 650.5 KB
Fully loadedfaster than 73% of 4,999 pages tested here1.47 s against a median of 1.84 s
Requestssends fewer requests than 77% of 4,999 pages tested here22 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 463 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 127.2 KB over 22 request(s). Images files are 90% 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.
  • The largest element took 5.34 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.

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.wikimedia.org
Mobile 390 × 844 · 92.9 KB · page is 3483 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 paint5.34 sgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint5.22 sfirst content on screen
Browser page weight138.2 KB19 request(s), scripts included
Largest contentful paint5.34 s
Poorgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking timenone over 50 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 20 requests
114.2 KB 90%
Javascript 1 request
2.7 KB 2%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 463 ms. Of that, 243 ms was the server thinking and 220 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.

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

JAVASCRIPTwww.wikimedia.org/portal/wikimedia.org/assets/js/index-5…
1.00 s
IMAGESwww.wikimedia.org/portal/wikimedia.org/assets/img/Meta-W…
990 ms
IMAGESfoundation.wikimedia.org/favicon.ico
989 ms
IMAGESwww.wikimedia.org/portal/wikimedia.org/assets/img/Wikivo…
989 ms
IMAGESwww.wikimedia.org/portal/wikimedia.org/assets/img/Wikifu…
985 ms
IMAGESwww.wikimedia.org/portal/wikimedia.org/assets/img/puzzle…
981 ms
IMAGESwww.wikimedia.org/portal/wikimedia.org/assets/img/Wikida…
980 ms
IMAGESwww.wikimedia.org/portal/wikimedia.org/assets/img/Wikive…
975 ms
IMAGESwww.wikimedia.org/portal/wikimedia.org/assets/img/MediaW…
970 ms
IMAGESwww.wikimedia.org/portal/wikimedia.org/assets/img/Common…
967 ms

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.wikimedia.org/portal/wikimedia.org/assets/js/index-56d76e0e59.jsjavascript2001.00 s2.7 KB
https://www.wikimedia.org/portal/wikimedia.org/assets/img/Meta-Wiki-logo_sister.svgimages200990 ms1.5 KB
https://foundation.wikimedia.org/favicon.ico 3rd partyimages200989 ms2.5 KB
https://www.wikimedia.org/portal/wikimedia.org/assets/img/Wikivoyage-logo_sister.svgimages200989 ms284 B
https://www.wikimedia.org/portal/wikimedia.org/assets/img/Wikifunctions-logo_sister.svgimages200985 ms1.7 KB
https://www.wikimedia.org/portal/wikimedia.org/assets/img/puzzle-globe.svgimages200981 ms12.2 KB
https://www.wikimedia.org/portal/wikimedia.org/assets/img/Wikidata-logo_sister.svgimages200980 ms258 B
https://www.wikimedia.org/portal/wikimedia.org/assets/img/Wikiversity-logo_sister.svgimages200975 ms743 B
https://www.wikimedia.org/portal/wikimedia.org/assets/img/MediaWiki-logo_sister.svgimages200970 ms2.1 KB
https://www.wikimedia.org/portal/wikimedia.org/assets/img/Commons-logo_sister.svgimages200967 ms477 B
https://www.wikimedia.org/portal/wikimedia.org/assets/img/Wikispecies-logo_sister.svgimages200964 ms868 B
https://www.wikimedia.org/portal/wikimedia.org/assets/img/Wikiquote-logo_sister.svgimages200962 ms473 B
https://www.wikimedia.org/portal/wikimedia.org/assets/img/Wikisource-logo_sister.svgimages200956 ms2.6 KB
https://www.wikimedia.org/portal/wikimedia.org/assets/img/Wikipedia-logo_sister.svgimages200955 ms875 B
https://www.wikimedia.org/portal/wikimedia.org/assets/img/welcome-image.svgimages200951 ms20.4 KB
https://www.wikimedia.org/portal/wikimedia.org/assets/img/Wikibooks-logo_sister.svgimages200948 ms860 B
https://www.wikimedia.org/portal/wikimedia.org/assets/img/Wiktionary-logo_sister.svgimages200940 ms1.0 KB
https://www.wikimedia.org/portal/wikimedia.org/assets/img/OOjs_UI_icon_heart-invert.svgimages200940 ms728 B
https://www.wikimedia.org/portal/wikimedia.org/assets/img/wikimedia_logo.pngimages200928 ms59.4 KB
https://www.wikimedia.org/portal/wikipedia.org/assets/img/[email protected]images200921 ms3.3 KB
https://www.wikimedia.org/portal/wikipedia.org/assets/img/Wikinews-logo_sister.pngimages200920 ms2.0 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.