Website readiness profile · Snapshot 23 October 2026
calendly.com
calendly.com's public homepage, certificate and DNS checked against 31 practices and compared with 50 Work Productivity Apps sites.
- Readiness index
- 88/100
- Ahead of
- 98%
- Practices observed
- 25/30
- Popularity band
- Top 5K
Work Productivity Apps median 72
of measured Work Productivity Apps sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: calendly.com. Thin bar: Work Productivity Apps peer median.
Enable
100/100
Peers 83
Harden
82/100
Peers 62
Accelerate
90/100
Peers 68
Recover
0/100
Peers 0
Priority fixes for calendly.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
Framing restricted
Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.
Why it matters: Without it, another site can load your pages in a hidden frame and trick visitors into clicking buttons (clickjacking).
What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.
On Cloudflare: Add the header with a response header transform rule.
50% of Work Productivity Apps peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Accelerate
HTTP/3 advertised
Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.
What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.
On Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.
40% of Work Productivity Apps peers do this.
Priority 3 · Harden
Content Security Policy present
Observed: The homepage response did not include a Content-Security-Policy header.
What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.
34% of Work Productivity Apps peers do this.
Guide: Payment Security and PCI DSS: What Website Owners Need to Know
Priority 4 · Harden
Referrer-Policy set
Observed: The homepage response did not include a Referrer-Policy header.
What to do: Send Referrer-Policy: strict-origin-when-cross-origin unless you have a reason to share more.
38% of Work Productivity Apps peers do this.
What calendly.com already does well
Practices fewer than half of Work Productivity Apps peers use.
- security.txt publishedsecurity.txt with a contact found.14% of peers
- DNSSEC signedDNSSEC delegation (DS record) present.20% of peers
- CAA records limit who can issue certificatesCAA limits issuance to amazon.com, comodoca.com, digicert.com and others.26% of peers
What we saw
- Homepage checked
- https://calendly.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2027-01-01
- CDN or edge
- Cloudflare, Amazon CloudFront
- Platform or framework
- Astro
- DNS operators
- Cloudflare
- HSTS
- max-age 365 days, includeSubDomains, preload
- DMARC policy
- p=quarantine
- Homepage HTML
- 854 KB, br
- Images on homepage
- 82 (svg 36, png 21, jpg 10, webp 1)
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
Not observed 5
Observed 25
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- HTTP/2 negotiated
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Not measured 1
- HTTP requests move to HTTPS
Own calendly.com?
Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.
Live status for this site: Status Is Down: calendly.com. This profile covers configuration only.