umamusu.wiki

Readiness by lane

Green: umamusu.wiki. Thin bar: Literary & Knowledge peer median.

Priority fixes for umamusu.wiki

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 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 300 seconds, 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.

   On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.

   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.

   On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   28% of Literary & Knowledge peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Accelerate

   Modern image formats in use

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

   On Cloudflare: Cloudflare Polish can convert images to WebP.

   31% of Literary & Knowledge peers do this.

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

What umamusu.wiki already does well

Practices fewer than half of Literary & Knowledge peers use.

• security.txt publishedsecurity.txt with a contact found.5% of peers
• X-Content-Type-Options: nosniffnosniff header present.38% of peers
• Structured data presentJSON-LD structured data found.46% of peers

What we saw

Homepage checked

https://umamusu.wiki/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-12-11

CDN or edge

Cloudflare

DNS operators

Cloudflare

DMARC policy

p=none

Homepage HTML

56 KB, br

Images on homepage

58 (png 2, svg 2)

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

• borntobenovel.com63
• poedb.tw64
• rutoki.com64
• tamilnovelwriters.com64
• wyrazy.pl64

Literary & Knowledge readiness benchmark