Stack playbook · Snapshot 23 October 2026
Drupal on Akamai: readiness playbook
What 103 measured sites on this stack get right, where they fall short, and the Drupal on Akamai-specific steps that close each gap.
- Sites measured
- 103
- Median readiness index
- 70/100
- Profiles on this stack
- 23
detected from homepage HTML and headers
all sites: 64
top-50K sites
Readiness by lane
Enable
84/100
All sites 77
Harden
68/100
All sites 55
Accelerate
61/100
All sites 63
Recover
15/100
All sites 11
The Drupal on Akamai playbook
Gaps ordered by impact, with the platform-specific step where one exists.
Static files cached for 30 days or more
26% 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.
Modern image formats in use
38% 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
No render-blocking scripts in <head>
27% 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
HSTS kept for at least a year
49% 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.
security.txt published
10% 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
11% 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.
HTTP/3 advertised
30% observed · all sites 36%
Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
DNSSEC signed
24% 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 Drupal on Akamai sites lead
- DMARC policy enforces quarantine or reject78% observedall sites 31%
- X-Content-Type-Options: nosniff89% observedall sites 48%
- Framing restricted88% observedall sites 49%
- Reachable over IPv667% observedall sites 44%