manga.in.ua

Readiness by lane

Green: manga.in.ua. Thin bar: Literary & Knowledge peer median.

Priority fixes for manga.in.ua

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

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   48% of Literary & Knowledge peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

3. Priority 3 · Accelerate

   Offscreen images lazy-loaded

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

4. Priority 4 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Cloudflare: Add the header with a response header transform rule.

   37% of Literary & Knowledge peers do this.

   Guide: A Practical Website Health Check for Owners

What manga.in.ua already does well

Practices fewer than half of Literary & Knowledge peers use.

• CAA records limit who can issue certificatesCAA limits issuance to comodoca.com, digicert.com, letsencrypt.org and others.13% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.22% of peers
• HSTS kept for at least a yearHSTS with a 365-day max-age.28% of peers

What we saw

Homepage checked

https://manga.in.ua/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2027-01-20

CDN or edge

Cloudflare

DNS operators

Cloudflare

HSTS

max-age 365 days

DMARC policy

p=quarantine

Homepage HTML

211 KB, br

Images on homepage

62 (png 31, jpg 25, webp 6)

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

• elsevier.com71
• komikindo.ch71
• lectorxd.com71
• mangadistrict.com71
• mvlempyr.io71

Literary & Knowledge readiness benchmark