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.
4.37 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
5.51 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
625 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.
7.00 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.
5.87 s
Page Load Progression
FPage Weight BudgetAction9.4 MB transferred, 42 requestsFIX
DThird-Party ImpactAction100% third-party, 0 ms blockingFIX
FJS Execution CostAction4925ms total JS executionFIX
Main Thread Breakdown
| Script | Total | Scripting | Parse/Compile | Party |
|---|---|---|---|---|
| https://www.grammy.com/ | 1769ms | 56ms | 12ms | 3rd |
| https://cmp.osano.com/6obDHT6lDyvrg2r/48d13449-731c-4859-93e5-726ae3442fe1/osano.js | 1354ms | 929ms | 42ms | 3rd |
| Unattributable | 967ms | 18ms | 0ms | 3rd |
| https://www.grammy.com/wp-content/themes/grammy/assets/dist/js/app.js?ver=0.1.40 | 835ms | 271ms | 66ms | 3rd |
DPage Weight InventoryAction42 resources · 9.4 MB · 60 KB savings availableFIX
~60.0 KiB of savings available
| # | Resource | Type | Size | Cache | Unused | 3rd party | Issues |
|---|---|---|---|---|---|---|---|
| — | — | ||||||
| 42 resources | 9.4 MiB | ||||||
FHTTP CachingActionNo cache headersFIX
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
CImage OptimizationAction26 images, 0 KB saveableREVIEW
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
BJS Bundles3 scripts, 60 KB unusedREVIEW
Downloaded but never executed on this page.
| Script | Size | Unused | Minified | Party |
|---|---|---|---|---|
| https://www.grammy.com/wp-content/themes/grammy/assets/dist/js/app.js?ver=0.1.40 | 120 KB | 34 KB (28%) | ✓ | 3rd |
| https://cmp.osano.com/6obDHT6lDyvrg2r/48d13449-731c-4859-93e5-726ae3442fe1/osano.js | 102 KB | 26 KB (26%) | ✓ | 3rd |
| blob:https://www.grammy.com/0c1ce74c-bc2b-4376-a11b-ad9a37aee0bf | -0 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
CGreen HostingActionWhether the site is served from green-energy infrastructureREVIEW
Green Hosting
No green hosting detected
A+Text CompressionAll text resources are compressedPASS
A+Font Loading3 fonts (65 KB)PASS
Web fonts
3
65 KB total
Render-blocking
0
of 3
Dominant font-display
swap
Most common across fonts
Font loading timeline
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)
A+Resource CachingAll resources properly cachedPASS
A+Critical Rendering PathNo render-blocking resourcesPASS
A+Resource Hints3 hints, 0 missing preconnectsPASS
Current Resource Hints
3 resource hints configured
A+Render-Blocking ResourcesNo render-blocking resources detectedPASS
A+Third-Party ResourcesNo third-party resources detectedPASS
Network Waterfall42 requests over 1673msINFO
Third-Party Script CostPer-script blocking time, transfer cost, and cache headersINFO
| Script | Category | Execution | Transfer | Unused | Monthly Cost | Verdict |
|---|---|---|---|---|---|---|
www.grammy.com www.grammy.com | Other | 1769ms | 75 KB | — | €9/mo | Costly |
cmp.osano.com cmp.osano.com | Other | 1354ms | 102 KB | 26% | €7/mo | Costly |
Unattributable Unattributable | Other | 967ms | 0 KB | — | €5/mo | Costly |
www.grammy.com www.grammy.com | Other | 835ms | 120 KB | 28% | €4/mo | Costly |
These scripts may cost more than they're worth
- www.grammy.com adds 1769ms and costs ~€9/month
- cmp.osano.com adds 1354ms and costs ~€7/month
- Unattributable adds 967ms and costs ~€5/month
- www.grammy.com adds 835ms and costs ~€4/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.grammy.com takes 1769ms 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
cmp.osano.com takes 1354ms 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
Unattributable takes 967ms 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.grammy.com takes 835ms 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