Stack playbook · Snapshot 23 October 2026
Nuxt: readiness playbook
What 630 measured sites on this platform or framework get right, where they fall short, and the Nuxt-specific steps that close each gap.
- Sites measured
- 630
- Median readiness index
- 68/100
- Profiles on this stack
- 362
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 56
Accelerate
74/100
All sites 64
Recover
13/100
All sites 10
The Nuxt playbook
Gaps ordered by impact, with the platform-specific step where one exists.
HSTS kept for at least a year
35% observed · all sites 34%
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.
CAA records limit who can issue certificates
9.2% observed · all sites 13%
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
11% observed · all sites 7.1%
Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.
DMARC policy enforces quarantine or reject
45% observed · all sites 39%
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.
Content Security Policy present
27% observed · all sites 32%
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
DNSSEC signed
9.2% observed · all sites 8%
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
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
HTTP/3 advertised
36% observed · all sites 37%
Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
Where Nuxt sites lead
- No render-blocking scripts in <head>74% observedall sites 48%
- Static files cached for 30 days or more68% observedall sites 51%
- Modern image formats in use55% observedall sites 40%
- robots.txt published91% observedall sites 76%