Website readiness profile · Snapshot 23 October 2026
kinokuniya.co.jp
kinokuniya.co.jp's public homepage, certificate and DNS checked against 31 practices and compared with 5,718 E-Commerce & Marketplaces sites.
- Readiness index
- 42/100
- Ahead of
- 2%
- Practices observed
- 12/31
- Popularity band
- Top 50K
E-Commerce & Marketplaces median 71
of measured E-Commerce & Marketplaces sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: kinokuniya.co.jp. Thin bar: E-Commerce & Marketplaces peer median.
Enable
87/100
Peers 86
Harden
38/100
Peers 60
Accelerate
0/100
Peers 69
Recover
100/100
Peers 11
Priority fixes for kinokuniya.co.jp
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTML compressed
Observed: The homepage HTML (106 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.
97% of E-Commerce & Marketplaces peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Guide: How to Set a Website Performance Budget That Teams Can Keep
Priority 2 · Accelerate
HTTP/2 negotiated
Observed: The TLS handshake selected http/1.1 instead of HTTP/2.
What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.
94% of E-Commerce & Marketplaces peers do this.
Priority 3 · 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.
On WordPress: Caching plugins or your host can set long browser cache lifetimes for theme and plugin assets.
60% of E-Commerce & Marketplaces peers do this.
Priority 4 · Accelerate
Modern image formats in use
Observed: The homepage had 49 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 WordPress: WordPress has supported WebP uploads since 5.8 and AVIF since 6.5; image plugins or the host can convert existing images.
47% of E-Commerce & Marketplaces peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
What kinokuniya.co.jp already does well
Practices fewer than half of E-Commerce & Marketplaces peers use.
- Nameservers spread across providersNameservers spread across more than one operator.11% of peers
What we saw
- Homepage checked
- https://www.kinokuniya.co.jp/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, http/1.1
- Certificate
- SSL Corporation, 197-day validity, expiring 2027-03-14
- Platform or framework
- WordPress
- DNS operators
- 2 self-run or other nameserver domains
- DMARC policy
- p=none
- Homepage HTML
- 106 KB, uncompressed
- Images on homepage
- 49 (jpg 39, png 9, gif 1)
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
Not observed 19
- HSTS kept for at least a year
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- Reachable over IPv6
- Structured data present
Observed 12
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Social preview image set
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Own kinokuniya.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: kinokuniya.co.jp. This profile covers configuration only.