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

SEO

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

2.47 s

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

7.13 s

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

340 ms

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

0.001

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

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

7.17 s

Page Load Progression

649 ms

1.3 s

1.9 s

2.6 s

3.2 s

3.9 s

4.5 s

5.2 s

Checks

6 PASS 2 REVIEW 5 FIX

Page Weight Budget

Action

4.9 MB transferred, 200 requests

FIX

4.9 MB transferred, 200 requests

Page weighs 15.5 MB (4.9 MB transferred)

JavaScript is 2.6 MB — consider code splitting or lazy loading

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

Got: 2.6 MB

Images are 1.5 MB — compress or use modern formats

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

Got: 1.5 MB

200 HTTP requests — consider bundling or reducing

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

Estimated 1.0 g CO2 per page load

4.9 MB transferred

200 requests

1.0 g CO2 per page load

JavaScript 2.6 MiB 53%

Images 1.5 MiB 31%

HTML 453.7 KiB 9%

Other 106.8 KiB 2%

CSS 84.2 KiB 2%

Fonts 63.2 KiB 1%

Other 41.6 KiB 1%

Other 27.3 KiB 1%

Other 8.1 KiB 0%

Other 745 B 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

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

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

93% third-party, 0 ms blocking

FIX

93% third-party, 0 ms blocking

Third-party code accounts for 93% of page weight (4.5 MiB of 4.9 MiB)

Third-party blocking time is low (0 ms)

93%

First-party Third-party

JS Bundles

Action

30 scripts, 936 KB unused

FIX

30 scripts, 936 KB unused

https://static.dzeninfra.ru/s3/zen-apps/dzen-deskt...: 230 KB unused (38%)