gosuslugi.ru speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 12:24 UTC. Grade A (90/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 35 ms 6%
- TCP connect 177 ms 28%
- Server wait 416 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 629 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 570.8 KB over 6 request(s), which is lean. Fonts files are 59% of it, so subset the fonts and stop preloading the weights you do not render.
- It runs over HTTP/2, so the assets share a connection instead of opening one each.
- 95% 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 744 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.
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. 6 request(s) in total, 570.8 KB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 629 ms. Of that, 416 ms was the server thinking and 212 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.
Third-party weight
medium impact1 third-party host(s) serve 544.2 KB 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://gu-st.ru/portal-st/lib-assets/fonts/Lato-Bold.woff 3rd party | fonts | 200 | 758 ms | 35.9 KB |
| https://gu-st.ru/portal-st/lib-assets/fonts/Lato-Regular.woff 3rd party | fonts | 200 | 722 ms | 301.9 KB |
| https://gu-st.ru/portal-st/lib-assets/fonts/Lato-Bold.woff2 3rd party | other | 200 | 682 ms | 27.9 KB |
| https://gu-st.ru/portal-st/lib-assets/fonts/Lato-Regular.woff2 3rd party | other | 200 | 618 ms | 178.4 KB |
| https://gosuslugi.ru/__jsch/static/script.js | javascript | 200 | 601 ms | 17.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.