Website readiness profile · Snapshot 23 October 2026
rakuten-sec.co.jp
rakuten-sec.co.jp's public homepage, certificate and DNS checked against 31 practices and compared with 241 Stock & Crypto Trading sites.
- Readiness index
- 65/100
- Ahead of
- 38%
- Practices observed
- 18/31
- Popularity band
- Top 5K
Stock & Crypto Trading median 69
of measured Stock & Crypto Trading sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: rakuten-sec.co.jp. Thin bar: Stock & Crypto Trading peer median.
Enable
69/100
Peers 82
Harden
65/100
Peers 61
Accelerate
60/100
Peers 67
Recover
100/100
Peers 6
Priority fixes for rakuten-sec.co.jp
Ordered by impact and by how common each practice is among peers.
Priority 1 · Enable
Mobile viewport configured
Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.
Why it matters: Without it, phones render the page at desktop width and shrink it, which makes text tiny and hard to use.
What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.
96% of Stock & Crypto Trading peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.
Priority 2 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 1 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.
55% of Stock & Crypto Trading peers do this.
Priority 3 · Accelerate
Modern image formats in use
Observed: The homepage had 98 images and none used WebP or AVIF.
What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.
48% of Stock & Crypto Trading peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
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.
60% of Stock & Crypto Trading peers do this.
What rakuten-sec.co.jp already does well
Practices fewer than half of Stock & Crypto Trading peers use.
- Nameservers spread across providersNameservers spread across more than one operator.6.2% of peers
- security.txt publishedsecurity.txt with a contact found.9.1% of peers
- HSTS kept for at least a yearHSTS with a 365-day max-age.44% of peers
What we saw
- Homepage checked
- https://www.rakuten-sec.co.jp/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- DigiCert, 198-day validity, expiring 2026-12-04
- DNS operators
- 3 self-run or other nameserver domains
- HSTS
- max-age 365 days
- DMARC policy
- p=reject
- Homepage HTML
- 314 KB, gzip
- Images on homepage
- 98 (png 89, svg 5, jpg 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
Not observed 13
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- Static files cached for 30 days or more
- Modern image formats in use
- Reachable over IPv6
- Mobile viewport configured
- Structured data present
Observed 18
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- security.txt published
- DMARC policy enforces quarantine or reject
- HTTP/2 negotiated
- HTML compressed
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Social preview image set
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Own rakuten-sec.co.jp?
Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.
Live status for this site: Status Is Down: rakuten-sec.co.jp. This profile covers configuration only.