Home/Speed tests/www.chromium.org

www.chromium.org speed test — 20 Oct 2026

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

https://www.chromium.org/

20 October 2026 at 13:57 UTC · Free test · report pt_4780d2445e4a
Grade
A
97/100
Performance99/100
Structure95/100

14 audit(s) passed, 2 need work

Share this reportXWhatsAppLinkedInFacebookTelegramRedditEmail
First byte (TTFB)255 msmeasured from this server
Fully loaded255 msfirst byte + slowest asset
Requests1document + assets
Page weight68 Bcompressed transfer
HTML document68 Bbr
ProtocolHTTP/3server not sent

Where the first byte went

  • DNS lookup 63 ms 25%
  • TCP connect 51 ms 20%
  • Server wait 141 ms 55%

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 83% of 4,999 pages tested here255 ms against a median of 449 ms
Page weightlighter than 100% of 4,999 pages tested here68 B against a median of 650.5 KB
Fully loadedfaster than 100% of 4,999 pages tested here255 ms against a median of 1.84 s
Requestssends fewer requests than 98% of 4,999 pages tested here1 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 255 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 68 B over 1 request(s), which is lean.
  • 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 160 ms, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.

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.chromium.org
Desktop 1366 × 768 · 86.8 KB · page is 773 px tall
Mobile screenshot of www.chromium.org
Mobile 390 × 844 · 68.7 KB · page is 1106 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 paint160 msgood is under 2.5 s
Cumulative layout shift0.001under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint160 msfirst content on screen
Browser page weight229.6 KB13 request(s), scripts included
Largest contentful paint160 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.001
Goodgood under 0.1, poor over 0.25
Total blocking timenone over 50 ms
Goodgood under 200 ms, poor over 600 ms

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.

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.

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.

Run a website speed testHave it fixed