Stack playbook · Snapshot 23 October 2026
WordPress on Imperva: readiness playbook
What 112 measured sites on this stack get right, where they fall short, and the WordPress on Imperva-specific steps that close each gap.
- Sites measured
- 112
- Median readiness index
- 66/100
- Profiles on this stack
- 12
detected from homepage HTML and headers
all sites: 64
top-50K sites
Readiness by lane
Enable
85/100
All sites 77
Harden
62/100
All sites 55
Accelerate
55/100
All sites 63
Recover
10/100
All sites 11
The WordPress on Imperva playbook
Gaps ordered by impact, with the platform-specific step where one exists.
Modern image formats in use
31% 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
No render-blocking scripts in <head>
18% 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
HTTP/3 advertised
0% observed · all sites 36%
Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
Static files cached for 30 days or more
34% 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.
security.txt published
1.9% 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.
CAA records limit who can issue certificates
8% 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.
HSTS kept for at least a year
61% 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.
DNSSEC signed
8.9% 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 Imperva sites lead
- HSTS kept for at least a year61% observedall sites 31%
- DMARC policy enforces quarantine or reject60% observedall sites 31%
- Canonical URL declared94% observedall sites 70%
- Structured data present76% observedall sites 53%