squarespace.com

Readiness by lane

Green: squarespace.com. Thin bar: Website Builders peer median.

Priority fixes for squarespace.com

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 180 days, below the one-year benchmark.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   What to do: 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.

   On Squarespace: this setting is largely controlled by the platform. Check the platform's settings and documentation, or ask its support team whether it can be changed for your domain.

   26% of Website Builders peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 8 external scripts without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   34% of Website Builders peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

3. Priority 3 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from DigiCert Inc had a 386-day validity period, longer than the 100-day maximum that applies from March 2027.

   What to do: Move to automated issuance and renewal now, while you still have time to test it.

   On Squarespace: this setting is largely controlled by the platform. Check the platform's settings and documentation, or ask its support team whether it can be changed for your domain.

   76% of Website Builders peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Squarespace: this setting is largely controlled by the platform. Check the platform's settings and documentation, or ask its support team whether it can be changed for your domain.

   42% of Website Builders peers do this.

   Guide: A Practical Website Health Check for Owners

What squarespace.com already does well

Practices fewer than half of Website Builders peers use.

• Nameservers spread across providersNameservers spread across NS1 and Squarespace DNS.5.3% of peers
• security.txt publishedsecurity.txt with a contact found.16% of peers
• X-Content-Type-Options: nosniffnosniff header present.39% of peers

What we saw

Homepage checked

https://www.squarespace.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 386-day validity, expiring 2027-03-03

CDN or edge

Squarespace

Platform or framework

Squarespace

DNS operators

NS1, Squarespace DNS

HSTS

max-age 180 days

DMARC policy

p=reject

Homepage HTML

608 KB, gzip

Images on homepage

77 (jpg 828, webp 805, png 54)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Website Builders sites

• bolt.new79
• neocities.org73
• webnode.com79
• wfolio.ru74
• wix.com76

Website Builders readiness benchmark