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.

2.17 s

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

2.87 s

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

232 ms

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

0.003

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.

5.25 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

6 PASS 2 REVIEW 5 FIX

Page Weight Budget

Action

3.9 MB transferred, 115 requests

FIX

3.9 MB transferred, 115 requests

Page weighs 13.4 MB (3.9 MB transferred)

JavaScript is 2.5 MB — consider code splitting or lazy loading

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

Got: 2.5 MB

Fonts are 434 KB — consider subsetting or using system fonts

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

Got: 434 KB

CSS is 237 KB — consider purging unused styles

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

Got: 237 KB

115 HTTP requests — consider bundling or reducing

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

Estimated 0.82 g CO2 per page load

3.9 MB transferred

115 requests

0.82 g CO2 per page load

JavaScript 2.5 MiB 63%

Fonts 434.4 KiB 11%

Images 424.4 KiB 11%

CSS 237.0 KiB 6%

HTML 235.2 KiB 6%

Other 112.3 KiB 3%

Other 29.1 KiB 1%

Other 18.1 KiB 0%

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

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 (3.9 MiB of 3.9 MiB)

Third-party blocking time is low (0 ms)

100%

First-party Third-party

JS Bundles

Action

51 scripts, 916 KB unused

FIX

51 scripts, 916 KB unused

https://cdns.gigya.com/js/gigya.js?apiKey=4_CO8231...: 137 KB unused (58%)