Website readiness profile · Snapshot 23 October 2026
ranking.net
ranking.net's public homepage, certificate and DNS checked against 31 practices and compared with 190 Ratings & Reviews sites.
- Readiness index
- 59/100
- Ahead of
- 30%
- Practices observed
- 16/30
- Popularity band
- Top 50K
Ratings & Reviews median 66
of measured Ratings & Reviews sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: ranking.net. Thin bar: Ratings & Reviews peer median.
Enable
87/100
Peers 82
Harden
45/100
Peers 54
Accelerate
53/100
Peers 68
Recover
0/100
Peers 6
Priority fixes for ranking.net
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.
88% of Ratings & Reviews peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · Accelerate
Modern image formats in use
Observed: The homepage had 241 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.
37% of Ratings & Reviews peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 3 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for ranking.net 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.
37% of Ratings & Reviews peers do this.
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.
51% of Ratings & Reviews peers do this.
Guide: Control Third-Party Scripts Before They Control Your Page
What ranking.net already does well
Practices fewer than half of Ratings & Reviews peers use.
- Referrer-Policy setReferrer-Policy present.26% of peers
- HSTS kept for at least a yearHSTS with a 730-day max-age covering subdomains.31% of peers
- X-Content-Type-Options: nosniffnosniff header present.40% of peers
What we saw
- Homepage checked
- https://ranking.net/
- Homepage response
- HTTP 200
- TLS
- TLSv1.2, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-03-06
- DNS operators
- Amazon Route 53
- HSTS
- max-age 730 days, includeSubDomains
- DMARC policy
- p=none
- Homepage HTML
- 250 KB, gzip
- Images on homepage
- 241 (png 234, jpg 7)
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 14
- TLS 1.3 negotiated
- 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
- Content Security Policy present
- HTTP/3 advertised
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- Reachable over IPv6
- Structured data present
- Nameservers spread across providers
Observed 16
- HSTS kept for at least a year
- Certificate has more than 14 days left
- X-Content-Type-Options: nosniff
- Framing restricted
- Referrer-Policy set
- HTTP/2 negotiated
- HTML compressed
- Static files cached for 30 days or more
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Not measured 1
- HTTP requests move to HTTPS
Own ranking.net?
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: ranking.net. This profile covers configuration only.