Website readiness profile · Snapshot 23 October 2026
horoscope.com
horoscope.com's public homepage, certificate and DNS checked against 31 practices and compared with 343 Uncategorized sites.
- Readiness index
- 67/100
- Ahead of
- 61%
- Practices observed
- 19/31
- Popularity band
- Top 5K
Uncategorized median 62
of measured Uncategorized sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: horoscope.com. Thin bar: Uncategorized peer median.
Enable
92/100
Peers 80
Harden
55/100
Peers 54
Accelerate
65/100
Peers 58
Recover
0/100
Peers 12
Priority fixes for horoscope.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
TLS 1.3 negotiated
Observed: The TLS connection negotiated TLSv1.2.
Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.
What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.
On Cloudflare: Turn on TLS 1.3 under SSL/TLS > Edge Certificates.
90% of Uncategorized peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for horoscope.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.
39% of Uncategorized peers do this.
Priority 3 · Accelerate
Modern image formats in use
Observed: The homepage had 7 images and none used WebP or AVIF.
What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.
On Cloudflare: Cloudflare Polish can convert images to WebP.
33% of Uncategorized peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 4 · Accelerate
Offscreen images lazy-loaded
Observed: The homepage had 7 images and none used loading="lazy".
What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.
On WordPress: WordPress has added loading="lazy" to images by default since 5.5; check that your theme or a plugin has not removed it.
52% of Uncategorized peers do this.
What horoscope.com already does well
Practices fewer than half of Uncategorized peers use.
- HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.34% of peers
- No render-blocking scripts in <head>Head scripts load without blocking.37% of peers
- Reachable over IPv6IPv6 address published.40% of peers
What we saw
- Homepage checked
- https://www.horoscope.com/
- Homepage response
- HTTP 200, after 1 redirect
- TLS
- TLSv1.2, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2026-12-05
- CDN or edge
- Cloudflare
- Platform or framework
- WordPress
- DNS operators
- Cloudflare
- HSTS
- max-age 365 days, includeSubDomains, preload
- DMARC policy
- p=none
- Homepage HTML
- 152 KB, gzip
- Images on homepage
- 7 (jpg 9, png 2, svg 1)
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 12
- TLS 1.3 negotiated
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- Modern image formats in use
- Offscreen images lazy-loaded
- Structured data present
- Nameservers spread across providers
Observed 19
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- X-Content-Type-Options: nosniff
- Framing restricted
- HTTP/2 negotiated
- HTML compressed
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own horoscope.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: horoscope.com. This profile covers configuration only.