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

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

5.18 s

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

41 ms

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

0.002

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

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

6.60 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

6.8 MB transferred, 115 requests

FIX

6.8 MB transferred, 115 requests

Page weighs 12.0 MB (6.8 MB transferred)

Images are 4.6 MB — compress or use modern formats

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

Got: 4.6 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

115 HTTP requests — consider bundling or reducing

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

Estimated 1.4 g CO2 per page load

6.8 MB transferred

115 requests

1.4 g CO2 per page load

Images 4.6 MiB 68%

JavaScript 1.8 MiB 27%

HTML 127.0 KiB 2%

CSS 116.3 KiB 2%

Fonts 112.7 KiB 2%

Other 7.6 KiB 0%

Other 1.9 KiB 0%

Other 1.8 KiB 0%

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

100% third-party, 0 ms blocking

FIX

100% third-party, 0 ms blocking

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

Third-party blocking time is low (0 ms)

100%

First-party Third-party

JS Bundles

Action

35 scripts, 517 KB unused

FIX

35 scripts, 517 KB unused

https://t.contentsquare.net/uxa/9f13e54095441.js: 100 KB unused (78%)