disneyplus.com

Readiness by lane

Green: disneyplus.com. Thin bar: Entertainment & Video Streaming peer median.

Priority fixes for disneyplus.com

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

1. 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.

   89% of Entertainment & Video Streaming peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: CDN Guide for Website Owners

2. 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.

   On Next.js: Add the header in the headers() option of next.config.js for all routes.

   31% of Entertainment & Video Streaming peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · 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.

   On Next.js: Add it in next.config.js headers().

   43% of Entertainment & Video Streaming peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · 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.

   34% of Entertainment & Video Streaming peers do this.

   Guide: CDN Guide for Website Owners

What disneyplus.com already does well

Practices fewer than half of Entertainment & Video Streaming peers use.

• Nameservers spread across providersNameservers spread across NS1 and Vercara UltraDNS.12% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.31% of peers
• Modern image formats in useWebP or AVIF images detected.32% of peers

What we saw

Homepage checked

https://www.disneyplus.com/

Homepage response

HTTP 200

TLS

TLSv1.3, http/1.1

Certificate

COMODO CA Limited, 365-day validity, expiring 2026-11-14

Platform or framework

Next.js

DNS operators

NS1, Vercara UltraDNS

DMARC policy

p=quarantine

Homepage HTML

1,867 KB, gzip

Images on homepage

150

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 Entertainment & Video Streaming sites

• ateamas.com62
• bilibili.tv62
• digionline.ro62
• domashniy.ru62
• dramabox.com62

Entertainment & Video Streaming readiness benchmark