Stack playbook · Snapshot 23 October 2026
Gatsby on Amazon CloudFront: readiness playbook
What 113 measured sites on this stack get right, where they fall short, and the Gatsby on Amazon CloudFront-specific steps that close each gap.
- Sites measured
- 113
- Median readiness index
- 72/100
- Profiles on this stack
- 16
detected from homepage HTML and headers
all sites: 64
top-50K sites
Readiness by lane
Enable
86/100
All sites 77
Harden
65/100
All sites 55
Accelerate
71/100
All sites 63
Recover
8/100
All sites 11
The Gatsby on Amazon CloudFront playbook
Gaps ordered by impact, with the platform-specific step where one exists.
security.txt published
8.2% 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.
Static files cached for 30 days or more
46% 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.
HTTP/3 advertised
25% observed · all sites 36%
Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
On Amazon CloudFront: Select HTTP/3 in the distribution's supported HTTP versions.
DNSSEC signed
11% 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
Certificate lifetime of 100 days or less
12% observed · all sites 75%
Move to automated issuance and renewal now, while you still have time to test it.
Content Security Policy present
41% 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
69% 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.
On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.
Where Gatsby on Amazon CloudFront sites lead
- DMARC policy enforces quarantine or reject71% observedall sites 31%
- HSTS kept for at least a year69% observedall sites 31%
- Modern image formats in use71% observedall sites 40%
- Offscreen images lazy-loaded85% observedall sites 61%