zdf.de

Readiness by lane

Green: zdf.de. Thin bar: Entertainment & Video Streaming peer median.

Priority fixes for zdf.de

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   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 Next.js: Add the header in the headers() option of next.config.js for all routes.

   31% of Entertainment & Video Streaming peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Modern image formats in use

   Observed: The homepage had 64 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.

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

   32% of Entertainment & Video Streaming peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   42% of Entertainment & Video Streaming peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

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 zdf.de 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
• Nameservers spread across providersNameservers spread across more than one operator.12% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.31% of peers

What we saw

Homepage checked

https://www.zdf.de/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-02-07

Platform or framework

Next.js

DNS operators

Akamai Edge DNS, plus 1 self-run or other nameserver domain

DMARC policy

p=reject

Homepage HTML

600 KB, gzip

Images on homepage

64 (jpg 19)

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

• alphatv.gr71
• catchplay.com71
• sky.it72
• thezeusnetwork.com72
• viorawatch.com72

Entertainment & Video Streaming readiness benchmark