Performance
· 15 checks — Lighthouse + waterfall + sustainability rolled into one auditable list.Performance-focused optimization plan with CWV assessment, top offenders, and time estimates
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
2.27 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.35 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
0 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.27 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
2.35 s
Page Load Progression
375 ms 750 ms 1.1 s 1.5 s
1.9 s
2.2 s
2.6 s
3.0 sDThird-Party ImpactAction100% third-party, 0 ms blockingFIX
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
A+Page Weight Budget197 KB transferred, 24 requestsPASS
A+Text CompressionAll text resources are compressedPASS
A+Image Optimization8 images, 0 KB saveablePASS
A+JS Execution Cost141ms total JS executionPASS
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://www.wechat.com/en | 71ms | 4ms | 0ms | 3rd |
| Unattributable | 70ms | 38ms | 0ms | 3rd |
A+Font LoadingNo web fonts (system fonts)PASS
A+JS Bundles3 scripts, 26 KB unusedPASS
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://sgnewres.wechat.com/t/wx_fed/base/wechat/wechat-main-page/wechat-portal/res/_nuxt/CDzkMDRi.js | 77 KB | 26 KB (36%) | ✓ | 3rd |
| https://sgnewres.wechat.com/t/wx_fed/base/wechat/wechat-main-page/wechat-portal/res/_nuxt/CQ-OdwOk.js | 39 KB | — | ✓ | 3rd |
| https://sgnewres.wechat.com/t/wx_fed/base/wechat/wechat-main-page/wechat-portal/res/_nuxt/BXL6JXhz.js | 3 KB | — | ✓ | 3rd |
Consider code splitting or tree shaking to reduce unused code.
This bundle has high unused code — code-split or tree-shake to ship only what executes.
Source: web.dev / Lighthouse coverage
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource HintsNo optimization neededPASS
APage Weight Inventory24 resources · 197 KB · 26 KB savings availablePASS
~26.4 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 24 resources | 197.3 KiB | ||||||
Network Waterfall24 requests over 1719msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
www.wechat.com www.wechat.com | Other | 71ms | 36 KB | — | ¥4/mo | Optional |
Unattributable Unattributable | Other | 70ms | 0 KB | — | ¥3/mo | Optional |
100% of JavaScript execution time is spent on third-party scripts. Consider auditing which scripts are essential.
When third-party JS execution time exceeds your own, performance gains from frontend work are capped by code you don't own.
Learn more ▾ ▴
Every millisecond of third-party JS competes with your own for main-thread time. If their share is bigger than yours, optimization on your code base barely moves the needle. Audit, defer, or remove third-parties before further frontend optimization. Use Lighthouse's third-party audit to identify the worst offenders.
Source: web.dev