Website readiness profile · Snapshot 23 October 2026
roku.com
roku.com's public homepage, certificate and DNS checked against 31 practices and compared with 536 Entertainment & Video Streaming sites.
- Readiness index
- 81/100
- Ahead of
- 96%
- Practices observed
- 22/29
- Popularity band
- Top 50K
Entertainment & Video Streaming median 62
of measured Entertainment & Video Streaming sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: roku.com. Thin bar: Entertainment & Video Streaming peer median.
Enable
100/100
Peers 80
Harden
69/100
Peers 52
Accelerate
87/100
Peers 60
Recover
0/100
Peers 12
Priority fixes for roku.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HSTS kept for at least a year
Observed: Strict-Transport-Security was sent with a max-age of 180 days, below the one-year benchmark.
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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.
31% of Entertainment & Video Streaming peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · 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 Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.
34% of Entertainment & Video Streaming peers do this.
Priority 3 · 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.
18% of Entertainment & Video Streaming peers do this.
Guide: Payment Security and PCI DSS: What Website Owners Need to Know
Priority 4 · Harden
CAA records limit who can issue certificates
Observed: No CAA record was found for roku.com, so any public certificate authority may issue for it.
What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.
On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.
9.5% of Entertainment & Video Streaming peers do this.
What roku.com already does well
Practices fewer than half of Entertainment & Video Streaming peers use.
- security.txt publishedsecurity.txt with a contact found.5.6% of peers
- DMARC policy enforces quarantine or rejectDMARC policy p=reject.31% of peers
- X-Content-Type-Options: nosniffnosniff header present.40% of peers
What we saw
- Homepage checked
- https://www.roku.com/
- Homepage response
- HTTP 200, after 1 redirect
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Google Trust Services, 90-day validity, expiring 2027-01-11
- CDN or edge
- Cloudflare
- DNS operators
- Amazon Route 53
- HSTS
- max-age 180 days
- DMARC policy
- p=reject
- Homepage HTML
- 58 KB, br
- Images on homepage
- 0
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 7
Observed 22
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- 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
- Reachable over IPv6
- 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
Not measured 2
- Modern image formats in use
- Offscreen images lazy-loaded
Own roku.com?
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: roku.com. This profile covers configuration only.