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

100

SEO

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.07 s

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

2.22 s

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

0 ms

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

0.000

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

1.30 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.22 s

Page Load Progression

375 ms

750 ms

1.1 s

1.5 s

1.9 s

2.2 s

2.6 s

3.0 s

Checks

5 PASS 3 REVIEW 5 FIX

Page Weight Budget

Action

4.2 MB transferred, 136 requests

FIX

4.2 MB transferred, 136 requests

Page weighs 7.6 MB (4.2 MB transferred)

Images are 2.8 MB — compress or use modern formats

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

Got: 2.8 MB

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

136 HTTP requests — consider bundling or reducing

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

Estimated 0.89 g CO2 per page load

4.2 MB transferred

136 requests

0.89 g CO2 per page load

Images 2.8 MiB 66%

JavaScript 1.2 MiB 27%

HTML 120.9 KiB 3%

Fonts 85.2 KiB 2%

Other 40.3 KiB 1%

CSS 20.9 KiB 0%

Other 13.7 KiB 0%

Other 1.9 KiB 0%

Other 514 B 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

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

94% third-party, 0 ms blocking

FIX

94% third-party, 0 ms blocking

Third-party code accounts for 94% of page weight (4.0 MiB of 4.2 MiB)

Third-party blocking time is low (0 ms)

94%

First-party Third-party

JS Bundles

Action

51 scripts, 756 KB unused

FIX

51 scripts, 756 KB unused

https://www.gstatic.com/recaptcha/releases/gTpTIWh...: 242 KB unused (67%)