Website readiness profile · Snapshot 23 October 2026
musasi.jp
musasi.jp's public homepage, certificate and DNS checked against 31 practices and compared with 231 Programming & Software sites.
- Readiness index
- 36/100
- Ahead of
- 1.7%
- Practices observed
- 8/29
- Popularity band
- Top 5K
Programming & Software median 68
of measured Programming & Software sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: musasi.jp. Thin bar: Programming & Software peer median.
Enable
68/100
Peers 81
Harden
29/100
Peers 59
Accelerate
21/100
Peers 65
Recover
0/100
Peers 7
Priority fixes for musasi.jp
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTML compressed
Observed: The homepage HTML (36 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.
94% of Programming & Software 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 · Harden
TLS 1.3 negotiated
Observed: The TLS connection negotiated TLSv1.2.
What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.
93% of Programming & Software peers do this.
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.
40% of Programming & Software peers do this.
Priority 4 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for musasi.jp was p=none, which asks receivers to take no action on failing mail.
What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.
45% of Programming & Software peers do this.
What we saw
- Homepage checked
- https://www.musasi.jp/
- Homepage response
- HTTP 200, after 1 redirect
- TLS
- TLSv1.2, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-04-02
- Platform or framework
- WordPress
- DNS operators
- Amazon Route 53
- DMARC policy
- p=none
- Homepage HTML
- 36 KB, uncompressed
- Images on homepage
- 27 (jpg 25, 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 21
- HSTS kept for at least a year
- TLS 1.3 negotiated
- 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/3 advertised
- HTML compressed
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- Reachable over IPv6
- Structured data present
- Social preview image set
- Page language declared
- Nameservers spread across providers
Observed 8
- HTTP requests move to HTTPS
- Certificate has more than 14 days left
- HTTP/2 negotiated
- robots.txt published
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- At most one redirect to the homepage
Not measured 2
- Static files cached for 30 days or more
- XML sitemap discoverable
Own musasi.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: musasi.jp. This profile covers configuration only.