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.
C
Image Optimization
Action
76 images, 0 KB saveable
REVIEW
76 images, 0 KB saveable
Warning::
!
https://vera-m.ru/images/gallery/photo_clinics/000... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://vera-m.ru/images/gallery/photo_clinics/000... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://vera-m.ru/images/gallery/photo_clinics/000... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://vera-m.ru/images/gallery/photo_clinics/000... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://vera-m.ru/images/gallery/photo_clinics/000... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://vera-m.ru/images/gallery/photo_clinics/000... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
76images18.5 MB
0oversized-0 KB
76legacy format
6missing dimensionsCLS risk
Set explicit width and height to prevent CLS.
Why this matters
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Why this matters
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Why this matters
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Why this matters
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Why this matters
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
Set explicit width and height to prevent CLS.
Why this matters
Image without explicit width/height — browser can't reserve space; CLS jumps when image loads.
Source: web.dev / Core Web Vitals
B
HTTP/3 (QUIC)
HTTP/3 not advertised
REVIEW
HTTP/3 not advertised
Info::
i
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.
C
Document Compression
Action
Document response served uncompressed
REVIEW
Document response served uncompressed
Info::
i
Main HTML response has no Content-Encoding (uncompressed)
The main HTML document is served without compression. The Text Compression section above lists the broader picture; for the main response specifically, even gzip would shave ~70-80% off most text payloads.
B
Main HTML Cache-Control
No Cache-Control header on main HTML response
REVIEW
No Cache-Control header on main HTML response
Info::
i
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.
B
Server-Timing Observability
No Server-Timing header found
REVIEW
No Server-Timing header found
Info::
i
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.
6 render-blocking <script src> tag(s) without async/defer
Each `<script src=...>` without `async`, `defer`, or `type="module"` blocks HTML parsing while the browser fetches and executes it. The block lasts the entire round-trip + execution time -- on slow networks this translates directly into LCP delay. Add `defer` (executes after parse, in source order) for scripts that interact with the DOM, or `async` (executes whenever ready) for analytics / independent scripts. Module scripts (`type="module"`) are deferred by default.
Warning::
!
Total JS execution time is 5.2 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.
C
Green Hosting
Action
Whether the site is served from green-energy infrastructure
REVIEW
Green Hosting
No green hosting detected
A+
Third-Party Impact
1% third-party, 0 ms blocking
PASS
1% third-party, 0 ms blocking
Info::
i
Third-party code accounts for 1% of page weight (269.6 KiB of 18.9 MiB)
Info::
✓
Third-party blocking time is low (0 ms)
99%
First-party Third-party
A+
Text Compression
All text resources are compressed
PASS
All text resources are compressed
Info::
✓
All text resources are compressed
All text resources are properly compressed.
A+
Font Loading
2 fonts (64 KB)
PASS
2 fonts (64 KB)
Info::
i
2 font(s) use font-display: swap (FOUT risk but functional)
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
Info::
✓
No caching issues found
All static resources have appropriate caching headers.
A+
Critical Rendering Path
No render-blocking resources
PASS
No render-blocking resources
Info::
✓
No render-blocking resources detected
A+
Resource Hints
No optimization needed
PASS
No optimization needed
Info::
✓
No resource hint issues
A+
LCP Image Preload
LCP preload audit not available
PASS
LCP preload audit not available
Info::
✓
LCP image preload audit not available for this scan
A+
Server Response Intelligence
1 server-response signal(s) detected
PASS
1 server-response signal(s) detected
Info::
i
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.
Each `<link rel="stylesheet">` without a non-blocking `media` attribute holds up the first paint. Browsers download all of them before painting any content. Consolidate into 1-2 critical-path stylesheets; defer non-critical CSS via `<link rel="stylesheet" media="print" onload="this.media='all'">` or via the loadCSS pattern; inline above-the-fold CSS in `<style>` to short-circuit the request entirely.
Asset Compression
No text asset hosts to measure
INFO
No text asset hosts to measure
Info::
i
No third-party or subdomain host served enough text assets to measure
Asset compression is measured per host, from one HEAD request against a sampled resource. Pages that serve all their JS and CSS from the document's own origin are covered by the document compression check instead.
Network Waterfall
116 requests over 3915ms
INFO
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
25%of JavaScript execution is third-party
First-party Third-party1283ms · 163KB · ₽380/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
top-fwz1.mail.ru
top-fwz1.mail.ru
Other
576ms
20 KB
—
₽171/mo
Costly
mc.yandex.ru
mc.yandex.ru
Other
320ms
90 KB
51%
₽95/mo
Costly
privacy-cs.mail.ru
privacy-cs.mail.ru
Other
294ms
22 KB
—
₽87/mo
Costly
mc.yandex.com
mc.yandex.com
Other
93ms
31 KB
—
₽28/mo
Optional
top-fwz1.mail.ru
Other
Costly
Execution576ms
Transfer20 KB
Monthly Cost₽171/mo
mc.yandex.ru
Other
Costly
Execution320ms
Transfer90 KB
Unused51%
Monthly Cost₽95/mo
privacy-cs.mail.ru
Other
Costly
Execution294ms
Transfer22 KB
Monthly Cost₽87/mo
mc.yandex.com
Other
Optional
Execution93ms
Transfer31 KB
Monthly Cost₽28/mo
These scripts may cost more than they're worth
top-fwz1.mail.ru adds 576ms and costs ~₽171/month
mc.yandex.ru adds 320ms and costs ~₽95/month
privacy-cs.mail.ru adds 294ms and costs ~₽87/month
top-fwz1.mail.ru takes 576ms 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
mc.yandex.ru takes 320ms 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
51% of mc.yandex.ru's code is unused. The script may be loading features you don't use.
Why this matters
Bundle has high unused-code ratio — tree-shaking and route-splitting recover the wasted bytes.
Source: web.dev
privacy-cs.mail.ru takes 294ms 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.