www.wechat.com/en speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 13:02 UTC. Grade E (57/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 97 ms 6%
- TCP connect 1.08 s 65%
- Server wait 480 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
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.66 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 226.5 KB over 8 request(s), which is lean. Javascript files are 81% 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/2, so the assets share a connection instead of opening one each.
- 84% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
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.
The headless browser did not capture this page when the test ran, so only the server measurements are shown.
Page weight by type
What the page is made of
Transfer size, compressed as sent. 8 request(s) in total, 226.5 KB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 1661 ms. Of that, 480 ms was the server thinking and 1181 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 impact3 render-blocking resource(s) in the document head (2 script(s), 1 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.
Avoid extra redirects
medium impact2 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
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
| Request | Type | Status | Time | Size |
|---|---|---|---|---|
| https://www.wechat.com/en/%2311e4853f-c516-4e74-bd75-b4c716c464bf-b | other | 0 | 10.00 s | 0 B |
| https://newres.wechat.com/t/fed_upload/25d133b0-63d9-4102-857c-5cc84c752232/NTI4MWU5.ico 3rd party | images | 200 | 427 ms | 827 B |
| https://sgnewres.wechat.com/t/wx_fed/base/wechat/wechat-main-page/wechat-portal/res/_nuxt/cvw5q-u1.js 3rd party | javascript | 200 | 398 ms | 45.8 KB |
| https://sgnewres.wechat.com/t/wx_fed/base/wechat/wechat-main-page/wechat-portal/res/_nuxt/logo.CNA5TJpi.svg 3rd party | images | 200 | 382 ms | 5.7 KB |
| https://sgnewres.wechat.com/t/wx_fed/base/wechat/wechat-main-page/wechat-portal/res/_nuxt/entry.Dq2oYbhO.css 3rd party | css | 200 | 375 ms | 859 B |
| https://sgnewres.wechat.com/t/wx_fed/base/wechat/wechat-main-page/wechat-portal/res/_nuxt/CoWwRVd0-legacy.js 3rd party | javascript | 200 | 361 ms | 61.5 KB |
| https://sgnewres.wechat.com/t/wx_fed/base/wechat/wechat-main-page/wechat-portal/res/_nuxt/O0QPq69Y.js 3rd party | javascript | 200 | 359 ms | 76.4 KB |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.