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

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

1.58 s

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

56 ms

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

0.384

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

1.98 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.07 s

Page Load Progression

499 ms

999 ms

1.5 s

2.0 s

2.5 s

3.0 s

3.5 s

4.0 s

Checks

6 PASS 2 REVIEW 5 FIX

Page Weight Budget

Action

2.8 MB transferred, 123 requests

FIX

2.8 MB transferred, 123 requests

Page weighs 5.9 MB (2.8 MB transferred)

Images are 1.3 MB — compress or use modern formats

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

Got: 1.3 MB

JavaScript is 1.0 MB — consider code splitting or lazy loading

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

Got: 1.0 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

123 HTTP requests — consider bundling or reducing

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

Estimated 0.59 g CO2 per page load

2.8 MB transferred

123 requests

0.59 g CO2 per page load

Images 1.3 MiB 44%

JavaScript 1.0 MiB 37%

Fonts 392.8 KiB 14%

CSS 99.6 KiB 3%

HTML 33.1 KiB 1%

Other 5.3 KiB 0%

Other 2.4 KiB 0%

Other 2.2 KiB 0%

Other 959 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 (2.8 MiB of 2.8 MiB)

Third-party blocking time is low (0 ms)

100%

First-party Third-party

JS Bundles

Action

32 scripts, 344 KB unused

FIX

32 scripts, 344 KB unused

https://www.googletagmanager.com/gtm.js?id=GTM-KGW...: 64 KB unused (37%)