mega.co.nz speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 12:26 UTC. Grade A (91/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 57 ms 10%
- TCP connect 162 ms 28%
- Server wait 368 ms 63%
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 587 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 2.7 KB over 2 request(s), which is lean. Javascript files are 80% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
- It runs over HTTP/2, 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. 2 request(s) in total, 2.7 KB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 587 ms. Of that, 368 ms was the server thinking and 219 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 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.
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://mega.co.nz/redirect.js | javascript | 200 | 621 ms | 2.2 KB |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.