Browsers will use heuristic caching, which can be unpredictable. Set explicit cache headers.
Info::
✓
Last-Modified header present
No Cache-Control header
Adding a Cache-Control header can significantly improve repeat-visit performance.
C
Image Optimization
Action
29 images, 0 KB saveable
REVIEW
29 images, 0 KB saveable
Warning::
!
https://etxpsych.com/wp-content/uploads/2026/01/am... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://etxpsych.com/wp-content/uploads/2026/01/bl... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://etxpsych.com/wp-content/uploads/2026/01/UH... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://etxpsych.com/wp-content/uploads/2026/01/ae... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://etxpsych.com/wp-content/uploads/2026/01/Ev... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://etxpsych.com/wp-content/uploads/2026/01/Me... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://etxpsych.com/wp-content/uploads/2026/01/Op... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
Warning::
!
https://etxpsych.com/wp-content/uploads/2026/01/UM... is missing width/height — may cause layout shift
Set explicit width and height to prevent CLS.
29images8.2 MB
0oversized-0 KB
26legacy 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.
C
Compression Algorithm
Action
Main response served uncompressed
REVIEW
Main 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.
B
JavaScript Blocking
2 JS blocking issue(s) detected
REVIEW
2 JS blocking issue(s) detected
Warning::
!
3 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 4.0 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
11% third-party, 0 ms blocking
PASS
11% third-party, 0 ms blocking
Info::
i
Third-party code accounts for 11% of page weight (1.0 MiB of 9.5 MiB)
Info::
✓
Third-party blocking time is low (0 ms)
89%
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
7 fonts (101 KB)
PASS
7 fonts (101 KB)
Info::
i
7 font(s) use font-display: swap (FOUT risk but functional)
Web fonts
7
101 KB total
Render-blocking
0
of 7
Dominant font-display
swap
Most common across fonts
Font loading timeline
TransferFOIT (block)FOUT (swap)
pxiEyp8kv8JHgFVrJJfecnF...woff2swap
Size8 KB
Load time38 ms
Start900 ms
RiskFOUT — text flashes from fallback to web font
pxiByp8kv8JHgFVrLGT9Z1x...woff2swap
Size8 KB
Load time47 ms
Start902 ms
RiskFOUT — text flashes from fallback to web font
pxiByp8kv8JHgFVrLEj6Z1x...woff2swap
Size8 KB
Load time63 ms
Start902 ms
RiskFOUT — text flashes from fallback to web font
KFO7CnqEu92Fr1ME7kSn66a...woff2swap
Size37 KB
Load time79 ms
Start902 ms
RiskFOUT — text flashes from fallback to web font
pxiByp8kv8JHgFVrLDz8Z1x...woff2swap
Size8 KB
Load time55 ms
Start902 ms
RiskFOUT — text flashes from fallback to web font
KFO7CnqEu92Fr1ME7kSn66a...woff2swap
Size34 KB
Load time113 ms
Start2.0 s
RiskFOUT — text flashes from fallback to web font
KFO7CnqEu92Fr1ME7kSn66a...woff2swap
Size0 KB
Load time0 ms
Start2.7 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
1 hints, 0 missing preconnects
PASS
1 hints, 0 missing preconnects
Info::
✓
Page uses 1 resource hint(s)
Current Resource Hints
preconnect—
preload—
dns-prefetch
1
prefetch—
1 resource hints configured
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
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::
✓
`Last-Modified` present -- timestamp-based conditional GET supported
Consider also setting `ETag` for stronger revalidation -- ETags are content hashes that don't suffer from clock-skew or DST issues. Last-Modified alone is functional for conditional GETs and not a bug.
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.
Network Waterfall
114 requests over 2652ms
INFO
HTML JavaScript CSS Images Fonts XHR/Fetch Other
Third-Party Script Cost
Per-script blocking time, transfer cost, and cache headers
INFO
38%of JavaScript execution is third-party
First-party Third-party1531ms · 157KB · $24/mo
Script
Category
Execution
Transfer
Unused
Monthly Cost
Verdict
Unattributable
Unattributable
Other
692ms
0 KB
—
$11/mo
Costly
www.gstatic.com
www.gstatic.com
Other
616ms
0 KB
48%
$10/mo
Costly
Google Tag Manager
www.googletagmanager.com
Tag Manager
222ms
157 KB
42%
$3/mo
Costly
Unattributable
Other
Costly
Execution692ms
Transfer0 KB
Monthly Cost$11/mo
www.gstatic.com
Other
Costly
Execution616ms
Transfer0 KB
Unused48%
Monthly Cost$10/mo
Google Tag Manager
Tag Manager
Costly
Execution222ms
Transfer157 KB
Unused42%
Monthly Cost$3/mo
These scripts may cost more than they're worth
Unattributable adds 692ms and costs ~$11/month
www.gstatic.com adds 616ms and costs ~$10/month
Google Tag Manager adds 222ms and costs ~$3/month
Unattributable takes 692ms 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
www.gstatic.com takes 616ms 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
Google Tag Manager takes 222ms 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.