gto.ru

Readiness by lane

Green: gto.ru. Thin bar: Fitness & Health peer median.

Priority fixes for gto.ru

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

1. Priority 1 · Harden

   Certificate has more than 14 days left

   Observed: The certificate from Let's Encrypt was due to expire on 2026-11-02 (10 days after the check).

   Why it matters: An expired certificate makes browsers show a full-page warning. Renewing well ahead of expiry leaves time to fix a failed renewal.

   What to do: Automate renewal with ACME (for example Let's Encrypt or your CDN's managed certificates) and add a renewal review to your release calendar so any certificate inside 21 days of expiry gets attention.

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

   Guide: HTTPS and TLS Guide for Website Owners

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.

   43% of Fitness & Health peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   81% of Fitness & Health peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

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.

   38% of Fitness & Health peers do this.

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

What gto.ru already does well

Practices fewer than half of Fitness & Health peers use.

• Nameservers spread across providersNameservers spread across more than one operator.9.9% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.44% of peers
• Modern image formats in useWebP or AVIF images detected.45% of peers

What we saw

Homepage checked

https://www.gto.ru/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-11-02

Platform or framework

Bitrix

DNS operators

2 self-run or other nameserver domains

DMARC policy

p=quarantine

Homepage HTML

2,420 KB, gzip

Images on homepage

344 (webp 3240, avif 2936, svg 46)

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

• gintarine.lt69
• grupposandonato.it70
• hpv.vn69
• psychologytoday.com69
• swiatprzychodni.pl70

Fitness & Health readiness benchmark