Stack playbook · Snapshot 23 October 2026
Webflow: readiness playbook
What 152 measured sites on this hosted platform get right, where they fall short, and the Webflow-specific steps that close each gap.
- Sites measured
- 152
- Median readiness index
- 75/100
- Profiles on this stack
- 70
detected from homepage HTML and headers
all sites: 64
top-50K sites
Readiness by lane
Enable
88/100
All sites 77
Harden
66/100
All sites 56
Accelerate
71/100
All sites 64
Recover
5/100
All sites 10
The Webflow playbook
Gaps ordered by impact, with the platform-specific step where one exists.
Static files cached for 30 days or more
28% 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.
No render-blocking scripts in <head>
20% observed · all sites 48%
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
security.txt published
11% 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
21% 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.
DNSSEC signed
15% observed · all sites 8%
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
HSTS kept for at least a year
65% 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.
X-Content-Type-Options: nosniff
30% observed · all sites 48%
Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.
Content Security Policy present
51% 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
Where Webflow sites lead
- Modern image formats in use84% observedall sites 40%
- Offscreen images lazy-loaded96% observedall sites 62%
- HSTS kept for at least a year65% observedall sites 34%
- DMARC policy enforces quarantine or reject69% observedall sites 39%
A note on hosted platforms
On Webflow, the platform controls much of the TLS, header and caching configuration. Owners mostly influence content-level checks such as images, structured data, social previews and the sitemap. Header-level gaps are worth raising with the platform.