Skip to content
https://wikipedia.com

Performance

· 17 checks — Lighthouse + waterfall + sustainability rolled into one auditable list.
SCORE
90
GRADE
A
FIX
2
REVIEW
2
PASS
11
INFO
2

Performance-focused optimization plan with CWV assessment, top offenders, and time estimates

Mobile Desktop
94
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
95
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

2.39 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.47 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.88 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.47 s

Page Load Progression

424 ms
848 ms
1.3 s
1.7 s
2.1 s
2.5 s
3.0 s
3.4 s
Checks
17
11 PASS 2 REVIEW 2 FIX
D
Third-Party Impact
Action
100% third-party, 0 ms blocking
FIX
100% third-party, 0 ms blocking
Warning::
Third-party code accounts for 100% of page weight (95.3 KiB of 95.4 KiB)
Info::
Third-party blocking time is low (0 ms)
100%
First-party Third-party
F
HTTP Caching
Action
No cache headers
FIX
No cache headers
Warning::
No Cache-Control header found
Browsers will use heuristic caching, which can be unpredictable. Set explicit cache headers.

No Cache-Control header

Adding a Cache-Control header can significantly improve repeat-visit performance.

C
JS Execution Cost
Action
1645ms total JS execution
REVIEW
1645ms total JS execution
Warning::
https://www.wikipedia.org/: 1524ms CPU time
Info::
Unattributable: 121ms CPU time
Warning::
Third-party scripts: 1645ms (100% of total)

Main Thread Breakdown

Style & Layout 81% Other 11% Script Evaluation 3%
ScriptTotalScriptingParse/CompileParty
https://www.wikipedia.org/1524ms16ms2ms3rd
Unattributable121ms6ms0ms3rd
C
Green Hosting
Action
Whether the site is served from green-energy infrastructure
REVIEW

Green Hosting

No green hosting detected

A+
Page Weight Budget
95 KB transferred, 8 requests
PASS
95 KB transferred, 8 requests
Info::
Page weighs 205 KB (95 KB transferred)
Info::
8 HTTP requests
Info::
Estimated 0.02 g CO2 per page load
95 KB / 2.4 MB budget
95 KB transferred
8 requests
0.02 g CO2 per page load
Images 60.3 KiB 63%
HTML 23.1 KiB 24%
JavaScript 10.1 KiB 11%
Other 1.9 KiB 2%
0 2.4 MB 4.9 MB
Under budget
A+
Text Compression
All text resources are compressed
PASS
All text resources are compressed
Info::
All text resources are compressed
All text resources are properly compressed.
A
Image Optimization
3 images, 0 KB saveable
PASS
3 images, 0 KB saveable
Info::
All images are well-optimized
3 images 60 KB
0 oversized -0 KB
3 legacy format
0 missing dimensions CLS risk
A+
Font Loading
No web fonts (system fonts)
PASS
No web fonts (system fonts)
Info::
No web fonts loaded — system fonts are fastest
No web fonts loaded — system fonts are optimal.
A+
JS Bundles
2 scripts, 0 KB unused
PASS
2 scripts, 0 KB unused
0 KB unused JavaScript

Downloaded but never executed on this page.

ScriptSizeUnusedMinifiedParty
https://www.wikipedia.org/portal/wikipedia.org/assets/js/index-a9b103e1fc.js9 KB—✓3rd
https://www.wikipedia.org/portal/wikipedia.org/assets/js/gt-ie9-507b16b6be.js1 KB—✓3rd
A+
Resource Caching
All resources properly cached
PASS
All resources properly cached
Info::
No caching issues found
All static resources have appropriate caching headers.
A+
Critical Rendering Path
No render-blocking resources
PASS
No render-blocking resources
Info::
No render-blocking resources detected
A+
Resource Hints
2 hints, 0 missing preconnects
PASS
2 hints, 0 missing preconnects
Info::
Page uses 2 resource hint(s)

Current Resource Hints

preconnect
2
preload
—
dns-prefetch
—
prefetch
—

2 resource hints configured

A
Page Weight Inventory
8 resources · 95 KB · 0 KB savings available
PASS
8 resources · 95 KB · 0 KB savings available
Info::
Within 1MB page-weight target
Got: 95 KB
Warning::
7 third-party resources (100% of weight)
8 resources · 95.4 KiB · 7 third-party Within 1MB page-weight target
Image 65% · 62.1 KiB
Document 24% · 23.2 KiB
JavaScript 11% · 10.1 KiB
A+
Render-Blocking Resources
No render-blocking resources detected
PASS
No render-blocking resources detected
Info::
No render-blocking resources detected in <head>
A+
Third-Party Resources
No third-party resources detected
PASS
No third-party resources detected
Network Waterfall
8 requests over 432ms
INFO
0 ms 500 ms 1.0 s 1.5 s 2.0 s 2.5 s FCP 2.4 s LCP 2.5 shttps://wikipedia.com// https://wikipedia.com/ — 301 — 139 B — 12 ms — h2https://www.wikipedia.org/www.wikipedia.org/ https://www.wikipedia.org/ — 200 — 23.1 KiB — 12 ms — h2https://www.wikipedia.org/portal/wikipedia.org/assets/img/Wikipedia-logo-v2@2x.pngwww.wikipedia.org/portal/wikipedia.... https://www.wikipedia.org/portal/wikipedia.org/assets/img/Wikipedia-logo-v2@2x.png — 200 — 37.6 KiB — 6 ms — h2https://www.wikipedia.org/portal/wikipedia.org/assets/js/index-a9b103e1fc.jswww.wikipedia.org/portal/wikipedia.... https://www.wikipedia.org/portal/wikipedia.org/assets/js/index-a9b103e1fc.js — 200 — 8.7 KiB — 8 ms — h2https://www.wikipedia.org/portal/wikipedia.org/assets/js/gt-ie9-507b16b6be.jswww.wikipedia.org/portal/wikipedia.... https://www.wikipedia.org/portal/wikipedia.org/assets/js/gt-ie9-507b16b6be.js — 200 — 1.3 KiB — 5 ms — h2https://www.wikipedia.org/portal/wikipedia.org/assets/img/sprite-e49fbf32.svgwww.wikipedia.org/portal/wikipedia.... https://www.wikipedia.org/portal/wikipedia.org/assets/img/sprite-e49fbf32.svg — 200 — 18.6 KiB — 5 ms — h2https://www.wikipedia.org/portal/wikipedia.org/assets/img/Wikinews-logo_sister@2x.pngwww.wikipedia.org/portal/wikipedia.... https://www.wikipedia.org/portal/wikipedia.org/assets/img/Wikinews-logo_sister@2x.png — 200 — 4.1 KiB — 3 ms — h2https://www.wikipedia.org/static/favicon/wikipedia.icowww.wikipedia.org/static/favicon/wi... https://www.wikipedia.org/static/favicon/wikipedia.ico — 200 — 1.8 KiB — 4 ms — h2
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
100% of JavaScript execution is third-party
First-party Third-party 1645ms · 23KB · $22/mo
www.wikipedia.org
Other
Costly
Execution 1524ms
Transfer 23 KB
Monthly Cost $20/mo
Unattributable
Other
Optional
Execution 121ms
Transfer 0 KB
Monthly Cost $2/mo

These scripts may cost more than they're worth

  • www.wikipedia.org adds 1524ms and costs ~$20/month

100% of JavaScript execution time is spent on third-party scripts. Consider auditing which scripts are essential.

Why this matters

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 1524ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.

Why this matters

This script has high main-thread execution time — optimize hot paths or defer.

Source: web.dev

How third-party costs are calculated

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback