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.11 s

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

2.06 s

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

14 ms

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

0.132

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

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

2.07 s

Page Load Progression

549 ms

1.1 s

1.6 s

2.2 s

2.7 s

3.3 s

3.8 s

4.4 s

Checks

7 PASS 3 REVIEW 3 FIX

Page Weight Budget

Action

3.9 MB transferred, 127 requests

FIX

3.9 MB transferred, 127 requests

Page weighs 9.5 MB (3.9 MB transferred)

JavaScript is 1.7 MB — consider code splitting or lazy loading

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

Got: 1.7 MB

Images are 1.5 MB — compress or use modern formats

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

Got: 1.5 MB

Fonts are 393 KB — consider subsetting or using system fonts

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

Got: 393 KB

CSS is 255 KB — consider purging unused styles

Remove unused CSS rules with tools like PurgeCSS to reduce stylesheet size.

Got: 255 KB

127 HTTP requests — consider bundling or reducing

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

Estimated 0.82 g CO2 per page load

3.9 MB transferred

127 requests

0.82 g CO2 per page load

JavaScript 1.7 MiB 43%

Images 1.5 MiB 39%

Fonts 393.4 KiB 10%

CSS 255.3 KiB 6%

HTML 96.7 KiB 2%

Other 1.6 KiB 0%

Other 1.5 KiB 0%

Other 837 B 0%

Other 0 B 0%

0 2.4 MB 4.9 MB

Over budget

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

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

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

Remove unused CSS rules with tools like PurgeCSS to reduce stylesheet size.

Why this matters

CSS bundle is large — purge unused styles (PurgeCSS, Tailwind JIT) to reduce CSS payload.

Source: web.dev

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

52 scripts, 380 KB unused

FIX

52 scripts, 380 KB unused

https://www.googletagmanager.com/gtag/js?id=AW-108...: 105 KB unused (72%)