Stack playbook · Snapshot 23 October 2026
Nuxt on Google edge: readiness playbook
What 136 measured sites on this stack get right, where they fall short, and the Nuxt on Google edge-specific steps that close each gap.
- Sites measured
- 136
- Median readiness index
- 68/100
- Profiles on this stack
- 28
detected from homepage HTML and headers
all sites: 64
top-50K sites
Readiness by lane
Enable
83/100
All sites 77
Harden
56/100
All sites 55
Accelerate
81/100
All sites 63
Recover
9/100
All sites 11
The Nuxt on Google edge playbook
Gaps ordered by impact, with the platform-specific step where one exists.
HSTS kept for at least a year
31% observed · all sites 31%
Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.
DMARC policy enforces quarantine or reject
36% observed · all sites 31%
Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.
CAA records limit who can issue certificates
5.1% observed · all sites 11%
Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.
security.txt published
8.6% observed · all sites 5.5%
Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.
DNSSEC signed
4.4% observed · all sites 8.1%
Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.
Guide: Website Uptime Readiness: Prepare Before Traffic Arrives
Content Security Policy present
30% observed · all sites 31%
Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.
Guide: Payment Security and PCI DSS: What Website Owners Need to Know
Modern image formats in use
55% observed · all sites 40%
Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.
On Nuxt: Nuxt Image can output WebP and AVIF.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Framing restricted
46% observed · all sites 49%
Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.
Where Nuxt on Google edge sites lead
- HTTP/3 advertised79% observedall sites 36%
- No render-blocking scripts in <head>86% observedall sites 44%
- Static files cached for 30 days or more76% observedall sites 50%
- Social preview image set72% observedall sites 55%