adtec.ru speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 15:40 UTC. Grade C (72/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 280 ms 28%
- TCP connect 209 ms 21%
- Server wait 497 ms 50%
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 985 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 990.7 KB over 7 request(s), which is lean. Images files are 52% of it, so resize and recompress the largest images before anything else.
- The HTML itself arrives gzip-compressed.
- 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.
Page weight by type
What the page is made of
Transfer size, compressed as sent. 7 request(s) in total, 990.7 KB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 985 ms. Of that, 497 ms was the server thinking and 489 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.
Image delivery and format
high impact2 image(s) over 200 KB and 2 large image(s) still served as JPEG or PNG.
Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.
Total page weight
medium impactThe page transfers 990.7 KB across 7 request(s), with the document itself at 1.4 KB.
Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.
Cache static assets
medium impact5 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.
JavaScript weight
medium impact1 JavaScript file(s) over 200 KB: index-Dvvu0KYn.js (456.4 KB)
Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.
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://mc.yandex.ru/watch/108522766 3rd party | other | 302 | 1.27 s | 0 B |
| https://adtec.ru/assets/index-iNMSSw9H.css | css | 200 | 1.17 s | 19.2 KB |
| https://adtec.ru/images/hero_bg_dark.png | images | 200 | 1.09 s | 207.2 KB |
| https://adtec.ru/assets/index-Dvvu0KYn.js | javascript | 200 | 1.06 s | 456.4 KB |
| https://adtec.ru/images/hero_bg_light.png | images | 200 | 1.04 s | 244.2 KB |
| https://adtec.ru/favicon.png | images | 200 | 1.01 s | 62.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.