saisoncard.co.jp

Readiness by lane

Green: saisoncard.co.jp. Thin bar: Banking & Finance peer median.

Priority fixes for saisoncard.co.jp

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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 Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

   62% of Banking & Finance peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Static files cached for 30 days or more

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

   43% of Banking & Finance peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 2 external scripts 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.

   36% of Banking & Finance peers do this.

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

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 Banking & Finance peers do this.

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

What saisoncard.co.jp already does well

Practices fewer than half of Banking & Finance peers use.

• HTTP/3 advertisedHTTP/3 advertised.22% of peers
• Modern image formats in useWebP or AVIF images detected.37% of peers
• Structured data presentJSON-LD structured data found.49% of peers

What we saw

Homepage checked

https://www.saisoncard.co.jp/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-03-13

CDN or edge

Amazon CloudFront

DNS operators

Amazon Route 53

DMARC policy

p=reject

Homepage HTML

304 KB, gzip

Images on homepage

194 (png 133, jpg 51, svg 24)

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 Banking & Finance sites

• absa.co.za68
• nab.com.au69
• ncsecu.org69
• produbanco.com.ec69
• trevts.com69

Banking & Finance readiness benchmark