doctoreto.com

Readiness by lane

Green: doctoreto.com. Thin bar: Fitness & Health peer median.

Priority fixes for doctoreto.com

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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 Next.js: Add the header in the headers() option of next.config.js for all routes.

   43% of Fitness & Health peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · 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.

   78% of Fitness & Health peers do this.

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

3. Priority 3 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Next.js: Add it in next.config.js headers().

   58% of Fitness & Health peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   On Next.js: Next.js documents nonce-based CSP with middleware.

   38% of Fitness & Health peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What doctoreto.com already does well

Practices fewer than half of Fitness & Health peers use.

• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.44% of peers
• Modern image formats in useWebP or AVIF images detected.45% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.45% of peers

What we saw

Homepage checked

https://doctoreto.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Asseco Data Systems S.A., 198-day validity, expiring 2027-02-15

Platform or framework

WordPress, Next.js

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=quarantine

Homepage HTML

2,822 KB, gzip

Images on homepage

729 (jpg 822, png 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

Compare with other Fitness & Health sites

• clinikally.com64
• drmyco.ir64
• ekshef.com64
• poradnikzdrowie.pl65
• tennisenpadelvlaanderen.be65

Fitness & Health readiness benchmark