knizhnik.org

Readiness by lane

Green: knizhnik.org. Thin bar: Literary & Knowledge peer median.

Priority fixes for knizhnik.org

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

1. Priority 1 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   69% of Literary & Knowledge peers do this. Limit: Only the standard location was requested, once, at the time of the check.

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

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.

   28% of Literary & Knowledge peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   Modern image formats in use

   Observed: The homepage had 62 images and none used WebP or AVIF.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   31% of Literary & Knowledge peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

4. Priority 4 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.knizhnik.org.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   22% of Literary & Knowledge peers do this.

   Guide: A Practical Website Health Check for Owners

What knizhnik.org already does well

Practices fewer than half of Literary & Knowledge peers use.

• No render-blocking scripts in <head>Head scripts load without blocking.48% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.49% of peers

What we saw

Homepage checked

https://knizhnik.org/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 174-day validity, expiring 2027-03-23

DNS operators

1 self-run or other nameserver domain

Homepage HTML

39 KB, gzip

Images on homepage

62 (jpg 53, svg 8)

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

• dexonline.ro47
• folkatlas.net47
• ixdzs.hk47
• litmir.club47
• loveread.ec47

Literary & Knowledge readiness benchmark