Website readiness profile · Snapshot 23 October 2026
dream-novel.jp
dream-novel.jp's public homepage, certificate and DNS checked against 31 practices and compared with 306 Online Publishing sites.
- Readiness index
- 28/100
- Ahead of
- 0%
- Practices observed
- 8/30
- Popularity band
- Top 50K
Online Publishing median 64
of measured Online Publishing sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: dream-novel.jp. Thin bar: Online Publishing peer median.
Enable
33/100
Peers 84
Harden
18/100
Peers 51
Accelerate
42/100
Peers 65
Recover
0/100
Peers 5
Priority fixes for dream-novel.jp
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HTTP requests move to HTTPS
Observed: A request to http://dream-novel.jp/ was not redirected to HTTPS.
Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.
What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.
93% of Online Publishing peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.
Priority 2 · Enable
Mobile viewport configured
Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.
What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.
96% of Online Publishing peers do this.
Priority 3 · 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.
89% of Online Publishing peers do this.
Priority 4 · 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.
91% of Online Publishing peers do this.
Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes
What we saw
- Homepage checked
- https://dream-novel.jp/
- Homepage response
- HTTP 200
- TLS
- TLSv1.2, HTTP/2
- Certificate
- Let's Encrypt, 89-day validity, expiring 2026-12-16
- DNS operators
- 1 self-run or other nameserver domain
- Homepage HTML
- 6 KB, gzip
- Images on homepage
- 3 (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 22
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- 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
- Static files cached for 30 days or more
- Modern image formats in use
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Mobile viewport configured
- Structured data present
- Nameservers spread across providers
Observed 8
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- HTTP/2 negotiated
- HTML compressed
- Meta description written
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Not measured 1
- Offscreen images lazy-loaded
Own dream-novel.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: dream-novel.jp. This profile covers configuration only.