Performance

· 26 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.

2.45 s

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

2.47 s

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

670 ms

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

0.039

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

3.96 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.71 s

Page Load Progression

706 ms

1.4 s

2.1 s

2.8 s

3.5 s

4.2 s

4.9 s

5.7 s

Checks

15 PASS 6 REVIEW 2 FIX

JS Execution Cost

Action

8392ms total JS execution

FIX

8392ms total JS execution

https://apprestore.ru/assets/app.js: 5455ms CPU time

https://apprestore.ru/: 1343ms CPU time

https://mc.yandex.ru/metrika/tag.js?id=112174020: 895ms CPU time

Unattributable: 699ms CPU time

Third-party scripts: 895ms (11% of total)

Main Thread Breakdown

Other 48% Style & Layout 21% Script Evaluation 17% Rendering 14%

Script	Total	Scripting	Parse/Compile	Party
https://apprestore.ru/assets/app.js	5455ms	529ms	0ms	1st
https://apprestore.ru/	1343ms	16ms	3ms	1st
https://mc.yandex.ru/metrika/tag.js?id=112174020	895ms	812ms	44ms	3rd
Unattributable	699ms	41ms	0ms	1st

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

35 images, 0 KB saveable

REVIEW

35 images, 0 KB saveable

All images are well-optimized

35 images 287 KB

0 oversized -0 KB

35 legacy format

0 missing dimensions CLS risk

HTTP/3 (QUIC)

HTTP/3 not advertised

REVIEW

HTTP/3 not advertised

HTTP/3 (QUIC) is not advertised

HTTP/3 isn't advertised via Alt-Svc and the worker didn't negotiate h3. HTTP/3 reduces handshake latency (1-RTT instead of 2-3 RTTs) and is more resilient on lossy connections. Most modern CDNs (Cloudflare, Fastly, AWS CloudFront, Google Cloud CDN) support HTTP/3 with a single config switch -- consider enabling for mobile-heavy workloads.

Compression Algorithm

Main response uses gzip; brotli would be ~20% smaller

REVIEW

Main response uses gzip; brotli would be ~20% smaller

Main HTML response uses gzip (brotli would be ~20% smaller)

All current browsers support brotli. Most CDNs (Cloudflare, Fastly, AWS CloudFront, Vercel, Netlify) can switch from gzip to brotli with a single config flag. Origin servers (nginx, Apache) need a brotli module compiled in -- nginx-brotli or Apache mod_brotli.

Main HTML Cache-Control

No Cache-Control header on main HTML response

REVIEW

No Cache-Control header on main HTML response

Main HTML response has no Cache-Control header

Without an explicit Cache-Control, browsers fall back to heuristic caching (~10% of Last-Modified age). Set `Cache-Control: no-cache` or `max-age=300` for HTML to control freshness explicitly -- prevents stale auth state and SPA shell drift.

Server-Timing Observability

No Server-Timing header found

REVIEW

No Server-Timing header found

Server-Timing exposes backend timing breakdowns to browser DevTools (e.g., `db: 45ms; render: 120ms; cache: 2ms`). Useful for diagnosing slow pages without backend log access. Most modern frameworks (Next.js, Cloudflare Workers, Fastly) emit it automatically; absence on a managed platform usually means telemetry headers are stripped at the edge.

Green Hosting

Action

Whether the site is served from green-energy infrastructure

REVIEW

Green Hosting

No green hosting detected

A+

Page Weight Budget

523 KB transferred, 49 requests

PASS

523 KB transferred, 49 requests

Page weighs 687 KB (523 KB transferred)

49 HTTP requests

Estimated 0.11 g CO2 per page load

523 KB transferred

49 requests

0.11 g CO2 per page load

Images 286.8 KiB 55%

CSS 106.4 KiB 20%

JavaScript 105.6 KiB 20%

HTML 10.0 KiB 2%

Other 6.8 KiB 1%

Other 6.4 KiB 1%

Other 637 B 0%

0 2.4 MB 4.9 MB

Under budget

A+

Third-Party Impact

18% third-party, 0 ms blocking

PASS

18% third-party, 0 ms blocking

Third-party code accounts for 18% of page weight (92.2 KiB of 522.6 KiB)

Third-party blocking time is low (0 ms)

82%

18%

First-party Third-party

A+

Text Compression

All text resources are compressed

PASS

All text resources are compressed

All text resources are properly compressed.

A+

Font Loading

No web fonts (system fonts)

PASS

No web fonts (system fonts)

No web fonts loaded — system fonts are fastest

No web fonts loaded — system fonts are optimal.

JS Bundles

2 scripts, 42 KB unused

PASS

2 scripts, 42 KB unused

https://mc.yandex.ru/metrika/tag.js?id=112174020: 42 KB unused (49%)

Consider code splitting or tree shaking to reduce unused code.

https://apprestore.ru/assets/app.js: unminified — 3 KB could be saved

Total unused JavaScript: 42 KB

42 KB unused JavaScript

Downloaded but never executed on this page.

Script	Size	Unused	Minified	Party
https://mc.yandex.ru/metrika/tag.js?id=112174020	87 KB	42 KB (49%)	✓	3rd
https://apprestore.ru/assets/app.js	19 KB	—	✗	1st

Consider code splitting or tree shaking to reduce unused code.

Why this matters

This bundle has high unused code — code-split or tree-shake to ship only what executes.

Source: web.dev / Lighthouse coverage

A+

Resource Caching

All resources properly cached

PASS

All resources properly cached

No caching issues found

All static resources have appropriate caching headers.

A+

Critical Rendering Path

No render-blocking resources

PASS

No render-blocking resources

No render-blocking resources detected

A+

Resource Hints

No optimization needed

PASS

No optimization needed

No resource hint issues

A+

LCP Image Preload

LCP preload audit not available

PASS

LCP preload audit not available

LCP image preload audit not available for this scan

Server Response Intelligence

2 server-response signal(s) detected

PASS

2 server-response signal(s) detected

Compressed response missing `Vary` header

The page is served with `Content-Encoding: gzip` but has no `Vary` header. Without `Vary: Accept-Encoding`, intermediary caches (corporate proxies, ISP caches) may serve the compressed variant to clients that didn't send the matching `Accept-Encoding` -- the client sees garbled bytes. Add `Vary: Accept-Encoding` whenever the response is conditionally compressed.

No `ETag` or `Last-Modified` -- conditional GET not supported

Without either header, browsers can't issue conditional GETs and refresh always re-downloads the full response body even when nothing changed. Add `ETag: "<hash>"` (or `Last-Modified: <date>`) on cacheable responses; the server returns 304 Not Modified when the client's cached copy is still valid, saving bandwidth.

A+

Page Weight Inventory

49 resources · 523 KB · 42 KB savings available

PASS

49 resources · 523 KB · 42 KB savings available

Within 1MB page-weight target

Got: 523 KB

10 third-party resources (18% of weight)

49 resources · 522.6 KiB · 10 third-party Within 1MB page-weight target

Image 55% · 289.3 KiB

CSS 20% · 106.4 KiB

JavaScript 20% · 105.6 KiB

Other 2% · 11.3 KiB

Document 2% · 10.0 KiB

~42.2 KiB of savings available

Remove unused JavaScript: 42.2 KiB

#	Resource	Type	Size	Cache	Unused	3rd party	Issues

49 resources			522.6 KiB

A+

Render-Blocking Resources

No render-blocking resources detected

PASS

No render-blocking resources detected

No render-blocking resources detected in <head>

A+

Third-Party Resources

No third-party resources detected

PASS

No third-party resources detected

JavaScript Blocking

1 JS blocking issue(s) detected

PASS

1 JS blocking issue(s) detected

Total JS execution time is 8.4 s -- over the 3.5s budget

Total JavaScript execution (parse + compile + run) across all scripts exceeds 3.5 seconds. On low-end devices that becomes 7-15+ seconds and shows up directly in TBT and INP. Reduce by: tree-shaking unused dependencies, code-splitting (dynamic `import()`), removing or deferring third-party tracking, and replacing heavy frameworks where they're not needed.

A+

CSS Performance Depth

No CSS performance depth issues detected

PASS

No CSS performance depth issues detected

Network Waterfall

49 requests over 4111ms

INFO

HTML JavaScript CSS Images Fonts XHR/Fetch Other

Third-Party Script Cost

Per-script blocking time, transfer cost, and cache headers

INFO

11% of JavaScript execution is third-party

First-party Third-party 895ms · 87KB · ₽466/mo

Script	Category	Execution	Transfer	Unused	Monthly Cost	Verdict
mc.yandex.ru mc.yandex.ru	Other	895ms	87 KB	49%	₽466/mo	Costly

mc.yandex.ru

Other

Costly

Execution 895ms

Transfer 87 KB

Unused 49%

Monthly Cost ₽466/mo

These scripts may cost more than they're worth

mc.yandex.ru adds 895ms and costs ~₽466/month

mc.yandex.ru takes 895ms of CPU time. Consider loading it asynchronously or replacing it with a lighter alternative.

Why this matters

This script has high main-thread execution time — optimize hot paths or defer.

Source: web.dev

How third-party costs are calculated

Image Optimization

65 images, 116 KB total, 0 KB wasted

INFO

Image Optimization Audit

Total Images

Total Size

116 KB

57 missing dimensions

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.