Stack playbook · Snapshot 23 October 2026
Magento / Adobe Commerce: readiness playbook
What 270 measured sites on this platform or framework get right, where they fall short, and the Magento / Adobe Commerce-specific steps that close each gap.
- Sites measured
- 270
- Median readiness index
- 72/100
- Profiles on this stack
- 133
detected from homepage HTML and headers
all sites: 64
top-50K sites
Readiness by lane
Enable
83/100
All sites 77
Harden
67/100
All sites 56
Accelerate
70/100
All sites 64
Recover
13/100
All sites 10
The Magento / Adobe Commerce playbook
Gaps ordered by impact, with the platform-specific step where one exists.
Modern image formats in use
33% 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.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
CAA records limit who can issue certificates
5.9% 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
6.8% 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>
37% 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.
Guide: Control Third-Party Scripts Before They Control Your Page
DMARC policy enforces quarantine or reject
49% 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.
HSTS kept for at least a year
60% 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.
DNSSEC signed
9.6% 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
HTTP/3 advertised
34% observed · all sites 37%
Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
Where Magento / Adobe Commerce sites lead
- X-Content-Type-Options: nosniff96% observedall sites 48%
- Framing restricted94% observedall sites 51%
- Static files cached for 30 days or more82% observedall sites 51%
- HSTS kept for at least a year60% observedall sites 34%