Performance

· 15 checks — Lighthouse + waterfall + sustainability rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

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

Mobile Desktop

Performance

Accessibility

Best Practices

SEO

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

1.20 s

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

1.42 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

35 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.333

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.72 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.

1.52 s

Page Load Progression

445 ms

889 ms

1.3 s

1.8 s

2.2 s

2.7 s

3.1 s

3.6 s

Checks

5 PASS 4 REVIEW 4 FIX

Page Weight Budget

Action

8.4 MB transferred, 40 requests

FIX

8.4 MB transferred, 40 requests

Page weighs 10.5 MB (8.4 MB transferred)

40 HTTP requests

Estimated 1.8 g CO2 per page load

8.4 MB transferred

40 requests

1.8 g CO2 per page load

Other 7.7 MiB 92%

Images 246.1 KiB 3%

JavaScript 222.1 KiB 3%

HTML 76.4 KiB 1%

Fonts 65.2 KiB 1%

CSS 34.8 KiB 0%

Other 16.4 KiB 0%

0 2.4 MB 4.9 MB

Over budget

Third-Party Impact

Action

100% third-party, 0 ms blocking

FIX

100% third-party, 0 ms blocking

Third-party code accounts for 100% of page weight (8.4 MiB of 8.4 MiB)

Third-party blocking time is low (0 ms)

100%

First-party Third-party

Page Weight Inventory

Action

40 resources · 8.4 MB · 60 KB savings available

FIX

40 resources · 8.4 MB · 60 KB savings available

Page weight 7.4 MB over 1MB target

Got: 8.4 MB Expected: ≤ 1 MB

~60 KB of savings available

39 third-party resources (100% of weight)

1 resources over 200KB

40 resources · 8.4 MiB · 39 third-party 7.4 MiB over 1MB target

Media 92% · 7.7 MiB

Image 3% · 261.3 KiB

JavaScript 3% · 222.1 KiB

Document 1% · 76.4 KiB

Font 1% · 65.2 KiB

CSS 0% · 34.8 KiB

Other 0% · 1.2 KiB

~60.1 KiB of savings available

Remove unused JavaScript: 60.1 KiB

#	Resource	Type	Size	Cache	Unused	3rd party	Issues

40 resources			8.4 MiB

HTTP Caching

Action

No cache headers

FIX

No cache headers

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.

Image Optimization

24 images, 0 KB saveable

REVIEW

24 images, 0 KB saveable

All images are well-optimized

24 images 246 KB

0 oversized -0 KB

10 legacy format

0 missing dimensions CLS risk

JS Execution Cost

Action

1316ms total JS execution

REVIEW

1316ms total JS execution

https://www.grammy.com/: 635ms CPU time

https://cmp.osano.com/6obDHT6lDyvrg2r/48d13449-731...: 276ms CPU time

https://www.grammy.com/wp-content/themes/grammy/as...: 218ms CPU time

Unattributable: 187ms CPU time

Third-party scripts: 1316ms (100% of total)

Main Thread Breakdown

Other 41% Script Evaluation 25% Style & Layout 17% Parse HTML & CSS 9% Rendering 4%

Script	Total	Scripting	Parse/Compile	Party
https://www.grammy.com/	635ms	18ms	3ms	3rd
https://cmp.osano.com/6obDHT6lDyvrg2r/48d13449-731c-4859-93e5-726ae3442fe1/osano.js	276ms	230ms	11ms	3rd
https://www.grammy.com/wp-content/themes/grammy/assets/dist/js/app.js?ver=0.1.40	218ms	76ms	22ms	3rd
Unattributable	187ms	6ms	0ms	3rd

JS Bundles

3 scripts, 60 KB unused

REVIEW

3 scripts, 60 KB unused

https://www.grammy.com/wp-content/themes/grammy/as...: 34 KB unused (28%)

Consider code splitting or tree shaking to reduce unused code.

https://cmp.osano.com/6obDHT6lDyvrg2r/48d13449-731...: 26 KB unused (26%)

Consider code splitting or tree shaking to reduce unused code.

Total unused JavaScript: 60 KB

60 KB unused JavaScript

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/1652d4f2-3151-4e04-870f-f9da976f7999	-0 KB	—	✓	3rd

Consider code splitting or tree shaking to reduce unused code.

Why this matters

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.

Why this matters

This bundle has high unused code — code-split or tree-shake to ship only what executes.

Source: web.dev / Lighthouse coverage

Green Hosting

Action

Whether the site is served from green-energy infrastructure

REVIEW

Green Hosting

No green hosting detected

A+

Text Compression

All text resources are compressed

PASS

All text resources are compressed

All text resources are properly compressed.

A+

Font Loading

3 fonts (65 KB)

PASS

3 fonts (65 KB)

3 font(s) use font-display: swap (FOUT risk but functional)

Web fonts

65 KB total

Render-blocking

of 3

Dominant font-display

swap

Most common across fonts

Font loading timeline

Transfer FOIT (block) FOUT (swap)

galaxie_polaris_book-we... woff2 swap

Size 21 KB

Load time 64 ms

Start 312 ms

Risk FOUT — text flashes from fallback to web font

galaxie_polaris_bold-we... woff2 swap

Size 21 KB

Load time 77 ms

Start 312 ms

Risk FOUT — text flashes from fallback to web font

galaxie_polaris_book_it... woff2 swap

Size 23 KB

Load time 64 ms

Start 585 ms

Risk FOUT — text flashes from fallback to web font

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 Caching

All resources properly cached

PASS

All resources properly cached

No caching issues found

All static resources have appropriate caching headers.

A+

Critical Rendering Path

No render-blocking resources

PASS

No render-blocking resources

No render-blocking resources detected

A+

Resource Hints

No optimization needed

PASS

No optimization needed

No resource hint issues

Network Waterfall

40 requests over 1468ms

INFO

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 1316ms · 297KB · €7/mo

Script	Category	Execution	Transfer	Unused	Monthly Cost	Verdict
www.grammy.com www.grammy.com	Other	635ms	75 KB	—	€3/mo	Costly
cmp.osano.com cmp.osano.com	Other	276ms	102 KB	26%	€1/mo	Costly
www.grammy.com www.grammy.com	Other	218ms	120 KB	28%	€1/mo	Costly
Unattributable Unattributable	Other	187ms	0 KB	—	€1/mo	Optional

www.grammy.com

Other

Costly

Execution 635ms

Transfer 75 KB

Monthly Cost €3/mo

cmp.osano.com

Other

Costly

Execution 276ms

Transfer 102 KB

Unused 26%

Monthly Cost €1/mo

www.grammy.com

Other

Costly

Execution 218ms

Transfer 120 KB

Unused 28%

Monthly Cost €1/mo

Unattributable

Other

Optional

Execution 187ms

Transfer 0 KB

Monthly Cost €1/mo

These scripts may cost more than they're worth

www.grammy.com adds 635ms and costs ~€3/month
cmp.osano.com adds 276ms and costs ~€1/month
www.grammy.com adds 218ms and costs ~€1/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.grammy.com takes 635ms 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

cmp.osano.com takes 276ms 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

www.grammy.com takes 218ms 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.