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

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

7.11 s

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

80 ms

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

0.163

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

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

7.12 s

Page Load Progression

614 ms

1.2 s

1.8 s

2.5 s

3.1 s

3.7 s

4.3 s

4.9 s

Checks

5 PASS 3 REVIEW 5 FIX

Page Weight Budget

Action

9.9 MB transferred, 168 requests

FIX

9.9 MB transferred, 168 requests

Page weighs 20.7 MB (9.9 MB transferred)

Images are 3.9 MB — compress or use modern formats

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

Got: 3.9 MB

JavaScript is 1.8 MB — consider code splitting or lazy loading

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

Got: 1.8 MB

CSS is 274 KB — consider purging unused styles

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

Got: 274 KB

Fonts are 215 KB — consider subsetting or using system fonts

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

Got: 215 KB

168 HTTP requests — consider bundling or reducing

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

Estimated 2.1 g CO2 per page load

9.9 MB transferred

168 requests

2.1 g CO2 per page load

Images 3.9 MiB 40%

Other 2.7 MiB 27%

JavaScript 1.8 MiB 18%

HTML 951.6 KiB 9%

CSS 273.8 KiB 3%

Fonts 214.7 KiB 2%

Other 123.4 KiB 1%

Other 16.5 KiB 0%

Other 1.3 KiB 0%

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

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

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

Third-party blocking time is low (0 ms)

100%

First-party Third-party

JS Bundles

Action

40 scripts, 486 KB unused

FIX

40 scripts, 486 KB unused

https://securepubads.g.doubleclick.net/pagead/mana...: 109 KB unused (58%)