www.tiktok.com speed test — 20 Oct 2026

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

https://www.tiktok.com/

20 October 2026 at 12:23 UTC · Free test · report pt_7d9b0755527f

Re-test this page Test your own site

Grade

86/100

Performance89/100

Structure82/100

11 audit(s) passed, 5 need work

First byte (TTFB)470 msmeasured from this server

Fully loaded1.65 sfirst byte + slowest asset

Requests26document + assets

Page weight1.30 MBcompressed transfer

HTML document77.8 KBbr

ProtocolHTTP/3nginx

Third-party1.22 MBother hosts

Where the first byte went

DNS lookup 50 ms 11%
TCP connect 36 ms 8%
Server wait 384 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 52% of 4,999 pages tested here470 ms against a median of 448 ms

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

Fully loadedfaster than 60% of 4,999 pages tested here1.65 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 arrived in 470 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 1.30 MB over 26 request(s). Javascript files are 94% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
94% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element painted at 1.87 s, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.015), so nothing jumps under the reader's cursor.
The main thread was blocked for 322 ms, so taps and scrolling wait while scripts run.

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 www.tiktok.com — **Mobile** 390 × 844 · 234.2 KB · page is 1065 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 paint1.87 sgood is under 2.5 s

Cumulative layout shift0.015under 0.1 is stable

Total blocking time322 mslong tasks during load

First contentful paint1.02 sfirst content on screen

Browser page weight6.45 MB251 request(s), scripts included

Largest contentful paint1.87 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.015

Goodgood under 0.1, poor over 0.25

Total blocking time322 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 25 requests

1.22 MB 94%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 470 ms. Of that, 384 ms was the server thinking and 86 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.

Total page weight

medium impact

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

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

Third-party weight

medium impact

2 third-party host(s) serve 1.22 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.

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: 75627.55f7bcc1.js (260.1 KB)

Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.

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.