Intentional for dynamic content, but increases server load for every page view.
Got: no-store, no-cache, must-revalidate
Info::
i
No ETag or Last-Modified header
Conditional requests (304 Not Modified) are not possible without validators.
Cache-Control
no-store, no-cache, must-revalidate
Directive
Value
Meaning
no-store
—
Never cache this response
no-cache
—
Cache but always revalidate first
must-revalidate
—
Must recheck with server after expiry
C
Image Optimization
Action
44 images, 0 KB saveable
REVIEW
44 images, 0 KB saveable
Warning::
!
https://needguide.net/images/ng_logo_black.png is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://needguide.net/images/search_black.png is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://needguide.net/images/flags/peru.png is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://needguide.net/images/flags/argentina.png is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://needguide.net/images/ng_logo_white.png is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://needguide.net/images/input_black.png is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://needguide.net/images/flags/butan.png is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://needguide.net/images/flags/usa.png is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
44images2.1 MB
0oversized-0 KB
16legacy format
8missing 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
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.
B
Document Compression
Document response uses gzip; brotli would be ~20% smaller
REVIEW
Document response uses gzip; brotli would be ~20% smaller
Info::
i
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.
B
Asset Compression
1 of 1 asset host serve text uncompressed
REVIEW
1 of 1 asset host serve text uncompressed
Warning::
!
www.google.com serves text assets uncompressed (assets: 6)
The sampled response carries a text content type but no Content-Encoding, so the bytes go over the wire raw. Text compression typically removes 70-80% of a JS or CSS payload -- this is the single cheapest transfer win available on this host.
Got: www.google.com (text/html)
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.
B
JavaScript Blocking
2 JS blocking issue(s) detected
REVIEW
2 JS blocking issue(s) detected
Warning::
!
1 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 3.6 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
28% third-party, 0 ms blocking
PASS
28% third-party, 0 ms blocking
Info::
i
Third-party code accounts for 28% of page weight (845.6 KiB of 2.9 MiB)
Info::
✓
Third-party blocking time is low (0 ms)
72%
28%
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
3 fonts (92 KB)
PASS
3 fonts (92 KB)
Info::
i
3 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
3
92 KB total
Render-blocking
0
of 3
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
memvYaGs126MiZpBA-UvWbX...woff2swap
Size22 KB
Load time33 ms
Start1.0 s
RiskFOUT — text flashes from fallback to web font
memtYaGs126MiZpBA-UFUIc...woff2swap
Size27 KB
Load time33 ms
Start1.0 s
RiskFOUT — text flashes from fallback to web font
memvYaGs126MiZpBA-UvWbX...woff2swap
Size42 KB
Load time27 ms
Start1.0 s
RiskFOUT — text flashes from fallback to web font
Optimization checklist
Preload critical fonts (priority=high)
Use woff2 format for all fonts
Set font-display to swap, optional, or fallback
Subset large fonts (≤100 KB each)
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+
Main HTML Cache-Control
Main HTML uses no-store -- correct for sensitive/dynamic content
PASS
Main HTML uses no-store -- correct for sensitive/dynamic content
Info::
✓
Main HTML uses no-store -- correct for sensitive/dynamic content
Got: no-store, no-cache, must-revalidate
A+
Server Response Intelligence
2 server-response signal(s) detected
PASS
2 server-response signal(s) detected
Info::
✓
`Vary` header declared: Accept-Encoding
The page declares a `Vary` header, telling downstream caches which request headers the response varies on. Critical for content-negotiated responses (compression, language, cookies, device class).
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.
A+
Render-Blocking Resources
No render-blocking resources detected
PASS
No render-blocking resources detected
Info::
✓
No render-blocking resources detected in <head>
A+
Third-Party Resources
No third-party resources detected
PASS
No third-party resources detected
A+
CSS Performance Depth
No CSS performance depth issues detected
PASS
No CSS performance depth issues detected
Info::
✓
No CSS performance depth issues detected
Network Waterfall
77 requests over 3004ms
INFO
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
48%of JavaScript execution is third-party
First-party Third-party1728ms · 724KB · ₽512/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
Google Tag Manager
www.googletagmanager.com
Tag Manager
446ms
179 KB
43%
₽132/mo
Costly
mc.yandex.ru
mc.yandex.ru
Other
372ms
90 KB
59%
₽110/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
337ms
188 KB
32%
₽100/mo
Costly
mc.yandex.ru
mc.yandex.ru
Other
231ms
88 KB
65%
₽68/mo
Costly
mc.yandex.com
mc.yandex.com
Other
127ms
32 KB
—
₽38/mo
Optional
www.google.com
www.google.com
Other
113ms
127 KB
69%
₽33/mo
Optional
Google Analytics
www.google-analytics.com
Analytics
101ms
21 KB
—
₽30/mo
Optional
Google Tag Manager
Tag Manager
Costly
Execution446ms
Transfer179 KB
Unused43%
Monthly Cost₽132/mo
mc.yandex.ru
Other
Costly
Execution372ms
Transfer90 KB
Unused59%
Monthly Cost₽110/mo
Google Tag Manager
Tag Manager
Costly
Execution337ms
Transfer188 KB
Unused32%
Monthly Cost₽100/mo
mc.yandex.ru
Other
Costly
Execution231ms
Transfer88 KB
Unused65%
Monthly Cost₽68/mo
mc.yandex.com
Other
Optional
Execution127ms
Transfer32 KB
Monthly Cost₽38/mo
www.google.com
Other
Optional
Execution113ms
Transfer127 KB
Unused69%
Monthly Cost₽33/mo
Google Analytics
Analytics
Optional
Execution101ms
Transfer21 KB
Monthly Cost₽30/mo
These scripts may cost more than they're worth
Google Tag Manager adds 446ms and costs ~₽132/month
mc.yandex.ru adds 372ms and costs ~₽110/month
Google Tag Manager adds 337ms and costs ~₽100/month
mc.yandex.ru adds 231ms and costs ~₽68/month
48% of JavaScript execution time comes from third-party scripts.
Why this matters
Third-party scripts (analytics, ads, social, A/B testing) often dominate execution time — every one is a perf-and-privacy tax.
Learn more ▾▴
Each third-party script is a black box: you don't control when it loads, what it executes, or how much it grows. They often account for a major share of total blocking time on average sites (HTTP Archive's Web Almanac documents the trend). Audit which ones you actually need, defer the rest, and use facade patterns (lite-youtube, lite-vimeo) for embedded media.
Source: web.dev / HTTP Archive Web Almanac
Google Tag Manager takes 446ms 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 372ms 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
59% 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
Google Tag Manager takes 337ms 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 231ms 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
65% 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
69% of www.google.com'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.