Website readiness profile · Snapshot 23 October 2026
starto.jp
starto.jp's public homepage, certificate and DNS checked against 31 practices and compared with 536 Entertainment & Video Streaming sites.
- Readiness index
- 45/100
- Ahead of
- 9%
- Practices observed
- 12/31
- Popularity band
- Top 50K
Entertainment & Video Streaming median 62
of measured Entertainment & Video Streaming sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: starto.jp. Thin bar: Entertainment & Video Streaming peer median.
Enable
74/100
Peers 80
Harden
38/100
Peers 52
Accelerate
28/100
Peers 60
Recover
0/100
Peers 12
Priority fixes for starto.jp
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTML compressed
Observed: The homepage HTML (157 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.
92% of Entertainment & Video Streaming 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
XML sitemap discoverable
Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.
What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.
71% of Entertainment & Video Streaming peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
Priority 3 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 0 seconds, 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.
46% of Entertainment & Video Streaming peers do this.
Priority 4 · 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.
On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.
31% of Entertainment & Video Streaming peers do this.
What starto.jp already does well
Practices fewer than half of Entertainment & Video Streaming peers use.
- HTTP/3 advertisedHTTP/3 advertised.34% of peers
What we saw
- Homepage checked
- https://starto.jp/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-03-23
- CDN or edge
- Amazon CloudFront
- DNS operators
- Amazon Route 53
- DMARC policy
- p=none
- Homepage HTML
- 157 KB, uncompressed
- Images on homepage
- 108 (jpg 63, svg 24, png 21)
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 19
- 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
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- XML sitemap discoverable
- Reachable over IPv6
- Structured data present
- Nameservers spread across providers
Observed 12
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- HTTP/2 negotiated
- HTTP/3 advertised
- robots.txt published
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own starto.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: starto.jp. This profile covers configuration only.