sso.passport.yandex.ru/push?uuid=3d540a24-03e4-4b8d-b85d-7bac6e80963e&retpath=https%3A%2F%2Fdzen.ru%2F%3Fyredirect%3Dtrue%26is_autologin_ya%3Dtrue speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 12:34 UTC. Grade B (86/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 48 ms 6%
- TCP connect 223 ms 28%
- Server wait 526 ms 66%
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 797 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 3.7 KB over 2 request(s), which is lean. Html files are 50% of it, so that one type is worth a look on its own.
- The HTML itself arrives gzip-compressed.
- It runs over HTTP/2, so the assets share a connection instead of opening one each.
- The largest element took 2.80 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
- Layout shift is 0.198 (good is under 0.1): something without a reserved size is loading late - an image, an ad, or a font swap.
- The main thread was blocked for 676 ms, so taps and scrolling wait while scripts run.
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.
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. 2 request(s) in total, 3.7 KB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 797 ms. Of that, 526 ms was the server thinking and 271 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.
Avoid extra redirects
medium impact2 redirect hop(s) before the page load started, each one a full round trip before the first byte.
Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.
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://sso.passport.yandex.ru/push?uuid=3d540a24-03e4-4b8d-b85d-7bac6e80963e&retpath=https%3A%2F%2Fdzen.ru%2F%3Fyredirect%3Dtrue%26is_autologin_ya%3Dtrue/it.host | html | 200 | 657 ms | 1.8 KB |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.