anikototv.to speed test — 20 Oct 2026

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

https://anikototv.to/

20 October 2026 at 15:35 UTC · Free test · report pt_6466bba216c8
Grade
A
92/100
Performance94/100
Structure88/100

13 audit(s) passed, 3 need work

First byte (TTFB)408 msmeasured from this server
Fully loaded848 msfirst byte + slowest asset
Requests9document + assets
Page weight212.5 KBcompressed transfer
HTML document8.7 KBzstd
ProtocolHTTP/3cloudflare
Third-party21.3 KBother hosts

Where the first byte went

  • DNS lookup 97 ms 24%
  • TCP connect 41 ms 10%
  • Server wait 271 ms 66%

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 bytefaster than 55% of 4,999 pages tested here408 ms against a median of 449 ms
Page weightlighter than 79% of 4,999 pages tested here212.5 KB against a median of 650.5 KB
Fully loadedfaster than 94% of 4,999 pages tested here848 ms against a median of 1.84 s
Requestssends fewer requests than 89% of 4,999 pages tested here9 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 408 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 212.5 KB over 9 request(s), which is lean. Css files are 75% of it, so split the stylesheet so the first screen does not download the whole site.
  • The HTML itself arrives zstd-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • The largest element painted at 608 ms, inside the 2.5 s Google calls good.
  • The main thread was blocked for 31 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.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Mobile screenshot of anikototv.to
Mobile 390 × 844 · 155.2 KB · page is 929 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 paint608 msgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time31 mslong tasks during load
First contentful paint608 msfirst content on screen
Browser page weight1.07 MB17 request(s), scripts included
Failed requests1blocked or unreachable
Largest contentful paint608 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time31 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Css 5 requests
159.4 KB 75%
Other 3 requests
44.4 KB 21%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 408 ms. Of that, 271 ms was the server thinking and 138 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

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

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

CSSfonts.googleapis.com/css2
440 ms
OTHERanikototv.to/AnikotoTheme/assets/images/favicon.png
433 ms
CSScdnjs.cloudflare.com/ajax/libs/tooltipster/4.0.0/css/toolti…
428 ms
CSSanikototv.to/AnikotoTheme/assets/css/style.css
408 ms
OTHERanikototv.to/AnikotoTheme/assets/images/logo.png
398 ms
CSScdnjs.cloudflare.com/ajax/libs/Swiper/5.4.4/css/swiper.min.css
392 ms
OTHERanikototv.to/anikoto/manifest.json
391 ms
CSScdnjs.cloudflare.com/ajax/libs/font-awesome/6.1.1/css/all.m…
390 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://fonts.googleapis.com/css2?family=Bebas+Neue&family=Nunito:wght@400;500;600;700&display=swap 3rd partycss200440 ms272 B
https://anikototv.to/AnikotoTheme/assets/images/favicon.pngother200433 ms17.6 KB
https://cdnjs.cloudflare.com/ajax/libs/tooltipster/4.0.0/css/tooltipster.bundle.min.css 3rd partycss200428 ms932 B
https://anikototv.to/AnikotoTheme/assets/css/style.css?v=5.37css200408 ms138.1 KB
https://anikototv.to/AnikotoTheme/assets/images/logo.pngother200398 ms26.5 KB
https://cdnjs.cloudflare.com/ajax/libs/Swiper/5.4.4/css/swiper.min.css 3rd partycss200392 ms3.5 KB
https://anikototv.to/anikoto/manifest.jsonother200391 ms246 B
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.1.1/css/all.min.css 3rd partycss200390 ms16.6 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.