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.

569 ms

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

3.03 s

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

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

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

4.66 s

Page Load Progression

612 ms

1.2 s

1.8 s

2.4 s

3.1 s

3.7 s

4.3 s

4.9 s

Checks

9 PASS 1 REVIEW 3 FIX

Page Weight Budget

Action

8.8 MB transferred, 159 requests

FIX

8.8 MB transferred, 159 requests

Page weighs 12.8 MB (8.8 MB transferred)

Images are 2.9 MB — compress or use modern formats

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

Got: 2.9 MB

JavaScript is 1.4 MB — consider code splitting or lazy loading

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

Got: 1.4 MB

Fonts are 379 KB — consider subsetting or using system fonts

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

Got: 379 KB

159 HTTP requests — consider bundling or reducing

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

Estimated 1.8 g CO2 per page load

8.8 MB transferred

159 requests

1.8 g CO2 per page load

Other 3.9 MiB 45%

Images 2.9 MiB 34%

JavaScript 1.4 MiB 15%

Fonts 378.5 KiB 4%

HTML 109.0 KiB 1%

CSS 63.0 KiB 1%

Other 2.6 KiB 0%

Other 1.3 KiB 0%

Other 1.1 KiB 0%

Other 346 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

JS Bundles

Action

55 scripts, 441 KB unused

FIX

55 scripts, 441 KB unused

https://www.googletagmanager.com/gtag/js?id=AW-333...: 64 KB unused (48%)