rutoki.com

Readiness by lane

Green: rutoki.com. Thin bar: Literary & Knowledge peer median.

Priority fixes for rutoki.com

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

1. Priority 1 · Accelerate

   Static files cached for 30 days or more

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

   Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

   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. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: Browser Caching Guide for Website Owners

2. Priority 2 · Accelerate

   Modern image formats in use

   Observed: The homepage had 650 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

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.rutoki.com.

   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

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.

   47% of Literary & Knowledge peers do this.

   Guide: CDN Guide for Website Owners

What rutoki.com already does well

Practices fewer than half of Literary & Knowledge peers use.

• CAA records limit who can issue certificatesCAA limits issuance to globalsign.com, letsencrypt.org.13% of peers
• HSTS kept for at least a yearHSTS with a 730-day max-age covering subdomains.28% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.48% of peers

What we saw

Homepage checked

https://rutoki.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 730 days, includeSubDomains, preload

Homepage HTML

643 KB, gzip

Images on homepage

650 (jpg 565, svg 75)

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

• mangaplaza.com64
• mindafansub.dev64
• poedb.tw64
• tamilnovelwriters.com64
• umamusu.wiki64

Literary & Knowledge readiness benchmark