t-j.ru

Readiness by lane

Green: t-j.ru. Thin bar: Online Publishing peer median.

Priority fixes for t-j.ru

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.

   92% of Online Publishing 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

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   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.

   89% of Online Publishing peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

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

   27% of Online Publishing peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

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.

   41% of Online Publishing peers do this.

   Guide: CDN Guide for Website Owners

What t-j.ru already does well

Practices fewer than half of Online Publishing peers use.

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

What we saw

Homepage checked

https://t-j.ru/

Homepage response

HTTP 200

TLS

TLSv1.2, http/1.1

Certificate

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

DNS operators

RU-CENTER DNS, plus 1 self-run or other nameserver domain

DMARC policy

p=reject

Homepage HTML

2,645 KB, gzip

Images on homepage

266 (jpg 987, png 329, webp 5)

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 Online Publishing sites

• 1101.com63
• rewayatna.com64
• setare.com64
• spunteblu.it64
• toptoon.jp64

Online Publishing readiness benchmark