STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

doraken.jp

doraken.jp's public homepage, certificate and DNS checked against 31 practices and compared with 485 Gaming Platforms & Consoles sites.

Readiness index
29/100

Gaming Platforms & Consoles median 62

Ahead of
<1%

of measured Gaming Platforms & Consoles sites

Practices observed
7/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 12:19:44 UTC from one location. How we measure

Readiness by lane

Green: doraken.jp. Thin bar: Gaming Platforms & Consoles peer median.

Enable

31/100

Peers 76

Harden

38/100

Peers 53

Accelerate

13/100

Peers 63

Recover

0/100

Peers 6

Priority fixes for doraken.jp

Ordered by impact and by how common each practice is among peers.

  1. Priority 1 · Accelerate

    HTML compressed

    Observed: The homepage HTML (27 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.

    93% of Gaming Platforms & Consoles peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

  2. 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.

    93% of Gaming Platforms & Consoles peers do this.

  3. 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 Gaming Platforms & Consoles peers do this.

  4. 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 Gaming Platforms & Consoles peers do this.

What doraken.jp already does well

Practices fewer than half of Gaming Platforms & Consoles peers use.

  • DMARC policy enforces quarantine or rejectDMARC policy p=reject.26% of peers
  • No render-blocking scripts in <head>Head scripts load without blocking.49% of peers

What we saw

Homepage checked
https://doraken.jp/
Homepage response
HTTP 200
TLS
TLSv1.2
Certificate
DigiCert, 198-day validity, expiring 2027-05-04
DNS operators
1 self-run or other nameserver domain
DMARC policy
p=reject
Homepage HTML
27 KB, uncompressed
Images on homepage
35 (png 18, gif 17)

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

Own doraken.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: doraken.jp. This profile covers configuration only.

Compare with other Gaming Platforms & Consoles sites