STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

dcplan.co.jp

dcplan.co.jp's public homepage, certificate and DNS checked against 31 practices and compared with 203 Insurance & Financial Planning sites.

Readiness index
47/100

Insurance & Financial Planning median 69

Ahead of
9.4%

of measured Insurance & Financial Planning sites

Practices observed
12/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:53:36 UTC from one location. How we measure

Readiness by lane

Green: dcplan.co.jp. Thin bar: Insurance & Financial Planning peer median.

Enable

26/100

Peers 81

Harden

78/100

Peers 64

Accelerate

20/100

Peers 60

Recover

0/100

Peers 19

Priority fixes for dcplan.co.jp

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

  1. Priority 1 · Accelerate

    HTTP/2 negotiated

    Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

    Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

    What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

    80% of Insurance & Financial Planning peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

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

    86% of Insurance & Financial Planning peers do this.

  3. Priority 3 · 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.

    81% of Insurance & Financial Planning peers do this.

  4. Priority 4 · Accelerate

    Static files cached for 30 days or more

    Observed: A same-site stylesheet or script was cacheable for 7 days, 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.

    51% of Insurance & Financial Planning peers do this.

What dcplan.co.jp already does well

Practices fewer than half of Insurance & Financial Planning peers use.

  • Referrer-Policy setReferrer-Policy present.39% of peers

What we saw

Homepage checked
https://www.dcplan.co.jp/
Homepage response
HTTP 200
TLS
TLSv1.3, http/1.1
Certificate
Cybertrust Japan Co., Ltd., 189-day validity, expiring 2027-02-01
DNS operators
Akamai Edge DNS
HSTS
max-age 365 days, includeSubDomains, preload
DMARC policy
p=quarantine
Homepage HTML
43 KB, gzip
Images on homepage
26 (gif 14, png 10)

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

Observed 12

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Content Security Policy present
  • Referrer-Policy set
  • HTML compressed
  • Mobile viewport configured
  • At most one redirect to the homepage

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

Compare with other Insurance & Financial Planning sites