irecommend.ru speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 15:03 UTC. Grade D (67/100), with the screenshots, the timings and the fixes that matter.

https://irecommend.ru/

20 October 2026 at 15:03 UTC · Free test · report pt_5774697a41a8

Re-test this page Test your own site

Grade

67/100

Performance59/100

Structure79/100

13 audit(s) passed, 3 need work

First byte (TTFB)1.06 smeasured from this server

Fully loaded6.18 sfirst byte + slowest asset

Requests26document + assets

Page weight93.6 KBcompressed transfer

HTML document35.4 KBgzip

ProtocolHTTP/3server not sent

Third-party52.4 KBother hosts

Where the first byte went

DNS lookup 72 ms 7%
TCP connect 224 ms 21%
Server wait 763 ms 72%

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.06 s against a median of 448 ms

Page weightlighter than 88% of 4,999 pages tested here93.6 KB against a median of 650.5 KB

Fully loadedslower than 96% of 4,999 pages tested here6.18 s against a median of 1.84 s

Requestssends more requests than 100% of 4,999 pages tested here26 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.06 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 93.6 KB over 26 request(s). Images files are 62% 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.
56% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.

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.

No screenshot for this report.

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

Images 25 requests

58.2 KB 62%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1059 ms. Of that, 763 ms was the server thinking and 296 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.

Render-blocking resources

high impact

19 render-blocking resource(s) in the document head (0 script(s), 19 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.

Mobile viewport

medium impact

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