Website readiness profile · Snapshot 23 October 2026
chatlyverse.com
chatlyverse.com's public homepage, certificate and DNS checked against 31 practices and compared with 94 Generative AI Chatbots & Assistants sites.
- Readiness index
- 28/100
- Ahead of
- 0%
- Practices observed
- 7/28
- Popularity band
- Top 50K
Generative AI Chatbots & Assistants median 73
of measured Generative AI Chatbots & Assistants sites
3 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: chatlyverse.com. Thin bar: Generative AI Chatbots & Assistants peer median.
Enable
69/100
Peers 89
Harden
14/100
Peers 62
Accelerate
0/100
Peers 77
Recover
0/100
Peers 4
Priority fixes for chatlyverse.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HTTP requests move to HTTPS
Observed: A request to http://www.chatlyverse.com/ was not redirected to HTTPS.
Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.
What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.
96% of Generative AI Chatbots & Assistants peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.
Priority 2 · Accelerate
HTML compressed
Observed: The homepage HTML (5 KB) was delivered without gzip, Brotli or zstd compression.
What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.
98% of Generative AI Chatbots & Assistants peers do this.
Guide: How to Set a Website Performance Budget That Teams Can Keep
Priority 3 · Accelerate
HTTP/2 negotiated
Observed: The TLS handshake selected HTTP/1.1 instead of HTTP/2.
What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.
97% of Generative AI Chatbots & Assistants peers do this.
Priority 4 · Harden
TLS 1.3 negotiated
Observed: The TLS connection negotiated TLSv1.2.
What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.
97% of Generative AI Chatbots & Assistants peers do this.
What we saw
- Homepage checked
- https://www.chatlyverse.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.2
- Certificate
- Amazon, 197-day validity, expiring 2027-04-06
- DNS operators
- Amazon Route 53
- Homepage HTML
- 5 KB, uncompressed
- Images on homepage
- 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 21
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- 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
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- No render-blocking scripts in <head>
- Reachable over IPv6
- Canonical URL declared
- Structured data present
- Social preview image set
- Nameservers spread across providers
Observed 7
- Certificate has more than 14 days left
- robots.txt published
- XML sitemap discoverable
- Meta description written
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
Not measured 3
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
Own chatlyverse.com?
Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.
Live status for this site: Status Is Down: chatlyverse.com. This profile covers configuration only.