Website readiness profile · Snapshot 23 October 2026
example.com
example.com's public homepage, certificate and DNS checked against 31 practices and compared with 343 Uncategorized sites.
- Readiness index
- 45/100
- Ahead of
- 8.7%
- Practices observed
- 12/28
- Popularity band
- Top 50K
Uncategorized median 62
of measured Uncategorized sites
3 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: example.com. Thin bar: Uncategorized peer median.
Enable
38/100
Peers 80
Harden
42/100
Peers 54
Accelerate
73/100
Peers 58
Recover
0/100
Peers 12
Priority fixes for example.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://example.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.
On Cloudflare: Turn on Always Use HTTPS under SSL/TLS > Edge Certificates.
88% of Uncategorized peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.
Priority 2 · Enable
robots.txt published
Observed: No robots.txt file was returned at the site root.
What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.
88% of Uncategorized peers do this.
Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes
Priority 3 · Enable
XML sitemap discoverable
Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.
What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.
75% of Uncategorized peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 4 · Harden
HSTS kept for at least a year
Observed: The homepage response did not include a Strict-Transport-Security header.
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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.
34% of Uncategorized peers do this.
What example.com already does well
Practices fewer than half of Uncategorized peers use.
- DNSSEC signedDNSSEC delegation (DS record) present.9.3% of peers
- HTTP/3 advertisedHTTP/3 advertised.33% of peers
- No render-blocking scripts in <head>Head scripts load without blocking.37% of peers
What we saw
- Homepage checked
- https://example.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- SSL Corporation, 90-day validity, expiring 2026-12-25
- CDN or edge
- Cloudflare
- DNS operators
- Cloudflare
- DMARC policy
- p=reject
- Homepage HTML
- 1 KB, br
- Images on homepage
- 0
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 16
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- CAA records limit who can issue certificates
- security.txt published
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- Static files cached for 30 days or more
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Structured data present
- Social preview image set
- Nameservers spread across providers
Observed 12
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- DNSSEC signed
- DMARC policy enforces quarantine or reject
- HTTP/2 negotiated
- HTTP/3 advertised
- No render-blocking scripts in <head>
- Reachable over IPv6
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
Not measured 3
- HTML compressed
- Modern image formats in use
- Offscreen images lazy-loaded
Own example.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: example.com. This profile covers configuration only.