Performance

· 22 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

100

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.

908 ms

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

1.15 s

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

0 ms

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

0.040

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

971 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.15 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

10 PASS 5 REVIEW 4 FIX

Page Weight Budget

Action

2.9 MB transferred, 105 requests

FIX

2.9 MB transferred, 105 requests

Page weighs 3.0 MB (2.9 MB transferred)

Images are 2.7 MB — compress or use modern formats

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

Got: 2.7 MB

105 HTTP requests — consider bundling or reducing

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

Estimated 0.60 g CO2 per page load

2.9 MB transferred

105 requests

0.60 g CO2 per page load

Images 2.7 MiB 93%

Fonts 141.3 KiB 5%

JavaScript 45.2 KiB 2%

HTML 12.1 KiB 0%

CSS 11.7 KiB 0%

Other 5.7 KiB 0%

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

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

Third-party blocking time is low (0 ms)

100%

First-party Third-party

Page Weight Inventory

Action

105 resources · 2.9 MB · 23 KB savings available

FIX

105 resources · 2.9 MB · 23 KB savings available

Page weight 2.9 MB exceeds 1 MB target by 1.9 MB

Got: 2.9 MB Expected: ≤ 1 MB

104 third-party resources (100% of weight)

3 resources over 200KB

105 resources · 2.9 MiB · 104 third-party 1.9 MiB over 1MB target

Image 93% · 2.7 MiB

Font 5% · 141.3 KiB

JavaScript 2% · 45.2 KiB

Document 0% · 12.6 KiB

CSS 0% · 11.7 KiB

Other 0% · 930 B

~23.0 KiB of savings available

Remove unused JavaScript: 23.0 KiB

#	Resource	Type	Size	Cache	Unused	3rd party	Issues

105 resources			2.9 MiB

HTTP Caching

Action

No cache headers

FIX

No cache headers

No Cache-Control header found

Browsers will use heuristic caching, which can be unpredictable. Set explicit cache headers.

No Cache-Control header

Adding a Cache-Control header can significantly improve repeat-visit performance.

Image Optimization

Action

89 images, 0 KB saveable

REVIEW

89 images, 0 KB saveable

https://techex.com.ua/wp-content/uploads/2026/05/7... is missing width/height — may cause layout shift