rm358.com speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 14:33 UTC. Grade A (94/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 92 ms 21%
- TCP connect 61 ms 14%
- Server wait 282 ms 65%
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 434 ms. That is workable, and the cheapest win left is caching or a warmer connection.
- The page transfers 7.3 KB over 4 request(s), which is lean. Images files are 74% of it, so resize and recompress the largest images before anything else.
- 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 628 ms, inside the 2.5 s Google calls good.
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. 4 request(s) in total, 7.3 KB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 434 ms. Of that, 282 ms was the server thinking and 153 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.
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://rm358.com/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js | html | 404 | 281 ms | 0 B |
| https://rm358.com/assets/index.css | css | 200 | 254 ms | 722 B |
| https://rm358.com/assets/logo-CR06HuVS.svg | images | 200 | 238 ms | 5.4 KB |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.