STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

justwatch.com

justwatch.com's public homepage, certificate and DNS checked against 31 practices and compared with 536 Entertainment & Video Streaming sites.

Readiness index
72/100

Entertainment & Video Streaming median 62

Ahead of
80%

of measured Entertainment & Video Streaming sites

Practices observed
19/29

2 of 31 could not be measured

Popularity band
Top 5K

Chrome UX Report top-sites list

Measured 2026-10-23 11:26:54 UTC from one location. How we measure

Readiness by lane

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

Enable

71/100

Peers 80

Harden

51/100

Peers 52

Accelerate

100/100

Peers 60

Recover

100/100

Peers 12

Priority fixes for justwatch.com

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

  1. Priority 1 · Enable

    XML sitemap discoverable

    Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

    Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.

    What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

    71% of Entertainment & Video Streaming peers do this. Limit: Only the standard location was requested, once, at the time of the check.

  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.

    31% of Entertainment & Video Streaming peers do this.

  3. Priority 3 · Enable

    Structured data present

    Observed: The homepage had no JSON-LD structured data.

    What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.

    48% of Entertainment & Video Streaming peers do this.

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

What justwatch.com already does well

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

  • Nameservers spread across providersNameservers spread across Amazon Route 53 and Google Cloud DNS.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.justwatch.com/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Google Trust Services, 90-day validity, expiring 2027-01-09
CDN or edge
Google edge
Platform or framework
Nuxt
DNS operators
Amazon Route 53, Google Cloud DNS
DMARC policy
p=quarantine
Homepage HTML
1,437 KB, br
Images on homepage
455 (jpg 510, webp 119, avif 115, png 69, svg 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

Observed 19

  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • DMARC policy enforces quarantine or reject
  • Framing restricted
  • HTTP/2 negotiated
  • HTTP/3 advertised
  • HTML compressed
  • Static files cached for 30 days or more
  • Modern image formats in use
  • Offscreen images lazy-loaded
  • No render-blocking scripts in <head>
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage
  • Nameservers spread across providers

Not measured 2

  • HTTP requests move to HTTPS
  • robots.txt published

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

Compare with other Entertainment & Video Streaming sites