Website readiness profile · Snapshot 23 October 2026
hamusoku.com
hamusoku.com's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.
- Readiness index
- 37/100
- Ahead of
- <1%
- Practices observed
- 10/31
- Popularity band
- Top 10K
News & Media median 68
of measured News & Media sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: hamusoku.com. Thin bar: News & Media peer median.
Enable
46/100
Peers 89
Harden
43/100
Peers 56
Accelerate
20/100
Peers 68
Recover
0/100
Peers 11
Priority fixes for hamusoku.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Enable
Mobile viewport configured
Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.
Why it matters: Without it, phones render the page at desktop width and shrink it, which makes text tiny and hard to use.
What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.
98% of News & Media peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.
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 News & Media peers do this.
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.
98% of News & Media peers do this.
Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes
Priority 4 · 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.
60% of News & Media peers do this.
What we saw
- Homepage checked
- https://hamusoku.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, http/1.1
- Certificate
- Let's Encrypt, 89-day validity, expiring 2026-12-30
- DNS operators
- 1 self-run or other nameserver domain
- Homepage HTML
- 101 KB, gzip
- Images on homepage
- 64 (jpg 63, 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 21
- HSTS kept for at least a year
- 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
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- Reachable over IPv6
- Canonical URL declared
- Mobile viewport configured
- Structured data present
- Nameservers spread across providers
Observed 10
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- HTML compressed
- XML sitemap discoverable
- Meta description written
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own hamusoku.com?
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: hamusoku.com. This profile covers configuration only.