Website readiness profile · Snapshot 23 October 2026
nomura.co.jp
nomura.co.jp's public homepage, certificate and DNS checked against 31 practices and compared with 549 Banking & Finance sites.
- Readiness index
- 60/100
- Ahead of
- 30%
- Practices observed
- 17/31
- Popularity band
- Top 50K
Banking & Finance median 66
of measured Banking & Finance sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: nomura.co.jp. Thin bar: Banking & Finance peer median.
Enable
95/100
Peers 78
Harden
48/100
Peers 64
Accelerate
45/100
Peers 55
Recover
100/100
Peers 21
Priority fixes for nomura.co.jp
Ordered by impact and by how common each practice is among peers.
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.
73% of Banking & Finance peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · Harden
HSTS kept for at least a year
Observed: The homepage response did not include a Strict-Transport-Security header.
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.
62% of Banking & Finance peers do this.
Priority 3 · 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.
43% of Banking & Finance peers do this.
Priority 4 · 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.
69% of Banking & Finance peers do this.
What nomura.co.jp already does well
Practices fewer than half of Banking & Finance peers use.
- Nameservers spread across providersNameservers spread across more than one operator.21% 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.nomura.co.jp/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, http/1.1
- Certificate
- DigiCert, 198-day validity, expiring 2027-02-04
- CDN or edge
- Akamai
- DNS operators
- Akamai Edge DNS, plus 1 self-run or other nameserver domain
- DMARC policy
- p=reject
- Homepage HTML
- 65 KB, gzip
- Images on homepage
- 21 (webp 17, png 15, svg 5, jpg 3)
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
Not observed 14
- HSTS kept for at least a year
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/2 negotiated
- HTTP/3 advertised
- Static files cached for 30 days or more
- No render-blocking scripts in <head>
- Reachable over IPv6
Observed 17
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- DMARC policy enforces quarantine or reject
- HTML compressed
- Modern image formats in use
- Offscreen images lazy-loaded
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Own nomura.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: nomura.co.jp. This profile covers configuration only.