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.

888 ms

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

1.56 s

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

40 ms

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

0.007

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.

3.69 s

Page Load Progression

580 ms

1.2 s

1.7 s

2.3 s

2.9 s

3.5 s

4.1 s

4.6 s

Checks

7 PASS 1 REVIEW 5 FIX

Page Weight Budget

Action

15.7 MB transferred, 122 requests

FIX

15.7 MB transferred, 122 requests

Page weighs 19.5 MB (15.7 MB transferred)

Images are 3.2 MB — compress or use modern formats

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

Got: 3.2 MB

JavaScript is 1.3 MB — consider code splitting or lazy loading

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

Got: 1.3 MB

122 HTTP requests — consider bundling or reducing

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

Estimated 3.3 g CO2 per page load

15.7 MB transferred

122 requests

3.3 g CO2 per page load

Other 10.9 MiB 69%

Images 3.2 MiB 20%

JavaScript 1.3 MiB 8%

CSS 128.3 KiB 1%

Fonts 119.2 KiB 1%

HTML 54.4 KiB 0%

Other 16.0 KiB 0%

Other 11.0 KiB 0%

Other 3.9 KiB 0%

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

100% third-party, 0 ms blocking

FIX

100% third-party, 0 ms blocking

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

Third-party blocking time is low (0 ms)

100%

First-party Third-party

JS Bundles

Action

34 scripts, 406 KB unused

FIX

34 scripts, 406 KB unused

https://www.googletagmanager.com/gtag/js?id=G-NEFT...: 69 KB unused (41%)