myhealthone.com

Readiness by lane

Green: myhealthone.com. Thin bar: Fitness & Health peer median.

Priority fixes for myhealthone.com

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Enable

   robots.txt published

   Observed: No robots.txt file was returned at the site root.

   Why it matters: robots.txt is where crawlers look first for crawl rules and sitemap locations. Without it, they assume everything is open.

   What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

   89% of Fitness & Health peers do this. Limit: Only the standard location was requested, once, at the time of the check.

   Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes

2. Priority 2 · 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 Next.js: Add the header in the headers() option of next.config.js for all routes.

   43% of Fitness & Health peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. 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.

   78% of Fitness & Health peers do this.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

4. Priority 4 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 4 seconds, 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.

   56% of Fitness & Health peers do this.

   Guide: Browser Caching Guide for Website Owners

What myhealthone.com already does well

Practices fewer than half of Fitness & Health peers use.

• CAA records limit who can issue certificatesCAA limits issuance to identrust.com, letsencrypt.org, pki.goog and others.11% of peers
• HTTP/3 advertisedHTTP/3 advertised.29% of peers
• Content Security Policy presentContent-Security-Policy present.38% of peers

What we saw

Homepage checked

https://myhealthone.com/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

IdenTrust, 198-day validity, expiring 2027-04-11

CDN or edge

Akamai

Platform or framework

Next.js, Sitecore

DNS operators

Azure DNS

DMARC policy

p=reject

Homepage HTML

232 KB, gzip

Images on homepage

29 (svg 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

Compare with other Fitness & Health sites

• darooyab.ir60
• drhast.com60
• hazipatika.com60
• lekarzebezkolejki.pl59
• maiia.com59

Fitness & Health readiness benchmark