net.ru speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 13:53 UTC. Grade C (74/100), with the screenshots, the timings and the fixes that matter.

https://net.ru/

20 October 2026 at 13:53 UTC · Free test · report pt_01c2c2831fe9
Grade
C
74/100
Performance74/100
Structure73/100

11 audit(s) passed, 5 need work

First byte (TTFB)1.09 smeasured from this server
Fully loaded2.14 sfirst byte + slowest asset
Requests6document + assets
Page weight123.4 KBcompressed transfer
HTML document6.8 KBno compression
ProtocolHTTP/2openresty
Third-party217 Bother hosts

Where the first byte went

  • DNS lookup 218 ms 20%
  • TCP connect 200 ms 18%
  • Server wait 669 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

First byteslower than 88% of 4,999 pages tested here1.09 s against a median of 448 ms
Page weightlighter than 85% of 4,999 pages tested here123.4 KB against a median of 650.5 KB
Fully loadedslower than 62% of 4,999 pages tested here2.14 s against a median of 1.84 s
Requestssends fewer requests than 92% of 4,999 pages tested here6 against a median of 26

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 1.09 s. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 123.4 KB over 6 request(s), which is lean. Javascript files are 77% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
  • It runs over HTTP/2, so the assets share a connection instead of opening one each.
  • The largest element painted at 2.09 s, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.

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.

Mobile screenshot of net.ru
Mobile 390 × 844 · 187.1 KB · page is 2217 px tall

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.

Largest contentful paint2.09 sgood is under 2.5 s
Cumulative layout shift0.001under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint2.08 sfirst content on screen
Browser page weight283.6 KB10 request(s), scripts included
Largest contentful paint2.09 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.001
Goodgood under 0.1, poor over 0.25
Total blocking timenone over 50 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 1 request
95.0 KB 77%
Css 2 requests
20.9 KB 17%
Images 2 requests
672 B 1%

Transfer size, compressed as sent. 6 request(s) in total, 123.4 KB across all of them.

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1088 ms. Of that, 669 ms was the server thinking and 418 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 impact

2 text response(s) of 10 KB or more are sent uncompressed, and the document itself is not compressed. That is 115.7 KB 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.

Render-blocking resources

high impact

3 render-blocking resource(s) in the document head (1 script(s), 2 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Cache static assets

medium impact

4 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.

Strict-Transport-Security

low impact

HSTS 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.

Waterfall

Slowest requests

IMAGESnet.ru/images/home-active.png
1.05 s
CSSnet.ru/css/main.css
1.03 s
JAVASCRIPTnet.ru/static/plugins/jquery-1.12.2.min.js
975 ms
IMAGESnet.ru/images/home.png
901 ms
CSSfonts.googleapis.com/css
430 ms

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

RequestTypeStatusTimeSize
https://net.ru/images/home-active.pngimages2001.05 s346 B
https://net.ru/css/main.csscss2001.03 s20.7 KB
https://net.ru/static/plugins/jquery-1.12.2.min.jsjavascript200975 ms95.0 KB
https://net.ru/images/home.pngimages200901 ms326 B
https://fonts.googleapis.com/css?family=Open+Sans:300&subset=latin,cyrillic 3rd partycss200430 ms217 B
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.