archlinux.org speed test — 20 Oct 2026

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

https://archlinux.org/

20 October 2026 at 13:20 UTC · Free test · report pt_20441d24d972
Grade
B
89/100
Performance87/100
Structure92/100

14 audit(s) passed, 2 need work

First byte (TTFB)664 msmeasured from this server
Fully loaded1.64 sfirst byte + slowest asset
Requests13document + assets
Page weight41.7 KBcompressed transfer
HTML document5.9 KBbr
ProtocolHTTP/3nginx

Where the first byte went

  • DNS lookup 79 ms 12%
  • TCP connect 38 ms 6%
  • Server wait 547 ms 82%

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 67% of 4,999 pages tested here664 ms against a median of 448 ms
Page weightlighter than 92% of 4,999 pages tested here41.7 KB against a median of 650.5 KB
Fully loadedfaster than 61% of 4,999 pages tested here1.64 s against a median of 1.84 s
Requestssends fewer requests than 85% of 4,999 pages tested here13 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 took 664 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 41.7 KB over 13 request(s), which is lean. Images files are 71% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives br-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 1.26 s, inside the 2.5 s Google calls good.

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 archlinux.org
Mobile 390 × 844 · 112.5 KB · page is 2121 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 paint1.26 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 paint1.26 sfirst content on screen
Browser page weight39.9 KB10 request(s), scripts included
Largest contentful paint1.26 s
Goodgood 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 9 requests
29.5 KB 71%
Css 2 requests
5.1 KB 12%
Javascript 1 request
1.1 KB 3%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 664 ms. Of that, 547 ms was the server thinking and 117 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.

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.

Waterfall

Slowest requests

IMAGESarchlinux.org/static/archlinux_common_style/apple-to…
977 ms
IMAGESarchlinux.org/static/rss.svg
972 ms
IMAGESarchlinux.org/static/archlinux_common_style/apple-to…
907 ms
IMAGESarchlinux.org/static/archlinux_common_style/apple-to…
874 ms
IMAGESarchlinux.org/static/archlinux_common_style/apple-to…
830 ms
IMAGESarchlinux.org/static/archlinux_common_style/favicon.png
813 ms
CSSarchlinux.org/static/archweb.css
805 ms
CSSarchlinux.org/static/archlinux_common_style/navbar.css
803 ms
JAVASCRIPTarchlinux.org/static/homepage.js
798 ms
IMAGESarchlinux.org/static/icons8_logo.png
791 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://archlinux.org/static/archlinux_common_style/apple-touch-icon-144x144.pngimages200977 ms3.0 KB
https://archlinux.org/static/rss.svgimages200972 ms227 B
https://archlinux.org/static/archlinux_common_style/apple-touch-icon-114x114.pngimages200907 ms1.9 KB
https://archlinux.org/static/archlinux_common_style/apple-touch-icon-72x72.pngimages200874 ms1.3 KB
https://archlinux.org/static/archlinux_common_style/apple-touch-icon-57x57.pngimages200830 ms1.1 KB
https://archlinux.org/static/archlinux_common_style/favicon.pngimages200813 ms7.7 KB
https://archlinux.org/static/archweb.csscss200805 ms4.6 KB
https://archlinux.org/static/archlinux_common_style/navbar.csscss200803 ms517 B
https://archlinux.org/static/homepage.jsjavascript200798 ms1.1 KB
https://archlinux.org/static/icons8_logo.pngimages200791 ms10.2 KB
https://archlinux.org/static/hetzner_logo.pngimages200791 ms1.9 KB
https://archlinux.org/static/click_and_pledge.pngimages200780 ms2.1 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.