Performance
· 17 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.
7.01 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
25.41 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
261 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.007
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
31.56 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.
26.52 s
Page Load Progression
FPage Weight BudgetAction12.8 MB transferred, 155 requestsFIX
Subset fonts to include only used characters, or switch to system font stacks.
Font payload is large — subset to used glyphs only, or fall back to system fonts (zero load time).
Source: web.dev font loading
Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.
Image bandwidth is high — modern formats (WebP/AVIF) and resizing typically cut it 50%+.
Source: web.dev
Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.
Source: web.dev
DThird-Party ImpactAction100% third-party, 0 ms blockingFIX
FJS Execution CostAction8086ms total JS executionFIX
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://www.tencent.com/en-us/ | 3439ms | 113ms | 9ms | 3rd |
| https://www.tencent.com/js/jquery.min.js | 1446ms | 395ms | 67ms | 3rd |
| Unattributable | 1347ms | 6ms | 0ms | 3rd |
| https://www.googletagmanager.com/gtm.js?id=GTM-TQP47XHV | 636ms | 240ms | 195ms | 3rd |
| https://cdn-go.cn/aegis/aegis-sdk/latest/aegis.min.js | 611ms | 269ms | 61ms | 3rd |
| https://www.tencent.com/js/swiper.min.js | 390ms | 193ms | 65ms | 3rd |
| https://www.tencent.com/ | 217ms | 127ms | 8ms | 3rd |
DPage Weight InventoryAction155 resources · 12.8 MB · 279 KB savings availableFIX
~278.5 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 155 resources | 12.8 MiB | ||||||
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
CJS BundlesAction24 scripts, 279 KB unusedREVIEW
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://www.googletagmanager.com/gtm.js?id=GTM-TQP47XHV | 0 KB | 73 KB (66%) | ✓ | 3rd |
| https://www.googletagmanager.com/gtm.js?id=GTM-TQP47XHV | 112 KB | 73 KB (66%) | ✓ | 3rd |
| https://cdn-go.cn/aegis/aegis-sdk/latest/aegis.min.js | 39 KB | 24 KB (60%) | ✓ | 3rd |
| https://cdn-go.cn/aegis/aegis-sdk/latest/aegis.min.js | 0 KB | 24 KB (60%) | ✓ | 3rd |
| https://www.tencent.com/js/swiper.min.js | 43 KB | 21 KB (50%) | ✓ | 3rd |
| https://www.tencent.com/js/swiper.min.js | 0 KB | 21 KB (50%) | ✓ | 3rd |
| https://www.tencent.com/js/jquery.min.js | 37 KB | 21 KB (57%) | ✓ | 3rd |
| https://www.tencent.com/js/jquery.min.js | 0 KB | 21 KB (57%) | ✓ | 3rd |
| https://www.tencent.com/js/tencent.js | 6 KB | — | ✗ | 3rd |
| https://www.tencent.com/js/qrcode.js | 12 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
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
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
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
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
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
A+Text CompressionAll text resources are compressedPASS
A+Image Optimization46 images, 0 KB saveablePASS
A+Font Loading10 fonts (7482 KB)PASS
Web fonts
10
7482 KB total
Render-blocking
0
of 10
Dominant font-display
swap
Most common across fonts
Font loading timeline
- Convert to woff2 for ~30% smaller file size
- Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
- Convert to woff2 for ~30% smaller file size
- Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
- Convert to woff2 for ~30% smaller file size
- Convert to woff2 for ~30% smaller file size
- Convert to woff2 for ~30% smaller file size
- Convert to woff2 for ~30% smaller file size
- Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
- Subset this font — over 100 KB suggests Latin Extended or full glyph coverage that most pages don't need
Optimization checklist
- Preload critical fonts (priority=high)
- Use woff2 format for all fonts
- Set font-display to swap, optional, or fallback
- Subset large fonts (≤100 KB each)
Fixing the unchecked items could save ~3806 KB and ~7612 ms
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource HintsNo optimization neededPASS
A+Render-Blocking ResourcesNo render-blocking resources detectedPASS
A+Third-Party ResourcesNo third-party resources detectedPASS
Network Waterfall155 requests over 11614msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
www.tencent.com www.tencent.com | Other | 3439ms | 13 KB | — | ¥170/mo | Costly |
www.tencent.com www.tencent.com | Other | 1446ms | 0 KB | 57% | ¥71/mo | Costly |
Unattributable Unattributable | Other | 1347ms | 0 KB | — | ¥66/mo | Costly |
Google Tag Manager www.googletagmanager.com | Tag Manager | 636ms | 0 KB | 66% | ¥31/mo | Costly |
cdn-go.cn cdn-go.cn | Other | 611ms | 0 KB | 60% | ¥30/mo | Costly |
www.tencent.com www.tencent.com | Other | 390ms | 0 KB | 50% | ¥19/mo | Costly |
www.tencent.com www.tencent.com | Other | 217ms | 13 KB | — | ¥11/mo | Costly |
These scripts may cost more than they're worth
- www.tencent.com adds 3439ms and costs ~¥170/month
- www.tencent.com adds 1446ms and costs ~¥71/month
- Unattributable adds 1347ms and costs ~¥66/month
- Google Tag Manager adds 636ms and costs ~¥31/month
- cdn-go.cn adds 611ms and costs ~¥30/month
- www.tencent.com adds 390ms and costs ~¥19/month
- www.tencent.com adds 217ms and costs ~¥11/month
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
www.tencent.com takes 3439ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
www.tencent.com takes 1446ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
57% of www.tencent.com's code is unused. The script may be loading features you don't use.
Bundle has high unused-code ratio — tree-shaking and route-splitting recover the wasted bytes.
Source: web.dev
Unattributable takes 1347ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
Google Tag Manager takes 636ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
66% of Google Tag Manager's code is unused. The script may be loading features you don't use.
Bundle has high unused-code ratio — tree-shaking and route-splitting recover the wasted bytes.
Source: web.dev
cdn-go.cn takes 611ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
60% of cdn-go.cn's code is unused. The script may be loading features you don't use.
Bundle has high unused-code ratio — tree-shaking and route-splitting recover the wasted bytes.
Source: web.dev
www.tencent.com takes 390ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev
50% of www.tencent.com's code is unused. The script may be loading features you don't use.
Bundle has high unused-code ratio — tree-shaking and route-splitting recover the wasted bytes.
Source: web.dev
www.tencent.com takes 217ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.
This script has high main-thread execution time — optimize hot paths or defer.
Source: web.dev