STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

gashapon.jp

gashapon.jp's public homepage, certificate and DNS checked against 31 practices and compared with 5,718 E-Commerce & Marketplaces sites.

Readiness index
43/100

E-Commerce & Marketplaces median 71

Ahead of
2.4%

of measured E-Commerce & Marketplaces sites

Practices observed
12/31

0 of 31 could not be measured

Popularity band
Top 10K

Chrome UX Report top-sites list

Measured 2026-10-23 12:18:32 UTC from one location. How we measure

Readiness by lane

Green: gashapon.jp. Thin bar: E-Commerce & Marketplaces peer median.

Enable

51/100

Peers 86

Harden

60/100

Peers 60

Accelerate

10/100

Peers 69

Recover

0/100

Peers 11

Priority fixes for gashapon.jp

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

  1. Priority 1 · Accelerate

    HTML compressed

    Observed: The homepage HTML (259 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.

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

  3. Priority 3 · Enable

    robots.txt published

    Observed: No robots.txt file was returned at the site root.

    What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

    95% of E-Commerce & Marketplaces peers do this.

  4. Priority 4 · Enable

    XML sitemap discoverable

    Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

    What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

    On WordPress: WordPress has generated a basic sitemap at /wp-sitemap.xml since 5.5; SEO plugins can replace it.

    87% of E-Commerce & Marketplaces peers do this.

What gashapon.jp already does well

Practices fewer than half of E-Commerce & Marketplaces peers use.

  • HSTS kept for at least a yearHSTS with a 365-day max-age.32% of peers

What we saw

Homepage checked
https://gashapon.jp/
Homepage response
HTTP 200
TLS
TLSv1.3, http/1.1
Certificate
GlobalSign, 199-day validity, expiring 2027-02-18
Platform or framework
WordPress
DNS operators
1 self-run or other nameserver domain
HSTS
max-age 365 days
Homepage HTML
259 KB, uncompressed
Images on homepage
222 (jpg 204, png 36, svg 5)

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 12

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Offscreen images lazy-loaded
  • Meta description written
  • Mobile viewport configured
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Own gashapon.jp?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

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

Compare with other E-Commerce & Marketplaces sites