Website readiness profile · Snapshot 23 October 2026
earth.jp
earth.jp's public homepage, certificate and DNS checked against 31 practices and compared with 87 Smart Home & Lifestyle sites.
- Readiness index
- 42/100
- Ahead of
- 6.9%
- Practices observed
- 11/31
- Popularity band
- Top 50K
Smart Home & Lifestyle median 71
of measured Smart Home & Lifestyle sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: earth.jp. Thin bar: Smart Home & Lifestyle peer median.
Enable
64/100
Peers 86
Harden
38/100
Peers 60
Accelerate
30/100
Peers 63
Recover
0/100
Peers 10
Priority fixes for earth.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.
88% of Smart Home & Lifestyle 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 · 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.
89% of Smart Home & Lifestyle peers do this.
Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes
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.
43% of Smart Home & Lifestyle peers do this.
Priority 4 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for earth.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.
52% of Smart Home & Lifestyle peers do this.
What earth.jp already does well
Practices fewer than half of Smart Home & Lifestyle peers use.
- No render-blocking scripts in <head>Head scripts load without blocking.37% of peers
What we saw
- Homepage checked
- https://www.earth.jp/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- GlobalSign, 199-day validity, expiring 2027-01-23
- DNS operators
- 1 self-run or other nameserver domain
- DMARC policy
- p=none
- Homepage HTML
- 36 KB, uncompressed
- Images on homepage
- 39 (jpg 20, svg 14, png 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
Not observed 20
- 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
- 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
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- robots.txt published
- Reachable over IPv6
- Canonical URL declared
- Structured data present
- Nameservers spread across providers
Observed 11
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- HTTP/2 negotiated
- No render-blocking scripts in <head>
- XML sitemap discoverable
- Meta description written
- Mobile viewport configured
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own earth.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: earth.jp. This profile covers configuration only.