reg.ru speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 12:34 UTC. Grade B (85/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 77 ms 10%
- TCP connect 215 ms 29%
- Server wait 453 ms 61%
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 744 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 13.3 KB over 1 request(s), which is lean.
- 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.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 744 ms. Of that, 453 ms was the server thinking and 292 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.
Compress text responses
high impact0 text response(s) of 10 KB or more are sent uncompressed, and the document itself is compressed. That is 0 B of compressible text.
Fix: Turn on brotli (preferred) or gzip for text/css, javascript and text/html in the web server. This is the cheapest win available on almost any site.
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.
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.