example.com speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 12:34 UTC. Grade A (96/100), with the screenshots, the timings and the fixes that matter.
A newer test of this page exists: 26 Oct 2026, grade A (96/100). This older result is kept for comparison.
Where the first byte went
- DNS lookup 49 ms 33%
- TCP connect 21 ms 14%
- Server wait 79 ms 53%
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
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.
Score history
2 tests of this URL, oldest to newest: 96 → 96 out of 100. The top line is a perfect score.
What these numbers mean
- The server answered in 149 ms, which is fast: almost all of the wait is the page itself, not the host.
- The page transfers 1.7 KB over 2 request(s), which is lean. Javascript files are 81% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
- 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 124 ms, inside the 2.5 s Google calls good.
Fix first: Cache static assets - Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.
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.
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.
Page weight by type
What the page is made of
Transfer size, compressed as sent. 2 request(s) in total, 1.7 KB across all of them.
Top issues
Cache static assets
medium impact1 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.
Mobile viewport
medium impactNo 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 impactHSTS 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
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
| Request | Type | Status | Time | Size |
|---|---|---|---|---|
| https://example.com/s.js | javascript | 200 | 124 ms | 1.3 KB |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.