www.wikiquote.org speed test — 20 Oct 2026

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

https://www.wikiquote.org/

20 October 2026 at 14:05 UTC · Free test · report pt_7f6e3987dca9
Grade
A
93/100
Performance93/100
Structure94/100

14 audit(s) passed, 2 need work

First byte (TTFB)443 msmeasured from this server
Fully loaded1.00 sfirst byte + slowest asset
Requests10document + assets
Page weight82.5 KBcompressed transfer
HTML document15.3 KBgzip
ProtocolHTTP/3ATS/9.2.15

Where the first byte went

  • DNS lookup 92 ms 21%
  • TCP connect 92 ms 21%
  • Server wait 259 ms 58%

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 here443 ms against a median of 449 ms
Page weightlighter than 89% of 4,999 pages tested here82.5 KB against a median of 650.5 KB
Fully loadedfaster than 92% of 4,999 pages tested here1.00 s against a median of 1.84 s
Requestssends fewer requests than 88% of 4,999 pages tested here10 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 443 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 82.5 KB over 10 request(s), which is lean. Images files are 72% 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 painted at 544 ms, inside the 2.5 s Google calls good.
  • The main thread was blocked for 106 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.

Desktop screenshot of www.wikiquote.org
Desktop 1366 × 768 · 68.2 KB · page is 1100 px tall
Mobile screenshot of www.wikiquote.org
Mobile 390 × 844 · 59.9 KB · page is 1222 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 paint544 msgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time106 mslong tasks during load
First contentful paint536 msfirst content on screen
Browser page weight49.8 KB5 request(s), scripts included
Largest contentful paint544 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time106 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 6 requests
59.7 KB 72%
Javascript 2 requests
6.6 KB 8%
Html 1 request
972 B 1%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 443 ms. Of that, 259 ms was the server thinking and 184 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

HTMLwww.wikiquote.org/static/apple-touch/wikiquote.png
558 ms
JAVASCRIPTwww.wikiquote.org/portal/wikiquote.org/assets/js/gt-ie9-…
544 ms
JAVASCRIPTwww.wikiquote.org/portal/wikiquote.org/assets/js/index-c…
509 ms
IMAGESwww.wikiquote.org/portal/wikiquote.org/assets/img/sprite…
478 ms
IMAGESwww.wikiquote.org/portal/wikiquote.org/assets/img/Wikiqu…
472 ms
IMAGESwww.wikiquote.org/portal/wikipedia.org/assets/img/Wikine…
471 ms
IMAGESwww.wikiquote.org/portal/wikiquote.org/assets/img/Wikiqu…
467 ms
IMAGESwww.wikiquote.org/portal/wikipedia.org/assets/img/Wikine…
461 ms
IMAGESwww.wikiquote.org/static/favicon/wikiquote.ico
451 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.wikiquote.org/static/apple-touch/wikiquote.pnghtml404558 ms972 B
https://www.wikiquote.org/portal/wikiquote.org/assets/js/gt-ie9-507b16b6be.jsjavascript200544 ms580 B
https://www.wikiquote.org/portal/wikiquote.org/assets/js/index-cd72cc99d1.jsjavascript200509 ms6.0 KB
https://www.wikiquote.org/portal/wikiquote.org/assets/img/sprite-0c5ee23c.svgimages200478 ms11.7 KB
https://www.wikiquote.org/portal/wikiquote.org/assets/img/Wikiquote-logo-tiles_2x.pngimages200472 ms26.1 KB
https://www.wikiquote.org/portal/wikipedia.org/assets/img/[email protected]images200471 ms3.3 KB
https://www.wikiquote.org/portal/wikiquote.org/assets/img/Wikiquote-logo-tiles_1x.pngimages200467 ms11.4 KB
https://www.wikiquote.org/portal/wikipedia.org/assets/img/Wikinews-logo_sister.pngimages200461 ms2.0 KB
https://www.wikiquote.org/static/favicon/wikiquote.icoimages200451 ms5.2 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.