vkplay.ru speed test — 20 Oct 2026

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

https://vkplay.ru/

20 October 2026 at 13:45 UTC · Free test · report pt_366e90b0de8c

Re-test this page Test your own site

Grade

71/100

Performance73/100

Structure67/100

9 audit(s) passed, 7 need work

First byte (TTFB)684 msmeasured from this server

Fully loaded2.82 sfirst byte + slowest asset

Requests26document + assets

Page weight1.97 MBcompressed transfer

HTML document3.5 KBgzip

ProtocolHTTP/3kittenx

Third-party1.92 MBother hosts

Where the first byte went

DNS lookup 58 ms 8%
TCP connect 193 ms 28%
Server wait 433 ms 63%

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 69% of 4,999 pages tested here684 ms against a median of 448 ms

Page weightheavier than 80% of 4,999 pages tested here1.97 MB against a median of 650.3 KB

Fully loadedslower than 80% of 4,999 pages tested here2.82 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 684 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 1.97 MB over 26 request(s). Javascript files are 69% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
98% 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

Javascript 15 requests

1.35 MB 69%

Css 4 requests

560.7 KB 28%

Fonts 3 requests

42.6 KB 2%

Images 3 requests

25.3 KB 1%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 684 ms. Of that, 433 ms was the server thinking and 251 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

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

Total page weight

high impact

The page transfers 1.97 MB across 26 request(s), with the document itself at 3.5 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

Cache static assets

medium impact

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

Third-party weight

medium impact

1 third-party host(s) serve 1.92 MB 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.