litgorod.ru

Readiness by lane

Green: litgorod.ru. Thin bar: Literary & Knowledge peer median.

Priority fixes for litgorod.ru

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   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.

   88% of Literary & Knowledge 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 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 1 days, short of the 30-day benchmark.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   49% of Literary & Knowledge peers do this.

   Guide: Browser Caching 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.

   28% of Literary & Knowledge peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 111 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   48% of Literary & Knowledge peers do this.

   Guide: Lazy Loading Without Broken Pages

What litgorod.ru already does well

Practices fewer than half of Literary & Knowledge peers use.

• Content Security Policy presentContent-Security-Policy present.18% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.22% of peers
• Modern image formats in useWebP or AVIF images detected.31% of peers

What we saw

Homepage checked

https://litgorod.ru/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

GlobalSign, 396-day validity, expiring 2026-11-08

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=reject

Homepage HTML

454 KB, gzip

Images on homepage

111 (jpg 52, png 26, gif 17, webp 10, svg 3)

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 Literary & Knowledge sites

• food.com68
• kadomi.xyz68
• komikbl.com68
• livelib.ru68
• manhwazone.com68

Literary & Knowledge readiness benchmark