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

100

SEO

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

625 ms

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

1.05 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.099

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

1.03 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.05 s

Page Load Progression

598 ms

1.2 s

1.8 s

2.4 s

3.0 s

3.6 s

4.2 s

4.8 s

Checks

8 PASS 3 REVIEW 2 FIX

Page Weight Inventory

Action

55 resources · 1.5 MB · 178 KB savings available

FIX

55 resources · 1.5 MB · 178 KB savings available

Page weight 479 KB over 1MB target

Got: 1.5 MB Expected: ≤ 1 MB

~178 KB of savings available

24 third-party resources (46% of weight)

55 resources · 1.5 MiB · 24 third-party 478.6 KiB over 1MB target

JavaScript 61% · 912.3 KiB

Image 35% · 530.8 KiB

Font 2% · 28.1 KiB

CSS 1% · 20.7 KiB

Document 0% · 7.4 KiB

Other 0% · 3.2 KiB

~178.3 KiB of savings available

Remove unused JavaScript: 178.3 KiB

#	Resource	Type	Size	Cache	Unused	3rd party	Issues

55 resources			1.5 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.

Last-Modified header present

No Cache-Control header

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

Page Weight Budget

1.5 MB transferred, 55 requests

REVIEW

1.5 MB transferred, 55 requests

Page weighs 3.6 MB (1.5 MB transferred)

JavaScript is 912 KB — consider code splitting or lazy loading

Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.

Got: 912 KB

55 HTTP requests

Estimated 0.31 g CO2 per page load

1.5 MB transferred

55 requests

0.31 g CO2 per page load

JavaScript 912.3 KiB 61%

Images 525.7 KiB 35%

Fonts 28.1 KiB 2%

CSS 20.7 KiB 1%

HTML 7.4 KiB 0%

Other 6.4 KiB 0%

Other 1.4 KiB 0%

Other 554 B 0%

0 2.4 MB 4.9 MB

Approaching limit

Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.

Why this matters

JavaScript bundle is large — code-split routes and lazy-load off-screen components to defer.

Source: web.dev

Third-Party Impact

46% third-party, 0 ms blocking

REVIEW

46% third-party, 0 ms blocking

Third-party code accounts for 46% of page weight (685.3 KiB of 1.5 MiB)

Third-party blocking time is low (0 ms)

54%

46%

First-party Third-party

JS Bundles

Action

30 scripts, 178 KB unused

REVIEW

30 scripts, 178 KB unused

https://www.googletagmanager.com/gtag/js?id=G-73MS...: 67 KB unused (43%)