Performance

· 16 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.

5.04 s

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

12.86 s

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

991 ms

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

0.003

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

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

12.88 s

Page Load Progression

519 ms

1.0 s

1.6 s

2.1 s

2.6 s

3.1 s

3.6 s

4.2 s

Checks

8 PASS 3 REVIEW 4 FIX

Page Weight Budget

Action

7.9 MB transferred, 160 requests

FIX

7.9 MB transferred, 160 requests

Page weighs 11.2 MB (7.9 MB transferred)

Images are 6.1 MB — compress or use modern formats

Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.

Got: 6.1 MB

JavaScript is 569 KB — consider code splitting or lazy loading

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

Got: 569 KB

Fonts are 404 KB — consider subsetting or using system fonts

Subset fonts to include only used characters, or switch to system font stacks.

Got: 404 KB

160 HTTP requests — consider bundling or reducing

Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.

Estimated 1.7 g CO2 per page load

7.9 MB transferred

160 requests

1.7 g CO2 per page load

Images 6.1 MiB 78%

Other 720.7 KiB 9%

JavaScript 569.4 KiB 7%

Fonts 404.4 KiB 5%

CSS 49.4 KiB 1%

HTML 19.3 KiB 0%

Other 13.7 KiB 0%

Other 4.2 KiB 0%

Other 553 B 0%

Other 216 B 0%

0 2.4 MB 4.9 MB

Over budget

Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.

Why this matters

Image bandwidth is high — modern formats (WebP/AVIF) and resizing typically cut it 50%+.

Source: web.dev

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

Subset fonts to include only used characters, or switch to system font stacks.

Why this matters

Font payload is large — subset to used glyphs only, or fall back to system fonts (zero load time).

Source: web.dev font loading

Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.

Why this matters

High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.

Source: web.dev

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 (7.9 MiB of 7.9 MiB)

Third-party blocking time is low (0 ms)

100%

First-party Third-party

Page Weight Inventory

Action

160 resources · 7.9 MB · 184 KB savings available

FIX

160 resources · 7.9 MB · 184 KB savings available

Page weight 6.9 MB over 1MB target

Got: 7.9 MB Expected: ≤ 1 MB

~184 KB of savings available

158 third-party resources (100% of weight)

2 resources over 200KB

160 resources · 7.9 MiB · 158 third-party 6.9 MiB over 1MB target

Image 78% · 6.2 MiB

Media 9% · 720.7 KiB

JavaScript 7% · 569.4 KiB

Font 5% · 404.4 KiB

CSS 1% · 49.4 KiB

Document 0% · 19.3 KiB

Other 0% · 4.9 KiB

~183.6 KiB of savings available

Remove unused JavaScript: 183.6 KiB

#	Resource	Type	Size	Cache	Unused	3rd party	Issues

160 resources			7.9 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

90 images, 0 KB saveable

REVIEW

90 images, 0 KB saveable

All images are well-optimized

90 images 6.1 MB

0 oversized -0 KB

90 legacy format

0 missing dimensions CLS risk

JS Bundles

Action

19 scripts, 184 KB unused

REVIEW

19 scripts, 184 KB unused

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