www.xv-ru.com speed test — 20 Oct 2026

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

https://www.xv-ru.com/

20 October 2026 at 15:17 UTC · Free test · report pt_5f5ed1b30fbe
Grade
A
90/100
Performance93/100
Structure86/100

12 audit(s) passed, 4 need work

First byte (TTFB)471 msmeasured from this server
Fully loaded1.33 sfirst byte + slowest asset
Requests15document + assets
Page weight507.3 KBcompressed transfer
HTML document24.6 KBgzip
ProtocolHTTP/3cloudflare
Third-party95.7 KBother hosts

Where the first byte went

  • DNS lookup 84 ms 18%
  • TCP connect 1 ms 0%
  • Server wait 386 ms 82%

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 53% of 4,999 pages tested here471 ms against a median of 448 ms
Page weightlighter than 58% of 4,999 pages tested here507.3 KB against a median of 650.5 KB
Fully loadedfaster than 81% of 4,999 pages tested here1.33 s against a median of 1.84 s
Requestssends fewer requests than 83% of 4,999 pages tested here15 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 arrived in 471 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 507.3 KB over 15 request(s), which is lean. Javascript files are 51% 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.
  • The largest element painted at 1.59 s, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.094), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 42 ms in total, which is not enough to feel.

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.

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 paint1.59 sgood is under 2.5 s
Cumulative layout shift0.094under 0.1 is stable
Total blocking time42 mslong tasks during load
First contentful paint1.32 sfirst content on screen
Browser page weight2.30 MB62 request(s), scripts included
Largest contentful paint1.59 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.094
Goodgood under 0.1, poor over 0.25
Total blocking time42 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 6 requests
259.3 KB 51%
Css 1 request
202.1 KB 40%
Images 6 requests
21.1 KB 4%
Other 1 request
220 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 471 ms. Of that, 386 ms was the server thinking and 85 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

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

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.

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

OTHERwww.xv-ru.com/manifest.json
856 ms
JAVASCRIPTverifycdn.agego.com/v2/verify.js
631 ms
IMAGESwww.xv-ru.com/static-files/v3/img/skins/default/logo…
592 ms
IMAGESwww.xv-ru.com/static-files/v3/img/skins/default/logo…
583 ms
JAVASCRIPTwww.xv-ru.com/static-files/v-3cdeb4e83b5/v3/js/skins…
571 ms
JAVASCRIPTwww.xv-ru.com/static-files/v3/js/libs/jquery.min.js
569 ms
IMAGESwww.xv-ru.com/static-files/img/lightbox/lightbox-bla…
568 ms
IMAGESwww.xv-ru.com/static-files/v3/img/skins/default/logo…
561 ms
CSSwww.xv-ru.com/static-files/v-b95aa40ff47/v3/css/defa…
560 ms
JAVASCRIPTwww.xv-ru.com/static-files/v-9a4f1a51a62/v3/js/skins…
559 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://www.xv-ru.com/manifest.jsonother200856 ms220 B
https://verifycdn.agego.com/v2/verify.js 3rd partyjavascript200631 ms95.7 KB
https://www.xv-ru.com/static-files/v3/img/skins/default/logo/events/xvideos.black.halloween.svgimages200592 ms11.1 KB
https://www.xv-ru.com/static-files/v3/img/skins/default/logo/xv.white.32.pngimages200583 ms1.5 KB
https://www.xv-ru.com/static-files/v-3cdeb4e83b5/v3/js/skins/min/default.sfw.static.jsjavascript200571 ms10.9 KB
https://www.xv-ru.com/static-files/v3/js/libs/jquery.min.jsjavascript200569 ms32.8 KB
https://www.xv-ru.com/static-files/img/lightbox/lightbox-blank.gifimages200568 ms43 B
https://www.xv-ru.com/static-files/v3/img/skins/default/logo/xv.white.svgimages200561 ms550 B
https://www.xv-ru.com/static-files/v-b95aa40ff47/v3/css/default/main.csscss200560 ms202.1 KB
https://www.xv-ru.com/static-files/v-9a4f1a51a62/v3/js/skins/min/default.footer.static.jsjavascript200559 ms10.0 KB
https://www.xv-ru.com/static-files/v3/img/skins/default/logo/xv.white.180.pngimages200559 ms6.9 KB
https://www.xv-ru.com/static-files/v3/img/skins/default/logo/xv.white.16.pngimages200559 ms973 B
https://www.xv-ru.com/static-files/v3/js/skins/min/require.static.jsjavascript200555 ms6.4 KB
https://www.xv-ru.com/static-files/v-62054a1c5c0/v3/js/skins/min/default.header.static.jsjavascript200548 ms103.5 KB
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.