WordPress on Sucuri: readiness playbook

Readiness by lane

The WordPress on Sucuri playbook

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

1. Static files cached for 30 days or more

   <1% 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 WordPress: Caching plugins or your host can set long browser cache lifetimes for theme and plugin assets.

   Guide: Browser Caching Guide for Website Owners

2. HSTS kept for at least a year

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

   Guide: HTTPS and TLS Guide for Website Owners

3. No render-blocking scripts in <head>

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

   On WordPress: Since WordPress 6.3, scripts can be registered with a defer or async loading strategy.

   Guide: Control Third-Party Scripts Before They Control Your Page

4. security.txt published

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

   Guide: A Practical Website Health Check for Owners

5. Modern image formats in use

   35% 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 WordPress: WordPress has supported WebP uploads since 5.8 and AVIF since 6.5; image plugins or the host can convert existing images.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

6. CAA records limit who can issue certificates

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

   Guide: HTTPS and TLS Guide for Website Owners

7. DMARC policy enforces quarantine or reject

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

   Guide: A Practical Website Health Check for Owners

8. DNSSEC signed

   6.8% 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

Where WordPress on Sucuri sites lead

• HTTP/3 advertised96% observedall sites 36%
• Content Security Policy present91% observedall sites 31%
• Framing restricted92% observedall sites 49%
• X-Content-Type-Options: nosniff89% observedall sites 48%

All 31 checks on WordPress on Sucuri

High-readiness WordPress on Sucuri sites

• riovagas.com.br66

Related