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

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

1.09 s

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

47 ms

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

0.054

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

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

4.25 s

Page Load Progression

557 ms

1.1 s

1.7 s

2.2 s

2.8 s

3.3 s

3.9 s

4.5 s

Checks

7 PASS 2 REVIEW 4 FIX

Page Weight Budget

Action

2.8 MB transferred, 178 requests

FIX

2.8 MB transferred, 178 requests

Page weighs 8.0 MB (2.8 MB transferred)

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

Fonts are 1.1 MB — consider subsetting or using system fonts

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

Got: 1.1 MB

178 HTTP requests — consider bundling or reducing

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

Estimated 0.59 g CO2 per page load

2.8 MB transferred

178 requests

0.59 g CO2 per page load

JavaScript 1.3 MiB 48%

Fonts 1.1 MiB 39%

Images 156.9 KiB 5%

HTML 127.5 KiB 4%

CSS 50.8 KiB 2%

Other 31.2 KiB 1%

Other 11.2 KiB 0%

Other 5.7 KiB 0%

Other 4.5 KiB 0%

Other 3.5 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 (2.8 MiB of 2.8 MiB)

Third-party blocking time is low (0 ms)

100%

First-party Third-party

JS Bundles

Action

52 scripts, 332 KB unused

FIX

52 scripts, 332 KB unused

https://static.hsappstatic.net/conversations-visit...: 149 KB unused (44%)