Stack playbook · Snapshot 23 October 2026
Gatsby: readiness playbook
What 301 measured sites on this platform or framework get right, where they fall short, and the Gatsby-specific steps that close each gap.
- Sites measured
- 301
- Median readiness index
- 72/100
- Profiles on this stack
- 32
detected from homepage HTML and headers
all sites: 64
top-50K sites
Readiness by lane
Enable
82/100
All sites 77
Harden
66/100
All sites 55
Accelerate
73/100
All sites 63
Recover
7/100
All sites 11
The Gatsby playbook
Gaps ordered by impact, with the platform-specific step where one exists.
security.txt published
10% 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.
CAA records limit who can issue certificates
17% 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.
HTTP/3 advertised
26% observed · all sites 36%
Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
Static files cached for 30 days or more
51% observed · all sites 50%
Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.
DNSSEC signed
15% 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
39% 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
HSTS kept for at least a year
67% 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
62% 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.
Where Gatsby sites lead
- HSTS kept for at least a year67% observedall sites 31%
- Modern image formats in use72% observedall sites 40%
- DMARC policy enforces quarantine or reject62% observedall sites 31%
- Referrer-Policy set49% observedall sites 23%