nissay.co.jp

Readiness by lane

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

Priority fixes for nissay.co.jp

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

1. Priority 1 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.

   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. Limit: Only the standard location was requested, once, at the time of the check.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

2. Priority 2 · Accelerate

   Static files cached for 30 days or more

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

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

   51% of Insurance & Financial Planning peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Cloudflare: Add the header with a response header transform rule.

   69% of Insurance & Financial Planning peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   51% of Insurance & Financial Planning peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What nissay.co.jp already does well

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

• Modern image formats in useWebP or AVIF images detected.43% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.43% of peers

What we saw

Homepage checked

https://www.nissay.co.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Cybertrust Japan Co., Ltd., 144-day validity, expiring 2027-01-01

CDN or edge

Cloudflare

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days

DMARC policy

p=quarantine

Homepage HTML

31 KB, gzip

Images on homepage

35 (webp 16, jpg 11, svg 4, png 4)

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 Insurance & Financial Planning sites

• aetna.com66
• financemasterpro.com66
• pacifico.com.pe66
• sura.co67
• unisalute.it66

Insurance & Financial Planning readiness benchmark