Website readiness profile · Snapshot 23 October 2026
astrosage.com
astrosage.com's public homepage, certificate and DNS checked against 31 practices and compared with 343 Uncategorized sites.
- Readiness index
- 47/100
- Ahead of
- 12%
- Practices observed
- 14/31
- Popularity band
- Top 10K
Uncategorized median 62
of measured Uncategorized sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: astrosage.com. Thin bar: Uncategorized peer median.
Enable
79/100
Peers 80
Harden
28/100
Peers 54
Accelerate
48/100
Peers 58
Recover
0/100
Peers 12
Priority fixes for astrosage.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.astrosage.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
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 3 · 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.
Priority 4 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 4 hours, short of the 30-day benchmark.
What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.
On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.
44% of Uncategorized peers do this.
What astrosage.com already does well
Practices fewer than half of Uncategorized peers use.
- HTTP/3 advertisedHTTP/3 advertised.33% of peers
- Reachable over IPv6IPv6 address published.40% of peers
What we saw
- Homepage checked
- https://www.astrosage.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2026-11-26
- CDN or edge
- Cloudflare
- DNS operators
- Cloudflare
- Homepage HTML
- 237 KB, br
- Images on homepage
- 127 (gif 92, png 33, jpg 2)
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 17
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- 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
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- XML sitemap discoverable
- Social preview image set
- Nameservers spread across providers
Observed 14
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- robots.txt published
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Page language declared
- At most one redirect to the homepage
Own astrosage.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: astrosage.com. This profile covers configuration only.