tiktokio.com speed test — 20 Oct 2026

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

https://tiktokio.com/

20 October 2026 at 13:02 UTC · Free test · report pt_aff1edee9c49

Re-test this page Test your own site

Grade

97/100

Performance100/100

Structure92/100

14 audit(s) passed, 2 need work

First byte (TTFB)175 msmeasured from this server

Fully loaded1.26 sfirst byte + slowest asset

Requests26document + assets

Page weight43.2 KBcompressed transfer

HTML document29.4 KBzstd

ProtocolHTTP/3cloudflare

Where the first byte went

DNS lookup 70 ms 40%
TCP connect 17 ms 10%
Server wait 88 ms 50%

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 96% of 4,999 pages tested here175 ms against a median of 449 ms

Page weightlighter than 92% of 4,999 pages tested here43.2 KB against a median of 650.5 KB

Fully loadedfaster than 85% of 4,999 pages tested here1.26 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 server answered in 175 ms, which is fast: almost all of the wait is the page itself, not the host.
The page transfers 43.2 KB over 26 request(s). Images files are 32% of it, so resize and recompress the largest images before anything else.
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 532 ms, inside the 2.5 s Google calls good.
Layout shift is 0.102 (good is under 0.1): something without a reserved size is loading late - an image, an ad, or a font swap.
The main thread was blocked for 309 ms, so taps and scrolling wait while scripts run.

Fix first: Render-blocking resources - 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.

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 tiktokio.com — **Mobile** 390 × 844 · 72.7 KB · page is 6000 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 paint532 msgood is under 2.5 s

Cumulative layout shift0.102under 0.1 is stable

Total blocking time309 mslong tasks during load

First contentful paint532 msfirst content on screen

Browser page weight1.30 MB142 request(s), scripts included

Failed requests5blocked or unreachable

Largest contentful paint532 ms

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.102

Needs improvementgood under 0.1, poor over 0.25

Total blocking time309 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

13.9 KB 32%

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

Top issues

Render-blocking resources

high impact

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