Website readiness profile · Snapshot 23 October 2026
dragons.jp
dragons.jp's public homepage, certificate and DNS checked against 31 practices and compared with 677 Sports Broadcast & Fantasy Games sites.
- Readiness index
- 22/100
- Ahead of
- <1%
- Practices observed
- 6/31
- Popularity band
- Top 50K
Sports Broadcast & Fantasy Games median 64
of measured Sports Broadcast & Fantasy Games sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: dragons.jp. Thin bar: Sports Broadcast & Fantasy Games peer median.
Enable
33/100
Peers 82
Harden
29/100
Peers 51
Accelerate
0/100
Peers 63
Recover
0/100
Peers 16
Priority fixes for dragons.jp
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTML compressed
Observed: The homepage HTML (79 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.
95% of Sports Broadcast & Fantasy Games 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
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 Sports Broadcast & Fantasy Games peers do this.
Priority 3 · 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.
91% of Sports Broadcast & Fantasy Games peers do this.
Priority 4 · 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.
90% of Sports Broadcast & Fantasy Games peers do this.
What we saw
- Homepage checked
- https://dragons.jp/
- Homepage response
- HTTP 200
- TLS
- TLSv1.2
- Certificate
- Amazon, 197-day validity, expiring 2027-03-25
- DNS operators
- Amazon Route 53
- DMARC policy
- p=none
- Homepage HTML
- 79 KB, uncompressed
- Images on homepage
- 118 (jpg 86, svg 16, png 1, 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 25
- HSTS kept for at least a year
- TLS 1.3 negotiated
- 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/2 negotiated
- HTTP/3 advertised
- 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>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Mobile viewport configured
- Structured data present
- Nameservers spread across providers
Observed 6
- HTTP requests move to HTTPS
- Certificate has more than 14 days left
- Meta description written
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own dragons.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: dragons.jp. This profile covers configuration only.