Stack playbook · Snapshot 23 October 2026
Next.js on Google edge: readiness playbook
What 169 measured sites on this stack get right, where they fall short, and the Next.js on Google edge-specific steps that close each gap.
- Sites measured
- 169
- Median readiness index
- 72/100
- Profiles on this stack
- 126
detected from homepage HTML and headers
all sites: 64
top-50K sites
Readiness by lane
Enable
86/100
All sites 77
Harden
61/100
All sites 56
Accelerate
78/100
All sites 64
Recover
10/100
All sites 10
The Next.js on Google edge playbook
Gaps ordered by impact, with the platform-specific step where one exists.
HSTS kept for at least a year
41% 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.
On Next.js: Add the header in the headers() option of next.config.js for all routes.
security.txt published
10% 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.
No render-blocking scripts in <head>
34% observed · all sites 48%
Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.
On Next.js: Use the next/script component with an appropriate loading strategy.
Guide: Control Third-Party Scripts Before They Control Your Page
CAA records limit who can issue certificates
22% 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.
Modern image formats in use
52% 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 Next.js: The next/image component serves optimized formats automatically.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
DNSSEC signed
11% 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
Content Security Policy present
36% 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.
On Next.js: Next.js documents nonce-based CSP with middleware.
Guide: Payment Security and PCI DSS: What Website Owners Need to Know
DMARC policy enforces quarantine or reject
64% 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.
Where Next.js on Google edge sites lead
- HTTP/3 advertised76% observedall sites 37%
- Static files cached for 30 days or more80% observedall sites 51%
- Offscreen images lazy-loaded91% observedall sites 62%
- DMARC policy enforces quarantine or reject64% observedall sites 39%