Website readiness profile · Snapshot 23 October 2026
hexahealth.com
hexahealth.com's public homepage, certificate and DNS checked against 31 practices and compared with 613 Fitness & Health sites.
- Readiness index
- 73/100
- Ahead of
- 67%
- Practices observed
- 21/31
- Popularity band
- Top 50K
Fitness & Health median 67
of measured Fitness & Health sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: hexahealth.com. Thin bar: Fitness & Health peer median.
Enable
95/100
Peers 82
Harden
69/100
Peers 59
Accelerate
63/100
Peers 63
Recover
0/100
Peers 10
Priority fixes for hexahealth.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · 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.
Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.
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.
56% of Fitness & Health peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for hexahealth.com was p=none, which asks receivers to take no action on failing mail.
What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.
44% of Fitness & Health peers do this.
Priority 3 · Accelerate
No render-blocking scripts in <head>
Observed: The homepage <head> loaded 1 external script 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.
On Next.js: Use the next/script component with an appropriate loading strategy.
45% of Fitness & Health peers do this.
Guide: Control Third-Party Scripts Before They Control Your Page
Priority 4 · Harden
Certificate lifetime of 100 days or less
Observed: The certificate from Amazon had a 197-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.
59% of Fitness & Health peers do this.
What hexahealth.com already does well
Practices fewer than half of Fitness & Health peers use.
- Referrer-Policy setReferrer-Policy present.33% of peers
- Content Security Policy presentContent-Security-Policy present.38% of peers
- HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.43% of peers
What we saw
- Homepage checked
- https://www.hexahealth.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-04-06
- Platform or framework
- Next.js
- DNS operators
- Amazon Route 53
- HSTS
- max-age 365 days, includeSubDomains, preload
- DMARC policy
- p=none
- Homepage HTML
- 2,203 KB, gzip
- Images on homepage
- 1,972 (png 743, svg 732, webp 485, jpg 15)
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 10
- 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
- HTTP/3 advertised
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- Reachable over IPv6
- Nameservers spread across providers
Observed 21
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/2 negotiated
- HTML compressed
- Modern image formats in use
- Offscreen images lazy-loaded
- robots.txt published
- XML sitemap discoverable
- 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
Own hexahealth.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: hexahealth.com. This profile covers configuration only.