Website readiness profile · Snapshot 23 October 2026
myhorsez.com
myhorsez.com's public homepage, certificate and DNS checked against 31 practices and compared with 485 Gaming Platforms & Consoles sites.
- Readiness index
- 67/100
- Ahead of
- 64%
- Practices observed
- 20/31
- Popularity band
- Top 50K
Gaming Platforms & Consoles median 62
of measured Gaming Platforms & Consoles sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: myhorsez.com. Thin bar: Gaming Platforms & Consoles peer median.
Enable
51/100
Peers 76
Harden
78/100
Peers 53
Accelerate
63/100
Peers 63
Recover
100/100
Peers 6
Priority fixes for myhorsez.com
Ordered by impact and by how common each practice is among peers.
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.
84% of Gaming Platforms & Consoles 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
Priority 2 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for no max-age, 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.
46% of Gaming Platforms & Consoles peers do this.
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.
61% of Gaming Platforms & Consoles peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 4 · 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.
49% of Gaming Platforms & Consoles peers do this.
Guide: Control Third-Party Scripts Before They Control Your Page
What myhorsez.com already does well
Practices fewer than half of Gaming Platforms & Consoles peers use.
- Nameservers spread across providersNameservers spread across more than one operator.5.8% of peers
- DNSSEC signedDNSSEC delegation (DS record) present.6.4% of peers
- Content Security Policy presentContent-Security-Policy present.22% of peers
What we saw
- Homepage checked
- https://www.myhorsez.com/
- Homepage response
- HTTP 200, after 2 redirects
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2026-11-30
- CDN or edge
- Google edge
- DNS operators
- 3 self-run or other nameserver domains
- HSTS
- max-age 365 days
- DMARC policy
- p=none
- Homepage HTML
- 169 KB, gzip
- Images on homepage
- 40 (png 15, webp 11, 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
Not observed 11
- CAA records limit who can issue certificates
- security.txt published
- DMARC policy enforces quarantine or reject
- Static files cached for 30 days or more
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Structured data present
- Social preview image set
- At most one redirect to the homepage
Observed 20
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- DNSSEC signed
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Modern image formats in use
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Page language declared
- Nameservers spread across providers
Own myhorsez.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: myhorsez.com. This profile covers configuration only.