www.forbes.ru speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 16:09 UTC. Grade B (87/100), with the screenshots, the timings and the fixes that matter.

https://www.forbes.ru/

20 October 2026 at 16:09 UTC · Free test · report pt_671181ae9dd1
Grade
B
87/100
Performance90/100
Structure83/100

11 audit(s) passed, 5 need work

First byte (TTFB)572 msmeasured from this server
Fully loaded572 msfirst byte + slowest asset
Requests1document + assets
Page weight13.3 KBcompressed transfer
HTML document13.3 KBno compression
ProtocolHTTP/35.252.32.223

Where the first byte went

  • DNS lookup 82 ms 14%
  • TCP connect 152 ms 27%
  • Server wait 339 ms 59%

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 60% of 4,999 pages tested here572 ms against a median of 448 ms
Page weightlighter than 95% of 4,999 pages tested here13.3 KB against a median of 650.5 KB
Fully loadedfaster than 97% of 4,999 pages tested here572 ms against a median of 1.84 s
Requestssends fewer requests than 98% of 4,999 pages tested here1 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 572 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 13.3 KB over 1 request(s), which is lean.
  • 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.

No screenshot for this report.

The headless browser did not capture this page when the test ran, so only the server measurements are shown.

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 572 ms. Of that, 339 ms was the server thinking and 234 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

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

Avoid extra redirects

medium impact

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

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.

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.