s-dri.com

Readiness by lane

Green: s-dri.com. Thin bar: Data & Analytics peer median.

Priority fixes for s-dri.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.

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

   Guide: CDN Guide for Website Owners

2. Priority 2 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 0 days, below the one-year benchmark.

   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 Fastly: Add the header in VCL or a header rule as described in Fastly's HSTS guide.

   34% of Data & Analytics 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.

   On WordPress: WordPress has generated a basic sitemap at /wp-sitemap.xml since 5.5; SEO plugins can replace it.

   63% of Data & Analytics peers do this.

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

4. Priority 4 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for s-dri.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.

   38% of Data & Analytics peers do this.

   Guide: A Practical Website Health Check for Owners

What s-dri.com already does well

Practices fewer than half of Data & Analytics peers use.

• Content Security Policy presentContent-Security-Policy present.24% of peers
• Modern image formats in useWebP or AVIF images detected.31% of peers
• Referrer-Policy setReferrer-Policy present.33% of peers

What we saw

Homepage checked

https://s-dri.com/

Homepage response

HTTP 200, after 2 redirects

TLS

TLSv1.3, http/1.1

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-14

CDN or edge

Fastly, Pantheon

Platform or framework

WordPress

DNS operators

DNS Made Easy

HSTS

max-age 0 days

DMARC policy

p=none

Homepage HTML

528 KB, gzip

Images on homepage

34 (webp 107, png 22, avif 21, jpg 14)

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 Data & Analytics sites

• leetify.com63
• lol.ps63
• nperf.com63
• statcounter.com63
• wolframalpha.com63

Data & Analytics readiness benchmark