atomex.net speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 15:04 UTC. Grade B (81/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 98 ms 24%
- TCP connect 83 ms 20%
- Server wait 225 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
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 406 ms. That is workable, and the cheapest win left is caching or a warmer connection.
- The page transfers 1.89 MB over 12 request(s), which is lean. Javascript files are 71% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
- The HTML itself arrives gzip-compressed.
- It runs over HTTP/3, so the assets share a connection instead of opening one each.
- 97% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
- The largest element painted at 1.43 s, inside the 2.5 s Google calls good.
- Layout stayed still (CLS 0.012), so nothing jumps under the reader's cursor.
- The main thread was blocked for 115 ms in total, which is not enough to feel.
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.
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. 12 request(s) in total, 1.89 MB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 406 ms. Of that, 225 ms was the server thinking and 181 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 impact5 render-blocking resource(s) in the document head (1 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.
Total page weight
high impactThe page transfers 1.89 MB across 12 request(s), with the document itself at 9.4 KB.
Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.
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.
Third-party weight
medium impact4 third-party host(s) serve 1.82 MB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.
Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.
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://fonts.gstatic.com/s/materialsymbolsoutlined/v374/kJF1BvYX7BgnkSrUwT8OhrdQw4oELdPIeeII9v6oDMzByHX9rA6RzaxHMPdY43zj-jCxv3fzvRNU22ZXGJpEpjC_1n-q_4MrImHCIJIZrDDxHOej.woff2 3rd party | fonts | 200 | 684 ms | 358.3 KB |
| https://atomex.net/styles.9066ba52616f15d8.css | css | 200 | 588 ms | 50.3 KB |
| https://cdn.atomex.net/ui_release/atomexui/release/uiApp/polyfills.32958274d531d2c7.js 3rd party | javascript | 200 | 579 ms | 12.4 KB |
| https://use.fontawesome.com/8dfca10a42.js 3rd party | javascript | 200 | 570 ms | 3.4 KB |
| https://atomex.net/manifest.webmanifest | other | 200 | 562 ms | 1.3 KB |
| https://atomex.net/assets/fonts/roboto/roboto.css?family=Roboto:300,400,500,700|Roboto+Mono:300&display=swap | css | 200 | 532 ms | 838 B |
| https://cdn.atomex.net/ui_release/atomexui/release/uiApp/runtime.1e962613947802e3.js 3rd party | javascript | 200 | 473 ms | 2.1 KB |
| https://cdn.atomex.net/ui_release/atomexui/release/uiApp/vendor.e7817d3149862ce9.js 3rd party | javascript | 200 | 469 ms | 1.17 MB |
| https://cdn.atomex.net/ui_release/atomexui/release/uiApp/main.8b6510eaa3b05cac.js 3rd party | javascript | 200 | 445 ms | 150.0 KB |
| https://fonts.gstatic.com/s/materialicons/v145/flUhRq6tzZclQEJ-Vdg-IuiaDsNc.woff2 3rd party | fonts | 200 | 443 ms | 125.3 KB |
| https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.2/css/all.min.css 3rd party | css | 200 | 414 ms | 18.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.