Website readiness profile · Snapshot 23 October 2026
yomuno.jp
yomuno.jp's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.
- Readiness index
- 68/100
- Ahead of
- 49%
- Practices observed
- 19/31
- Popularity band
- Top 50K
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: yomuno.jp. Thin bar: News & Media peer median.
Enable
87/100
Peers 89
Harden
58/100
Peers 56
Accelerate
68/100
Peers 68
Recover
0/100
Peers 11
Priority fixes for yomuno.jp
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTML compressed
Observed: The homepage HTML (182 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.
97% of News & Media 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
HSTS kept for at least a year
Observed: Strict-Transport-Security was sent with a max-age of 0 days, below the one-year benchmark.
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.
On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.
35% of News & Media peers do this.
Priority 3 · Accelerate
No render-blocking scripts in <head>
Observed: The homepage <head> loaded 2 external scripts without async or defer.
What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.
42% of News & Media peers do this.
Guide: Control Third-Party Scripts Before They Control Your Page
Priority 4 · Enable
Page language declared
Observed: The homepage <html> element had no lang attribute.
What to do: Set lang on the html element (for example lang="en") and on any sections in another language.
97% of News & Media peers do this.
What yomuno.jp already does well
Practices fewer than half of News & Media peers use.
- HTTP/3 advertisedHTTP/3 advertised.36% of peers
- DMARC policy enforces quarantine or rejectDMARC policy p=reject.37% of peers
- X-Content-Type-Options: nosniffnosniff header present.42% of peers
What we saw
- Homepage checked
- https://yomuno.jp/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 394-day validity, expiring 2026-12-22
- CDN or edge
- Amazon CloudFront
- DNS operators
- Amazon Route 53
- HSTS
- max-age 0 days
- DMARC policy
- p=reject
- Homepage HTML
- 182 KB, uncompressed
- Images on homepage
- 83 (jpg 64, png 15, svg 2, webp 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 12
- 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
- Content Security Policy present
- Referrer-Policy set
- HTML compressed
- No render-blocking scripts in <head>
- Reachable over IPv6
- Page language declared
- Nameservers spread across providers
Observed 19
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- HTTP/2 negotiated
- HTTP/3 advertised
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Social preview image set
- At most one redirect to the homepage
Own yomuno.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: yomuno.jp. This profile covers configuration only.