www.uc.cn speed test — 20 Oct 2026

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

https://www.uc.cn/

20 October 2026 at 13:55 UTC · Free test · report pt_e0dc5f78faa6

Re-test this page Test your own site

Grade

62/100

Performance52/100

Structure77/100

11 audit(s) passed, 5 need work

First byte (TTFB)2.13 smeasured from this server

Fully loaded4.81 sfirst byte + slowest asset

Requests15document + assets

Page weight934.5 KBcompressed transfer

HTML document100.0 KBgzip

ProtocolHTTP/3Tengine

Third-party834.6 KBother hosts

Where the first byte went

DNS lookup 280 ms 13%
TCP connect 1.24 s 58%
Server wait 613 ms 29%

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 98% of 4,999 pages tested here2.13 s against a median of 448 ms

Page weightheavier than 60% of 4,999 pages tested here934.5 KB against a median of 650.3 KB

Fully loadedslower than 90% of 4,999 pages tested here4.81 s against a median of 1.84 s

Requestssends fewer requests than 83% of 4,999 pages tested here15 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 2.13 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 934.5 KB over 15 request(s), which is lean. Images files are 60% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
89% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element took 3.40 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.

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.uc.cn — **Mobile** 390 × 844 · 218.5 KB · page is 2121 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 paint3.40 sgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking timenone over 50 mslong tasks during load

First contentful paint980 msfirst content on screen

Browser page weight7.38 MB87 request(s), scripts included

Largest contentful paint3.40 s

Needs improvementgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

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 5 requests

562.5 KB 60%

Javascript 7 requests

267.8 KB 29%

Css 2 requests

4.3 KB 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 2130 ms. Of that, 613 ms was the server thinking and 1516 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 934.5 KB across 15 request(s), with the document itself at 100.0 KB.

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

Third-party weight

medium impact

3 third-party host(s) serve 834.6 KB 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.

HTML document size

medium impact

The document transfers 100.0 KB. A bloated document delays every other request, because nothing else can start until it is parsed.

Fix: Paginate long listings, move repeated markup into a template, and stop inlining large data URIs into the HTML.

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.

Waterfall

Slowest requests

IMAGESpeco-img.uc.cn/ulive_fe/upload/2025/d64b969ae4916ab82…

2.68 s

IMAGESpeco-img.uc.cn/ulive_fe/upload/2025/4283b312b974294d1…

1.97 s

IMAGESpeco-img.uc.cn/ulive_fe/upload/2025/2df9d242dfa2aea65…

1.83 s

IMAGESpeco-img.uc.cn/ulive_fe/upload/2025/755786d343870a380…

1.04 s