taz.de

Readiness by lane

Green: taz.de. Thin bar: News & Media peer median.

Priority fixes for taz.de

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.

   94% of News & Media 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 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 120 seconds, short of the 30-day benchmark.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   60% of News & Media peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 182 days, below the one-year benchmark.

   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.

   35% of News & Media peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 3 external scripts 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.

   42% of News & Media peers do this.

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

What taz.de already does well

Practices fewer than half of News & Media peers use.

• Nameservers spread across providersNameservers spread across more than one operator.11% of peers
• Content Security Policy presentContent-Security-Policy present.29% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.37% of peers

What we saw

Homepage checked

https://taz.de/

Homepage response

HTTP 200

TLS

TLSv1.3, http/1.1

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-18

DNS operators

3 self-run or other nameserver domains

HSTS

max-age 182 days

DMARC policy

p=reject

Homepage HTML

419 KB, gzip

Images on homepage

163 (webp 281, png 28, svg 4, jpg 1)

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 News & Media sites

• sciencepost.fr65
• setn.com65
• tagesspiegel.de65
• techpowerup.com65
• tejaratnews.com65

News & Media readiness benchmark