STATUS IS UPWEBSITE READINESS

Stack playbook · Snapshot 23 October 2026

PrestaShop on Cloudflare: readiness playbook

What 528 measured sites on this stack get right, where they fall short, and the PrestaShop on Cloudflare-specific steps that close each gap.

Sites measured
528

detected from homepage HTML and headers

Median readiness index
66/100

all sites: 64

Profiles on this stack
22

top-50K sites

Readiness by lane

Enable

86/100

All sites 77

Harden

54/100

All sites 55

Accelerate

72/100

All sites 63

Recover

2/100

All sites 11

The PrestaShop on Cloudflare playbook

Gaps ordered by impact, with the platform-specific step where one exists.

  1. HSTS kept for at least a year

    21% 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.

  2. DMARC policy enforces quarantine or reject

    32% 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.

  3. security.txt published

    3.6% 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.

  4. CAA records limit who can issue certificates

    10% 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.

  5. Static files cached for 30 days or more

    42% 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.

    On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.

  6. Content Security Policy present

    16% 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.

  7. Modern image formats in use

    44% 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.

  8. DNSSEC signed

    5.5% 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.

Where PrestaShop on Cloudflare sites lead

  • Reachable over IPv695% observedall sites 44%
  • HTTP/3 advertised78% observedall sites 36%
  • Structured data present79% observedall sites 53%
  • Certificate lifetime of 100 days or less98% observedall sites 75%

All 31 checks on PrestaShop on Cloudflare

High-readiness PrestaShop on Cloudflare sites

Related