dhc.co.jp

Readiness by lane

Green: dhc.co.jp. Thin bar: E-Commerce & Marketplaces peer median.

Priority fixes for dhc.co.jp

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

1. Priority 1 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 30 days, short of the 30-day benchmark.

   Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.

   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.

   On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.

   60% of E-Commerce & Marketplaces peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: Browser Caching Guide for Website Owners

2. Priority 2 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 1 days, below the one-year benchmark.

   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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   32% of E-Commerce & Marketplaces peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for dhc.co.jp was p=none, which asks receivers to take no action on failing mail.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   39% of E-Commerce & Marketplaces peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   44% of E-Commerce & Marketplaces peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

What dhc.co.jp already does well

Practices fewer than half of E-Commerce & Marketplaces peers use.

• Nameservers spread across providersNameservers spread across more than one operator.11% of peers
• Modern image formats in useWebP or AVIF images detected.47% of peers
• Content Security Policy presentContent-Security-Policy present.48% of peers

What we saw

Homepage checked

https://www.dhc.co.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 396-day validity, expiring 2027-01-18

CDN or edge

Cloudflare

DNS operators

2 self-run or other nameserver domains

HSTS

max-age 1 days, includeSubDomains, preload

DMARC policy

p=none

Homepage HTML

503 KB, gzip

Images on homepage

251 (webp 111, png 102, svg 39)

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

Compare with other E-Commerce & Marketplaces sites

• cottonon.com64
• cyamoda.com64
• daikinindia.com64
• doclasse.com64
• dospara.co.jp64

E-Commerce & Marketplaces readiness benchmark