Stack playbook · Snapshot 23 October 2026
PrestaShop: readiness playbook
What 173 measured sites on this platform or framework get right, where they fall short, and the PrestaShop-specific steps that close each gap.
- Sites measured
- 173
- Median readiness index
- 64/100
- Profiles on this stack
- 41
detected from homepage HTML and headers
all sites: 64
top-50K sites
Readiness by lane
Enable
85/100
All sites 77
Harden
55/100
All sites 56
Accelerate
65/100
All sites 64
Recover
12/100
All sites 10
The PrestaShop playbook
Gaps ordered by impact, with the platform-specific step where one exists.
HSTS kept for at least a year
24% 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.
security.txt published
6% 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.
CAA records limit who can issue certificates
9.8% 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.
DMARC policy enforces quarantine or reject
41% 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.
Modern image formats in use
41% 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
Static files cached for 30 days or more
43% observed · all sites 51%
Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.
Content Security Policy present
16% 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.
Guide: Payment Security and PCI DSS: What Website Owners Need to Know
Framing restricted
32% observed · all sites 51%
Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.
Where PrestaShop sites lead
- Structured data present80% observedall sites 51%
- robots.txt published98% observedall sites 76%
- Certificate lifetime of 100 days or less81% observedall sites 67%
- Meta description written97% observedall sites 84%