Website readiness profile · Snapshot 23 October 2026
pokemon.co.jp
pokemon.co.jp's public homepage, certificate and DNS checked against 31 practices and compared with 485 Gaming Platforms & Consoles sites.
- Readiness index
- 59/100
- Ahead of
- 39%
- Practices observed
- 15/29
- Popularity band
- Top 50K
Gaming Platforms & Consoles median 62
of measured Gaming Platforms & Consoles sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: pokemon.co.jp. Thin bar: Gaming Platforms & Consoles peer median.
Enable
77/100
Peers 76
Harden
56/100
Peers 53
Accelerate
47/100
Peers 63
Recover
0/100
Peers 6
Priority fixes for pokemon.co.jp
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTML compressed
Observed: The homepage HTML (35 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.
93% of Gaming Platforms & Consoles 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
Modern image formats in use
Observed: The homepage had 32 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.
43% of Gaming Platforms & Consoles peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 3 · Enable
Canonical URL declared
Observed: The homepage did not declare a canonical URL.
What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.
59% of Gaming Platforms & Consoles peers do this.
Priority 4 · Harden
Certificate lifetime of 100 days or less
Observed: The certificate from Amazon had a 197-day validity period, longer than the 100-day maximum that applies from March 2027.
What to do: Move to automated issuance and renewal now, while you still have time to test it.
76% of Gaming Platforms & Consoles peers do this.
What pokemon.co.jp already does well
Practices fewer than half of Gaming Platforms & Consoles peers use.
- DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.26% of peers
- HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.30% of peers
- X-Content-Type-Options: nosniffnosniff header present.38% of peers
What we saw
- Homepage checked
- https://www.pokemon.co.jp/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2026-12-26
- CDN or edge
- Amazon CloudFront
- DNS operators
- Amazon Route 53
- HSTS
- max-age 365 days, includeSubDomains, preload
- DMARC policy
- p=quarantine
- Homepage HTML
- 35 KB, uncompressed
- Images on homepage
- 32 (gif 16, svg 10, png 3)
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 14
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- HTML compressed
- Modern image formats in use
- Reachable over IPv6
- Canonical URL declared
- Structured data present
- Nameservers spread across providers
Observed 15
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- HTTP/2 negotiated
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Meta description written
- Mobile viewport configured
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Not measured 2
- HTTP requests move to HTTPS
- Static files cached for 30 days or more
Own pokemon.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: pokemon.co.jp. This profile covers configuration only.