STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

kadokawa.co.jp

kadokawa.co.jp's public homepage, certificate and DNS checked against 31 practices and compared with 306 Online Publishing sites.

Readiness index
47/100

Online Publishing median 64

Ahead of
9.2%

of measured Online Publishing sites

Practices observed
13/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:43:08 UTC from one location. How we measure

Readiness by lane

Green: kadokawa.co.jp. Thin bar: Online Publishing peer median.

Enable

92/100

Peers 84

Harden

38/100

Peers 51

Accelerate

18/100

Peers 65

Recover

0/100

Peers 5

Priority fixes for kadokawa.co.jp

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

  1. Priority 1 · Accelerate

    HTML compressed

    Observed: The homepage HTML (169 KB) was delivered without gzip, Brotli or zstd compression.

    Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.

    What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.

    On Amazon CloudFront: Enable Compress objects automatically on the cache behaviour.

    94% of Online Publishing peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

  2. Priority 2 · 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.

    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.

    57% of Online Publishing peers do this.

  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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

    27% of Online Publishing peers do this.

  4. Priority 4 · Accelerate

    Modern image formats in use

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

    38% of Online Publishing peers do this.

What kadokawa.co.jp already does well

Practices fewer than half of Online Publishing peers use.

  • Reachable over IPv6IPv6 address published.48% of peers

What we saw

Homepage checked
https://www.kadokawa.co.jp/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Amazon, 197-day validity, expiring 2026-12-22
CDN or edge
Amazon CloudFront
DNS operators
Amazon Route 53
DMARC policy
p=none
Homepage HTML
169 KB, uncompressed
Images on homepage
78 (png 62, jpg 16)

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

Observed 13

  • HTTP requests move to HTTPS
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • HTTP/2 negotiated
  • robots.txt published
  • XML sitemap discoverable
  • Reachable over IPv6
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Own kadokawa.co.jp?

Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.

Live status for this site: Status Is Down: kadokawa.co.jp. This profile covers configuration only.

Compare with other Online Publishing sites