Stack playbook · Snapshot 23 October 2026
Magento / Adobe Commerce on Cloudflare: readiness playbook
What 528 measured sites on this stack get right, where they fall short, and the Magento / Adobe Commerce on Cloudflare-specific steps that close each gap.
- Sites measured
- 528
- Median readiness index
- 72/100
- Profiles on this stack
- 50
detected from homepage HTML and headers
all sites: 64
top-50K sites
Readiness by lane
Enable
85/100
All sites 77
Harden
65/100
All sites 55
Accelerate
75/100
All sites 63
Recover
3/100
All sites 11
The Magento / Adobe Commerce on Cloudflare playbook
Gaps ordered by impact, with the platform-specific step where one exists.
HSTS kept for at least a year
39% 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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.
security.txt published
6.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.
On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.
Modern image formats in use
40% 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 Cloudflare: Cloudflare Polish can convert images to WebP.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
DMARC policy enforces quarantine or reject
41% 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.
CAA records limit who can issue certificates
12% 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.
On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.
No render-blocking scripts in <head>
37% observed · all sites 44%
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
DNSSEC signed
7.6% 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.
On Cloudflare: Enable DNSSEC in DNS > Settings and add the DS record at the registrar.
Guide: Website Uptime Readiness: Prepare Before Traffic Arrives
Content Security Policy present
38% 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
Where Magento / Adobe Commerce on Cloudflare sites lead
- Reachable over IPv694% observedall sites 44%
- X-Content-Type-Options: nosniff97% observedall sites 48%
- Framing restricted93% observedall sites 49%
- Static files cached for 30 days or more89% observedall sites 50%