STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

robinhood.com

robinhood.com's public homepage, certificate and DNS checked against 31 practices and compared with 241 Stock & Crypto Trading sites.

Readiness index
82/100

Stock & Crypto Trading median 69

Ahead of
85%

of measured Stock & Crypto Trading sites

Practices observed
23/31

0 of 31 could not be measured

Popularity band
Top 10K

Chrome UX Report top-sites list

Measured 2026-10-23 11:40:14 UTC from one location. How we measure

Readiness by lane

Green: robinhood.com. Thin bar: Stock & Crypto Trading peer median.

Enable

87/100

Peers 82

Harden

91/100

Peers 61

Accelerate

65/100

Peers 67

Recover

0/100

Peers 6

Priority fixes for robinhood.com

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

  1. Priority 1 · Accelerate

    Modern image formats in use

    Observed: The homepage had 12 images and none used WebP or AVIF.

    Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.

    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.

    On Next.js: The next/image component serves optimized formats automatically.

    48% 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.

  2. Priority 2 · Accelerate

    Offscreen images lazy-loaded

    Observed: The homepage had 12 images and none used loading="lazy".

    What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

    63% of Stock & Crypto Trading peers do this.

  3. Priority 3 · Accelerate

    HTTP/3 advertised

    Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

    What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

    On Amazon CloudFront: Select HTTP/3 in the distribution's supported HTTP versions.

    36% of Stock & Crypto Trading peers do this.

  4. Priority 4 · Harden

    Certificate lifetime of 100 days or less

    Observed: The certificate from Amazon had a 394-day validity period, longer than the 100-day maximum that applies from March 2027.

    What to do: Move to automated issuance and renewal now, while you still have time to test it.

    60% of Stock & Crypto Trading peers do this.

What robinhood.com already does well

Practices fewer than half of Stock & Crypto Trading peers use.

  • security.txt publishedsecurity.txt with a contact found.9.1% of peers
  • CAA records limit who can issue certificatesCAA limits issuance to amazonaws.com, cloudflare.com, comodoca.com and others.15% of peers
  • Referrer-Policy setReferrer-Policy present.38% of peers

What we saw

Homepage checked
https://robinhood.com/
Homepage response
HTTP 200, after 1 redirect
TLS
TLSv1.3, HTTP/2
Certificate
Amazon, 394-day validity, expiring 2027-01-07
CDN or edge
Amazon CloudFront
Platform or framework
Next.js
DNS operators
Amazon Route 53
HSTS
max-age 365 days
DMARC policy
p=quarantine
Homepage HTML
261 KB, gzip
Images on homepage
12 (jpg 17, svg 10, png 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

Observed 23

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • CAA records limit who can issue certificates
  • security.txt published
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Content Security Policy present
  • Referrer-Policy set
  • HTTP/2 negotiated
  • HTML compressed
  • Static files cached for 30 days or more
  • No render-blocking scripts in <head>
  • robots.txt published
  • XML sitemap discoverable
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Own robinhood.com?

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: robinhood.com. This profile covers configuration only.

Compare with other Stock & Crypto Trading sites