Stack playbook · Snapshot 23 October 2026
Tilda: readiness playbook
What 249 measured sites on this hosted platform get right, where they fall short, and the Tilda-specific steps that close each gap.
- Sites measured
- 249
- Median readiness index
- 56/100
- Profiles on this stack
- 9
detected from homepage HTML and headers
all sites: 64
top-50K sites
Readiness by lane
Enable
79/100
All sites 77
Harden
48/100
All sites 55
Accelerate
46/100
All sites 63
Recover
15/100
All sites 11
The Tilda playbook
Gaps ordered by impact, with the platform-specific step where one exists.
HSTS kept for at least a year
7.6% 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.
DMARC policy enforces quarantine or reject
16% 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.
Modern image formats in use
22% 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>
8.8% 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
Static files cached for 30 days or more
27% 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.
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.
Content Security Policy present
3.6% 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.
Guide: Payment Security and PCI DSS: What Website Owners Need to Know
CAA records limit who can issue certificates
4% 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.
Where Tilda sites lead
- Framing restricted77% observedall sites 49%
- Social preview image set83% observedall sites 55%
- XML sitemap discoverable94% observedall sites 73%
- Canonical URL declared91% observedall sites 70%
A note on hosted platforms
On Tilda, 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.