www.freedesktop.org/wiki speed test — 20 Oct 2026

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

https://www.freedesktop.org/wiki/

20 October 2026 at 13:28 UTC · Free test · report pt_4c248ebaecc0
Grade
A
90/100
Performance96/100
Structure82/100

11 audit(s) passed, 5 need work

First byte (TTFB)362 msmeasured from this server
Fully loaded722 msfirst byte + slowest asset
Requests6document + assets
Page weight15.6 KBcompressed transfer
HTML document3.3 KBgzip
ProtocolHTTP/2Apache

Where the first byte went

  • DNS lookup 103 ms 28%
  • TCP connect 34 ms 9%
  • Server wait 225 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 62% of 4,999 pages tested here362 ms against a median of 449 ms
Page weightlighter than 94% of 4,999 pages tested here15.6 KB against a median of 650.5 KB
Fully loadedfaster than 96% of 4,999 pages tested here722 ms against a median of 1.84 s
Requestssends fewer requests than 92% of 4,999 pages tested here6 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 362 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 15.6 KB over 6 request(s), which is lean. Images files are 51% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/2, so the assets share a connection instead of opening one each.
  • The largest element painted at 412 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.015), so nothing jumps under the reader's cursor.

Fix first: Render-blocking resources - 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.

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.

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 paint412 msgood is under 2.5 s
Cumulative layout shift0.015under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint408 msfirst content on screen
Browser page weight11.7 KB5 request(s), scripts included
Failed requests2blocked or unreachable
Largest contentful paint412 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.015
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 2 requests
8.0 KB 51%
Css 3 requests
4.3 KB 28%

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

Top issues

Render-blocking resources

high impact

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

Cache static assets

medium impact

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

Mobile viewport

medium impact

No viewport meta tag, so a phone renders the desktop layout scaled down.

Fix: Add a viewport meta tag with width=device-width and an initial scale of 1.

Strict-Transport-Security

low impact

HSTS is not set, so the first visit on a hostile network can still be downgraded to HTTP.

Fix: Send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains once every subdomain is HTTPS.

Waterfall

Slowest requests

IMAGESwww.freedesktop.org/wiki/logo.png
360 ms
IMAGESwww.paypal.com/en_US/i/scr/pixel.gif
352 ms
CSSwww.freedesktop.org/wiki/local.css
335 ms
CSSwww.freedesktop.org/wiki/xorg.css
310 ms
CSSwww.freedesktop.org/wiki/style.css
306 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.freedesktop.org/wiki/logo.pngimages200360 ms8.0 KB
https://www.paypal.com/en_US/i/scr/pixel.gif 3rd partyimages301352 ms0 B
https://www.freedesktop.org/wiki/local.csscss200335 ms96 B
https://www.freedesktop.org/wiki/xorg.csscss200310 ms1.6 KB
https://www.freedesktop.org/wiki/style.csscss200306 ms2.6 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.