Category benchmark · Snapshot 23 October 2026
Website Builders: website readiness
31 configuration checks across 38 Website Builders sites from the SID website catalog, with 26 individual profiles for sites in the Chrome UX Report top 50K.
- Sites measured
- 38
- Median readiness index
- 64/100
- Profiles
- 26
- Weakest lane
- Recover
all popularity bands
all sites: 64
top-50K sites
lowest weighted score
Readiness by lane
Enable
81/100
All sites 77
Harden
58/100
All sites 56
Accelerate
63/100
All sites 64
Recover
5/100
All sites 10
Biggest gaps for Website Builders sites
The checks with the most room to improve, weighted by impact.
HSTS kept for at least a year
26% 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.
Static files cached for 30 days or more
42% 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.
CAA records limit who can issue certificates
16% 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.
security.txt published
16% 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.
No render-blocking scripts in <head>
34% 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
Content Security Policy present
26% 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 Website Builders sites lead
- DMARC policy enforces quarantine or reject61% observedall sites 39%
- Modern image formats in use62% observedall sites 40%
- Social preview image set74% observedall sites 57%
- robots.txt published89% observedall sites 76%
Stack mix
CDN and edge
- Cloudflare37%
- Google edge7.9%
- Amazon CloudFront5.3%
- Vercel2.6%
Platform or framework
DNS operator
- Cloudflare34%
- Amazon Route 5324%
- NS17.9%
- Squarespace DNS5.3%
- Google Cloud DNS2.6%
- Xserver/Value-Domain DNS2.6%
Certificate authority
- Let's Encrypt45%
- Google Trust Services32%
- Amazon7.9%
- GlobalSign5.3%
- DigiCert2.6%
- Key-Systems GmbH2.6%
- PerfectSSL2.6%
- TAIWAN-CA2.6%
Readiness leaders
Website Builders sites in the top 50K with the highest share of observed practices (at least 26 of 31 checks measured). This lists only what we observed on 23 October 2026; owners can request a correction.
- framer.com88/100
- msha.ke86/100
- webflow.com82/100
- wordpress.org80/100
- bolt.new79/100
- webnode.com79/100
- wix.com76/100
- squarespace.com74/100
- wfolio.ru74/100
- neocities.org73/100
All 31 checks for Website Builders
Website Builders profiles
Readiness index shown next to each site.
- bio.site62
- bolt.new79
- bridgewebs.com41
- carrd.com62
- comicfury.com56
- framer.com88
- joy.link56
- linkcloud.ai65
- lit.link67
- msha.ke86
- nanos.jp38
- neocities.org73
- oopsie.bio52
- sfl.gl71
- shop2000.com.tw37
- squarespace.com74
- straw.page62
- taplink.cc58
- tilda.cc60
- videosflow.sbs52
- webflow.com82
- webnode.com79
- weebly.com59
- wfolio.ru74
- wix.com76
- wordpress.org80