onetz.de

Readiness by lane

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

Priority fixes for onetz.de

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

1. Priority 1 · Enable

   Meta description written

   Observed: The homepage had no meta description.

   Why it matters: Search engines often use it for the snippet under your link, so a clear description can improve click-through.

   What to do: Write a short, specific description of the page for people, not a list of keywords.

   95% of News & Media peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: Meta Titles and Descriptions That Match Search Intent

2. Priority 2 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for onetz.de was p=none, which asks receivers to take no action on failing mail.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   37% of News & Media peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 2 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

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

   42% of News & Media peers do this.

   Guide: A Practical Website Health Check for Owners

What onetz.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
• HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.35% of peers
• X-Content-Type-Options: nosniffnosniff header present.42% of peers

What we saw

Homepage checked

https://www.onetz.de/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Sectigo, 198-day validity, expiring 2026-12-07

Platform or framework

Drupal

DNS operators

2 self-run or other nameserver domains

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=none

Homepage HTML

473 KB, gzip

Images on homepage

252 (webp 353, jpg 248, png 2)

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

• newsweek.pl69
• novilist.hr69
• nzz.ch69
• onlarissa.gr69
• orf.at69

News & Media readiness benchmark