www.gov.cn speed test — 20 Oct 2026

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

https://www.gov.cn/

20 October 2026 at 13:09 UTC · Free test · report pt_6cdcc4470720
Grade
C
79/100
Performance91/100
Structure62/100

9 audit(s) passed, 7 need work

First byte (TTFB)423 msmeasured from this server
Fully loaded1.98 sfirst byte + slowest asset
Requests26document + assets
Page weight1.04 MBcompressed transfer
HTML document14.5 KBgzip
ProtocolHTTP/2server not sent

Where the first byte went

  • DNS lookup 85 ms 20%
  • TCP connect 98 ms 23%
  • Server wait 240 ms 57%

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 53% of 4,999 pages tested here423 ms against a median of 449 ms
Page weightheavier than 64% of 4,999 pages tested here1.04 MB against a median of 650.3 KB
Fully loadedslower than 56% of 4,999 pages tested here1.98 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 423 ms. That is workable, and the cheapest win left is caching or a warmer connection.
  • The page transfers 1.04 MB over 26 request(s). Images files are 99% 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 1.39 s, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.001), so nothing jumps under the reader's cursor.

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.gov.cn
Mobile 390 × 844 · 192.4 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 paint1.39 sgood is under 2.5 s
Cumulative layout shift0.001under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint896 msfirst content on screen
Browser page weight1.59 MB84 request(s), scripts included
Largest contentful paint1.39 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.001
Goodgood under 0.1, poor over 0.25
Total blocking timenone over 50 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests
1.02 MB 99%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 423 ms. Of that, 240 ms was the server thinking and 183 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.

Image delivery and format

high impact

3 image(s) over 200 KB and 3 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Render-blocking resources

high impact

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

TLS certificate validity

high impact

The certificate for www.gov.cn has 19 day(s) left.

Fix: Renew automatically (certbot with a working renewal timer) and alert on the certificate, not on the renew command, so a silent failure is caught weeks before a browser warning.

Total page weight

medium impact

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

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

Waterfall

Slowest requests

IMAGESwww.gov.cn/images/gtrs_logo_lt.png
1.55 s
IMAGESwww.gov.cn/images/gtrs_index_gwywls.png
1.53 s
IMAGESwww.gov.cn/images/t1_3.png
1.26 s
IMAGESwww.gov.cn/images/gtrs_newsearch.png
1.24 s
IMAGESwww.gov.cn/images/newlogo19ysp_rt.png
1.19 s
IMAGESwww.gov.cn/images/t2_2.png
1.17 s
IMAGESwww.gov.cn/images/20240913tuixiu.png
1.17 s
IMAGESwww.gov.cn/images/newlogo19ysp_lt.png
1.17 s
IMAGESwww.gov.cn/images/gtrs_logo_rt.png
1.17 s
IMAGESwww.gov.cn/images/20240607chusheng.png
1.16 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.gov.cn/images/gtrs_logo_lt.pngimages2001.55 s7.5 KB
https://www.gov.cn/images/gtrs_index_gwywls.pngimages2001.53 s5.3 KB
https://www.gov.cn/images/t1_3.pngimages2001.26 s2.2 KB
https://www.gov.cn/images/gtrs_newsearch.pngimages2001.24 s807 B
https://www.gov.cn/images/newlogo19ysp_rt.pngimages2001.19 s13.0 KB
https://www.gov.cn/images/t2_2.pngimages2001.17 s3.1 KB
https://www.gov.cn/images/20240913tuixiu.pngimages2001.17 s1.9 KB
https://www.gov.cn/images/newlogo19ysp_lt.pngimages2001.17 s15.2 KB
https://www.gov.cn/images/gtrs_logo_rt.pngimages2001.17 s9.9 KB
https://www.gov.cn/images/20240607chusheng.pngimages2001.16 s2.6 KB
https://www.gov.cn/images/20241121zxtc_ico.pngimages2001.16 s1.8 KB
https://www.gov.cn/images/gwyhlwdc20250623.pngimages2001.16 s21.2 KB
https://www.gov.cn/images/t2_1.pngimages2001.16 s2.1 KB
https://www.gov.cn/images/20241121qyyg_ico.pngimages2001.16 s1.7 KB
https://www.gov.cn/images/20241121jyfz_ico.pngimages2001.16 s1.4 KB
https://www.gov.cn/images/gtrs_index_dxdcyj.jpgimages2001.16 s25.4 KB
https://www.gov.cn/images/20240913jiuyi.pngimages2001.15 s1.5 KB
https://www.gov.cn/images/t1_2.pngimages2001.15 s2.7 KB
https://www.gov.cn/shouye/datu/202610/W020261019715790356875_ORIGIN.jpgimages2001.15 s201.4 KB
https://www.gov.cn/shouye/zhengcejiedu/202610/W020261020520640450337_ORIGIN.jpgimages2001.15 s59.0 KB
https://www.gov.cn/shouye/jyzjhygq/202610/W020261020709942056634_ORIGIN.pngimages2001.15 s33.1 KB
https://www.gov.cn/images/gtrs_index_gywzxd.gifimages2001.14 s20.0 KB
https://www.gov.cn/shouye/datu/202610/W020261013554934432728.jpgimages2001.14 s294.5 KB
https://www.gov.cn/shouye/datu/202610/W020261016779111395388_ORIGIN.jpgimages2001.13 s319.5 KB
https://www.gov.cn/images/gtrs_newshouqi.pngimages2001.13 s409 B
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.