Performance

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

586 ms

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

1.72 s

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

25 ms

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

0.004

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

1.14 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.84 s

Page Load Progression

646 ms

1.3 s

1.9 s

2.6 s

3.2 s

3.9 s

4.5 s

5.2 s

Checks

8 PASS 7 REVIEW 4 FIX

Page Weight Budget

Action

4.2 MB transferred, 113 requests

FIX

4.2 MB transferred, 113 requests

Page weighs 9.5 MB (4.2 MB transferred)

JavaScript is 1.2 MB — consider code splitting or lazy loading

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

Got: 1.2 MB

Fonts are 673 KB — consider subsetting or using system fonts

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

Got: 673 KB

CSS is 334 KB — consider purging unused styles

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

Got: 334 KB

113 HTTP requests — consider bundling or reducing

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

Estimated 0.88 g CO2 per page load

4.2 MB transferred

113 requests

0.88 g CO2 per page load

Other 1.8 MiB 44%

JavaScript 1.2 MiB 28%

Fonts 672.9 KiB 16%

CSS 333.7 KiB 8%

Images 115.7 KiB 3%

HTML 60.1 KiB 1%

Other 28.6 KiB 1%

Other 14.5 KiB 0%

Other 3.3 KiB 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

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

Third-Party Impact

Action

99% third-party, 0 ms blocking

FIX

99% third-party, 0 ms blocking

Third-party code accounts for 99% of page weight (4.1 MiB of 4.2 MiB)

Third-party blocking time is low (0 ms)

99%

First-party Third-party

JS Bundles

Action

48 scripts, 445 KB unused

FIX

48 scripts, 445 KB unused

https://www.googletagmanager.com/gtag/js?id=G-23LN...: 119 KB unused (65%)