www.people.com.cn speed test — 20 Oct 2026

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

https://www.people.com.cn/

20 October 2026 at 13:03 UTC · Free test · report pt_d29f10bf9b65
Grade
B
87/100
Performance91/100
Structure80/100

11 audit(s) passed, 5 need work

First byte (TTFB)498 msmeasured from this server
Fully loaded1.86 sfirst byte + slowest asset
Requests26document + assets
Page weight204.0 KBcompressed transfer
HTML document36.7 KBgzip
ProtocolHTTP/2wswaf

Where the first byte went

  • DNS lookup 108 ms 22%
  • TCP connect 74 ms 15%
  • Server wait 316 ms 63%

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 55% of 4,999 pages tested here498 ms against a median of 448 ms
Page weightlighter than 79% of 4,999 pages tested here204.0 KB against a median of 650.5 KB
Fully loadedslower than 51% of 4,999 pages tested here1.86 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 498 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 204.0 KB over 26 request(s). Images files are 82% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives gzip-compressed.
  • It runs over HTTP/2, so the assets share a connection instead of opening one each.
  • The largest element painted at 896 ms, inside the 2.5 s Google calls good.
  • Layout shift is 0.357 (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 1 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 paint896 msgood is under 2.5 s
Cumulative layout shift0.357under 0.1 is stable
Total blocking time1 mslong tasks during load
First contentful paint608 msfirst content on screen
Browser page weight8.74 MB170 request(s), scripts included
Largest contentful paint896 ms
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.357
Poorgood under 0.1, poor over 0.25
Total blocking time1 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests
167.4 KB 82%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 498 ms. Of that, 316 ms was the server thinking and 182 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

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

Cache static assets

medium impact

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

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

IMAGESwww.people.com.cn/img/2020peopleindex/img/dyz/17.png
1.36 s
IMAGESwww.people.com.cn/img/2020peopleindex/img/dyz/04.png
1.23 s
IMAGESwww.people.com.cn/img/2020peopleindex/img/dyz/12.png
1.21 s
IMAGESwww.people.com.cn/img/2020peopleindex/img/dyz/16.png
1.21 s
IMAGESwww.people.com.cn/img/2020peopleindex/img/dyz/10.png
1.20 s
IMAGESwww.people.com.cn/img/2020peopleindex/img/dyz/08.png
1.20 s
IMAGESwww.people.com.cn/img/2020peopleindex/img/dyz/07.png
1.20 s
IMAGESwww.people.com.cn/img/2020peopleindex/img/dyz/06.png
1.20 s
IMAGESwww.people.com.cn/img/2020peopleindex/img/dyz/05.png
1.19 s
IMAGESwww.people.com.cn/img/2020peopleindex/img/dyz/11.png
1.19 s

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.people.com.cn/img/2020peopleindex/img/dyz/17.pngimages2001.36 s3.4 KB
https://www.people.com.cn/img/2020peopleindex/img/dyz/04.pngimages2001.23 s2.4 KB
https://www.people.com.cn/img/2020peopleindex/img/dyz/12.pngimages2001.21 s2.6 KB
https://www.people.com.cn/img/2020peopleindex/img/dyz/16.pngimages2001.21 s2.9 KB
https://www.people.com.cn/img/2020peopleindex/img/dyz/10.pngimages2001.20 s2.4 KB
https://www.people.com.cn/img/2020peopleindex/img/dyz/08.pngimages2001.20 s1.9 KB
https://www.people.com.cn/img/2020peopleindex/img/dyz/07.pngimages2001.20 s3.1 KB
https://www.people.com.cn/img/2020peopleindex/img/dyz/06.pngimages2001.20 s2.3 KB
https://www.people.com.cn/img/2020peopleindex/img/dyz/05.pngimages2001.19 s2.3 KB
https://www.people.com.cn/img/2020peopleindex/img/dyz/11.pngimages2001.19 s2.5 KB
https://www.people.com.cn/img/2020peopleindex/img/dyz/02.pngimages2001.19 s2.1 KB
https://www.people.com.cn/img/2020peopleindex/img/xjp.pngimages2001.18 s74.3 KB
https://www.people.com.cn/img/2020peopleindex/img/dyz/09.pngimages2001.18 s2.3 KB
https://www.people.com.cn/img/2020peopleindex/img/dyz/20.pngimages2001.18 s1.4 KB
https://www.people.com.cn/img/2020peopleindex/img/dyz/19.pngimages2001.17 s1.6 KB
https://www.people.com.cn/img/2020peopleindex/img/dyz/03.pngimages2001.17 s3.1 KB
https://www.people.com.cn/img/2020peopleindex/img/dyz/14.pngimages2001.17 s2.1 KB
https://www.people.com.cn/img/2020peopleindex/img/dyz/01.pngimages2001.17 s1.9 KB
https://www.people.com.cn/img/2020peopleindex/img/arrow2.pngimages2001.16 s232 B
https://www.people.com.cn/img/2020peopleindex/img/2025gb/databaseh.pngimages2001.16 s35.3 KB
https://www.people.com.cn/img/2020peopleindex/img/t_logo1.pngimages2001.16 s8.6 KB
https://www.people.com.cn/img/2020peopleindex/img/dyz/taiy4.pngimages2001.16 s1.4 KB
https://www.people.com.cn/img/2020peopleindex/img/dyz/21.pngimages2001.16 s1.5 KB
https://www.people.com.cn/img/2020peopleindex/img/dyz/15.pngimages2001.15 s2.2 KB
https://www.people.com.cn/img/2020peopleindex/img/dyz/13.pngimages2001.14 s3.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.