Performance

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

3.47 s

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

5.32 s

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

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

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

5.32 s

Page Load Progression

520 ms

1.0 s

1.6 s

2.1 s

2.6 s

3.1 s

3.6 s

4.2 s

Checks

6 PASS 2 REVIEW 5 FIX

Page Weight Budget

Action

8.1 MB transferred, 162 requests

FIX

8.1 MB transferred, 162 requests

Page weighs 11.2 MB (8.1 MB transferred)

Images are 6.2 MB — compress or use modern formats

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

Got: 6.2 MB

JavaScript is 773 KB — consider code splitting or lazy loading

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

Got: 773 KB

Fonts are 404 KB — consider subsetting or using system fonts

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

Got: 404 KB

CSS is 239 KB — consider purging unused styles

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

Got: 239 KB

162 HTTP requests — consider bundling or reducing

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

Estimated 1.7 g CO2 per page load

8.1 MB transferred

162 requests

1.7 g CO2 per page load

Images 6.2 MiB 76%

JavaScript 773.3 KiB 9%

Other 571.5 KiB 7%

Fonts 404.4 KiB 5%

CSS 238.9 KiB 3%

HTML 19.3 KiB 0%

Other 13.7 KiB 0%

Other 4.2 KiB 0%

Other 553 B 0%

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

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

100% third-party, 0 ms blocking

FIX

100% third-party, 0 ms blocking

Third-party code accounts for 100% of page weight (8.1 MiB of 8.1 MiB)

Third-party blocking time is low (0 ms)

100%

First-party Third-party

JS Bundles

Action

19 scripts, 310 KB unused

FIX

19 scripts, 310 KB unused

https://www.googletagmanager.com/gtag/js?id=G-KQJB...: 66 KB unused (37%)