Performance
· 16 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.42 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.50 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
4 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.89 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.51 s
Page Load Progression
453 ms 907 ms
1.4 s
1.8 s
2.3 s 2.7 s 3.2 s
3.6 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.
CJS Execution CostAction1811ms total JS executionREVIEW
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://www.wikipedia.org/ | 1642ms | 11ms | 3ms | 3rd |
| Unattributable | 169ms | 11ms | 0ms | 3rd |
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
A+Page Weight Budget277 KB transferred, 10 requestsPASS
A+Text CompressionAll text resources are compressedPASS
AImage Optimization4 images, 0 KB saveablePASS
A+Font LoadingNo web fonts (system fonts)PASS
A+JS Bundles2 scripts, 0 KB unusedPASS
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://www.wikipedia.org/portal/wikipedia.org/assets/js/index-90de98612a.js | 10 KB | — | ✓ | 3rd |
| https://www.wikipedia.org/portal/wikipedia.org/assets/js/gt-ie9-507b16b6be.js | 1 KB | — | ✓ | 3rd |
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource Hints2 hints, 0 missing preconnectsPASS
Current Resource Hints
2 resource hints configured
A+Render-Blocking ResourcesNo render-blocking resources detectedPASS
A+Third-Party ResourcesNo third-party resources detectedPASS
Network Waterfall10 requests over 0msINFO
Performance analysis not available for this result.
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
www.wikipedia.org www.wikipedia.org | Other | 1642ms | 28 KB | — | $22/mo | Costly |
Unattributable Unattributable | Other | 169ms | 0 KB | — | $2/mo | Optional |
These scripts may cost more than they're worth
- www.wikipedia.org adds 1642ms and costs ~$22/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.wikipedia.org takes 1642ms 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