proza.ru

Readiness by lane

Green: proza.ru. Thin bar: Online Publishing peer median.

Priority fixes for proza.ru

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (27 KB) was delivered without gzip, Brotli or zstd compression.

   Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.

   What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.

   On Tilda: this setting is largely controlled by the platform. Check the platform's settings and documentation, or ask its support team whether it can be changed for your domain.

   94% of Online Publishing peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: How to Set a Website Performance Budget That Teams Can Keep

2. Priority 2 · Accelerate

   HTTP/2 negotiated

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

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

   On Tilda: this setting is largely controlled by the platform. Check the platform's settings and documentation, or ask its support team whether it can be changed for your domain.

   92% of Online Publishing peers do this.

   Guide: CDN 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.

   79% of Online Publishing peers do this.

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

4. Priority 4 · 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 Tilda: this setting is largely controlled by the platform. Check the platform's settings and documentation, or ask its support team whether it can be changed for your domain.

   27% of Online Publishing peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What proza.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
• Framing restrictedFraming controls present.37% of peers

What we saw

Homepage checked

https://proza.ru/

Homepage response

HTTP 200

TLS

TLSv1.3, http/1.1

Certificate

GlobalSign, 199-day validity, expiring 2027-05-08

Platform or framework

Tilda

DNS operators

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

Homepage HTML

27 KB, uncompressed

Images on homepage

12 (jpg 5, png 5, svg 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 Online Publishing sites

• dragonball-multiverse.com43
• kitappad.com42
• pogovorim.by36
• stihi.ru36
• xkcd.com39

Online Publishing readiness benchmark