STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

rtings.com

rtings.com's public homepage, certificate and DNS checked against 31 practices and compared with 190 Ratings & Reviews sites.

Readiness index
70/100

Ratings & Reviews median 66

Ahead of
63%

of measured Ratings & Reviews sites

Practices observed
20/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:13:12 UTC from one location. How we measure

Readiness by lane

Green: rtings.com. Thin bar: Ratings & Reviews peer median.

Enable

95/100

Peers 82

Harden

62/100

Peers 54

Accelerate

63/100

Peers 68

Recover

0/100

Peers 6

Priority fixes for rtings.com

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

  1. Priority 1 · Accelerate

    HTTP/2 negotiated

    Observed: The TLS handshake selected HTTP/1.1 instead of HTTP/2.

    Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

    What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

    On Amazon CloudFront: Choose HTTP/2 (or HTTP/2 and HTTP/3) as supported versions on the distribution.

    94% of Ratings & Reviews peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

  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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

    31% of Ratings & Reviews peers do this.

  3. Priority 3 · Accelerate

    Offscreen images lazy-loaded

    Observed: The homepage had 35 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.

    65% of Ratings & Reviews peers do this.

  4. Priority 4 · Accelerate

    HTTP/3 advertised

    Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

    What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

    On Amazon CloudFront: Select HTTP/3 in the distribution's supported HTTP versions.

    40% of Ratings & Reviews peers do this.

What rtings.com already does well

Practices fewer than half of Ratings & Reviews peers use.

  • Referrer-Policy setReferrer-Policy present.26% of peers
  • DMARC policy enforces quarantine or rejectDMARC policy p=reject.37% of peers
  • Modern image formats in useWebP or AVIF images detected.37% of peers

What we saw

Homepage checked
https://www.rtings.com/
Homepage response
HTTP 200
TLS
TLSv1.3
Certificate
Amazon, 393-day validity, expiring 2027-01-15
CDN or edge
Amazon CloudFront
DNS operators
Amazon Route 53
DMARC policy
p=reject
Homepage HTML
264 KB, gzip
Images on homepage
35 (jpg 35)

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

Observed 20

  • HTTP requests move to HTTPS
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Referrer-Policy set
  • HTML compressed
  • Static files cached for 30 days or more
  • Modern image formats in use
  • No render-blocking scripts in <head>
  • 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 rtings.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: rtings.com. This profile covers configuration only.

Compare with other Ratings & Reviews sites