Website readiness profile · Snapshot 23 October 2026
welt.de
welt.de's public homepage, certificate and DNS checked against 31 practices and compared with 3,856 News & Media sites.
- Readiness index
- 90/100
- Ahead of
- >99%
- Practices observed
- 28/31
- Popularity band
- Top 1K
News & Media median 68
of measured News & Media sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: welt.de. Thin bar: News & Media peer median.
Enable
100/100
Peers 89
Harden
94/100
Peers 56
Accelerate
75/100
Peers 68
Recover
100/100
Peers 11
Priority fixes for welt.de
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
Modern image formats in use
Observed: The homepage had 83 images and none used WebP or AVIF.
Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.
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.
44% 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: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 2 · 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.
36% of News & Media peers do this.
Priority 3 · Harden
CAA records limit who can issue certificates
Observed: No CAA record was found for welt.de, so any public certificate authority may issue for it.
What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.
13% of News & Media peers do this.
What welt.de already does well
Practices fewer than half of News & Media peers use.
- DNSSEC signedDNSSEC delegation (DS record) present.6.1% of peers
- security.txt publishedsecurity.txt with a contact found.6.2% of peers
- Nameservers spread across providersNameservers spread across more than one operator.11% of peers
What we saw
- Homepage checked
- https://www.welt.de/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Let's Encrypt, 89-day validity, expiring 2026-12-27
- DNS operators
- Akamai Edge DNS, plus 1 self-run or other nameserver domain
- HSTS
- max-age 365 days, includeSubDomains
- DMARC policy
- p=reject
- Homepage HTML
- 1,410 KB, gzip
- Images on homepage
- 83
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
Not observed 3
Observed 28
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/2 negotiated
- HTML compressed
- Static files cached for 30 days or more
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Own welt.de?
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: welt.de. This profile covers configuration only.