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

100

SEO

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

2.25 s

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

3.22 s

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

1.32 s

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.

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

10.29 s

Page Load Progression

948 ms

1.9 s

2.8 s

3.8 s

4.7 s

5.7 s

6.6 s

7.6 s

Checks

6 PASS 3 REVIEW 4 FIX

Page Weight Budget

Action

6.9 MB transferred, 207 requests

FIX

6.9 MB transferred, 207 requests

Page weighs 23.3 MB (6.9 MB transferred)

JavaScript is 5.0 MB — consider code splitting or lazy loading

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

Got: 5.0 MB

Fonts are 284 KB — consider subsetting or using system fonts

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

Got: 284 KB

207 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.9 MB transferred

207 requests

1.4 g CO2 per page load

JavaScript 5.0 MiB 72%

Images 944.6 KiB 13%

Other 293.5 KiB 4%

Fonts 284.2 KiB 4%

HTML 268.7 KiB 4%

Other 98.6 KiB 1%

CSS 63.6 KiB 1%

Other 18.2 KiB 0%

Other 17.5 KiB 0%

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

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.9 MiB of 6.9 MiB)

Third-party blocking time is low (0 ms)

100%

First-party Third-party

JS Bundles

Action

82 scripts, 2.1 MB unused

FIX

82 scripts, 2.1 MB unused

https://d3e54v103j8qbb.cloudfront.net/gen/js/entry...: 1.3 MB unused (47%)