miraheze.org speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 15:32 UTC. Grade B (89/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 74 ms 12%
- TCP connect 65 ms 11%
- Server wait 467 ms 77%
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.
What these numbers mean
- The first byte took 606 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 312.0 KB over 11 request(s), which is lean. Fonts files are 87% of it, so subset the fonts and stop preloading the weights you do not render.
- The HTML itself arrives gzip-compressed.
- It runs over HTTP/3, so the assets share a connection instead of opening one each.
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.
The headless browser did not capture this page when the test ran, so only the server measurements are shown.
Page weight by type
What the page is made of
Transfer size, compressed as sent. 11 request(s) in total, 312.0 KB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 606 ms. Of that, 467 ms was the server thinking and 139 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.
Render-blocking resources
high impact4 render-blocking resource(s) in the document head (0 script(s), 4 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 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.
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://miraheze.org/css/bootstrap.min.v1.css | css | 200 | 590 ms | 3.8 KB |
| https://analytics.wikitide.net/matomo.php?idsite=9838&rec=1&action_name=Landing_Home 3rd party | images | 200 | 583 ms | 43 B |
| https://miraheze.org/css/style.v1.css | css | 200 | 568 ms | 2.5 KB |
| https://miraheze.org/webfonts/fa-brands-400.woff2 | fonts | 200 | 546 ms | 115.9 KB |
| https://miraheze.org/img/favicon.ico | images | 200 | 546 ms | 1006 B |
| https://miraheze.org/img/apple-touch-icon.png | images | 200 | 521 ms | 2.0 KB |
| https://miraheze.org/css/fonts.min.v1.css | css | 200 | 519 ms | 1.7 KB |
| https://cdn.jsdelivr.net/npm/[email protected]/dist/js/bootstrap.bundle.min.js 3rd party | javascript | 200 | 456 ms | 23.9 KB |
| https://miraheze.org/img/Miraheze-Logo.svg | images | 200 | 455 ms | 486 B |
| https://miraheze.org/webfonts/fa-solid-900.woff2 | fonts | 200 | 449 ms | 154.5 KB |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.