www.wiktionary.org speed test — 20 Oct 2026

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

https://www.wiktionary.org/

20 October 2026 at 12:44 UTC · Free test · report pt_16335b8c3dfe
Grade
A
97/100
Performance97/100
Structure98/100

15 audit(s) passed, 1 need work

First byte (TTFB)308 msmeasured from this server
Fully loaded974 msfirst byte + slowest asset
Requests10document + assets
Page weight166.4 KBcompressed transfer
HTML document17.6 KBgzip
ProtocolHTTP/3ATS/9.2.15

Where the first byte went

  • DNS lookup 51 ms 17%
  • TCP connect 66 ms 21%
  • Server wait 190 ms 62%

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 73% of 4,999 pages tested here308 ms against a median of 449 ms
Page weightlighter than 82% of 4,999 pages tested here166.4 KB against a median of 650.5 KB
Fully loadedfaster than 92% of 4,999 pages tested here974 ms 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 308 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 166.4 KB over 10 request(s), which is lean. Images files are 85% 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 508 ms, inside the 2.5 s Google calls good.
  • The main thread was blocked for 138 ms in total, which is not enough to feel.

Fix first: Avoid extra redirects - 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.

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

Page weight by type

What the page is made of

Images 7 requests
142.2 KB 85%
Javascript 2 requests
6.6 KB 4%

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

Top issues

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.wiktionary.org/portal/wiktionary.org/assets/js/gt-ie9…
666 ms
JAVASCRIPTwww.wiktionary.org/portal/wiktionary.org/assets/js/index-…
640 ms
IMAGESwww.wiktionary.org/portal/wiktionary.org/assets/img/Wikti…
617 ms
IMAGESwww.wiktionary.org/portal/wiktionary.org/assets/img/Wikti…
615 ms
IMAGESwww.wiktionary.org/portal/wikipedia.org/assets/img/Wikine…
614 ms
IMAGESwww.wiktionary.org/portal/wikipedia.org/assets/img/Wikine…
614 ms
IMAGESwww.wiktionary.org/portal/wiktionary.org/assets/img/sprit…
598 ms
IMAGESwww.wiktionary.org/static/apple-touch/wiktionary.png
598 ms
IMAGESwww.wiktionary.org/static/favicon/piece.ico
598 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.wiktionary.org/portal/wiktionary.org/assets/js/gt-ie9-507b16b6be.jsjavascript200666 ms580 B
https://www.wiktionary.org/portal/wiktionary.org/assets/js/index-cd72cc99d1.jsjavascript200640 ms6.0 KB
https://www.wiktionary.org/portal/wiktionary.org/assets/img/Wiktionary-logo-tiles_1x.pngimages200617 ms33.4 KB
https://www.wiktionary.org/portal/wiktionary.org/assets/img/Wiktionary-logo-tiles_2x.pngimages200615 ms79.5 KB
https://www.wiktionary.org/portal/wikipedia.org/assets/img/[email protected]images200614 ms3.3 KB
https://www.wiktionary.org/portal/wikipedia.org/assets/img/Wikinews-logo_sister.pngimages200614 ms2.0 KB
https://www.wiktionary.org/portal/wiktionary.org/assets/img/sprite-512be98e.svgimages200598 ms11.0 KB
https://www.wiktionary.org/static/apple-touch/wiktionary.pngimages200598 ms6.5 KB
https://www.wiktionary.org/static/favicon/piece.icoimages200598 ms6.5 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.