app.toutiao.com speed test — 20 Oct 2026

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

https://app.toutiao.com/

20 October 2026 at 13:18 UTC · Free test · report pt_ce8d3158e0fd
Grade
C
76/100
Performance72/100
Structure82/100

12 audit(s) passed, 4 need work

First byte (TTFB)1.23 smeasured from this server
Fully loaded1.58 sfirst byte + slowest asset
Requests5document + assets
Page weight209.6 KBcompressed transfer
HTML document1.8 KBbr
ProtocolHTTP/3Tengine
Third-party207.8 KBother hosts

Where the first byte went

  • DNS lookup 240 ms 19%
  • TCP connect 66 ms 5%
  • Server wait 927 ms 75%

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 92% of 4,999 pages tested here1.23 s against a median of 448 ms
Page weightlighter than 79% of 4,999 pages tested here209.6 KB against a median of 650.5 KB
Fully loadedfaster than 65% of 4,999 pages tested here1.58 s against a median of 1.84 s
Requestssends fewer requests than 93% of 4,999 pages tested here5 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 1.23 s. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 209.6 KB over 5 request(s), which is lean. Javascript files are 95% 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.
  • 99% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The largest element took 6.24 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
  • The main thread was blocked for 8 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 paint6.24 sgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking time8 mslong tasks during load
First contentful paint4.56 sfirst content on screen
Browser page weight161.34 MB14 request(s), scripts included
Failed requests3blocked or unreachable
Largest contentful paint6.24 s
Poorgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking time8 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 2 requests
199.0 KB 95%
Images 1 request
7.7 KB 4%
Css 1 request
1.1 KB 1%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1233 ms. Of that, 927 ms was the server thinking and 306 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.

Cache static assets

medium impact

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

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: 834.6b60b3d6.js (195.5 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

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

Waterfall

Slowest requests

JAVASCRIPTlf-toutiao-ug-dns.toutiaocdn.com/obj/toutiao-ug-tos/tt_download_page/st…
348 ms
CSSlf-toutiao-ug-dns.toutiaocdn.com/obj/toutiao-ug-tos/tt_download_page/st…
341 ms
IMAGESlf-toutiao-ug-dns.toutiaocdn.com/obj/toutiao-ug-tos/tt_download_page/to…
292 ms
JAVASCRIPTlf-toutiao-ug-dns.toutiaocdn.com/obj/toutiao-ug-tos/tt_download_page/st…
285 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://lf-toutiao-ug-dns.toutiaocdn.com/obj/toutiao-ug-tos/tt_download_page/static/js/834.6b60b3d6.js 3rd partyjavascript200348 ms195.5 KB
https://lf-toutiao-ug-dns.toutiaocdn.com/obj/toutiao-ug-tos/tt_download_page/static/css/main.f5119bd6.css 3rd partycss200341 ms1.1 KB
https://lf-toutiao-ug-dns.toutiaocdn.com/obj/toutiao-ug-tos/tt_download_page/toutiao_favicon.ico 3rd partyimages200292 ms7.7 KB
https://lf-toutiao-ug-dns.toutiaocdn.com/obj/toutiao-ug-tos/tt_download_page/static/js/main.385dd7e5.js 3rd partyjavascript200285 ms3.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.