Website readiness profile · Snapshot 23 October 2026
telekom.de
telekom.de's public homepage, certificate and DNS checked against 31 practices and compared with 285 Telecommunications & Internet sites.
- Readiness index
- 79/100
- Ahead of
- 85%
- Practices observed
- 23/31
- Popularity band
- Top 10K
Telecommunications & Internet median 67
of measured Telecommunications & Internet sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: telekom.de. Thin bar: Telecommunications & Internet peer median.
Enable
92/100
Peers 82
Harden
82/100
Peers 61
Accelerate
63/100
Peers 57
Recover
100/100
Peers 16
Priority fixes for telekom.de
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 1 hours, short of the 30-day benchmark.
Why it matters: Returning visitors and later page views reuse cached files instead of downloading them again.
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.
41% of Telecommunications & Internet peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Priority 2 · Accelerate
No render-blocking scripts in <head>
Observed: The homepage <head> loaded 6 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.
37% of Telecommunications & Internet peers do this.
Guide: Control Third-Party Scripts Before They Control Your Page
Priority 3 · Enable
Social preview image set
Observed: The homepage had no og:image, so shared links may show without a preview image.
What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.
59% of Telecommunications & Internet peers do this.
Priority 4 · Harden
CAA records limit who can issue certificates
Observed: No CAA record was found for telekom.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.
15% of Telecommunications & Internet peers do this.
What telekom.de already does well
Practices fewer than half of Telecommunications & Internet peers use.
- security.txt publishedsecurity.txt with a contact found.13% of peers
- Nameservers spread across providersNameservers spread across more than one operator.16% of peers
- Reachable over IPv6IPv6 address published.33% of peers
What we saw
- Homepage checked
- https://www.telekom.de/
- Homepage response
- HTTP 200, after 1 redirect
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-04-07
- CDN or edge
- Amazon CloudFront
- DNS operators
- 3 self-run or other nameserver domains
- HSTS
- max-age 365 days, includeSubDomains
- DMARC policy
- p=quarantine
- Homepage HTML
- 270 KB, br
- Images on homepage
- 227 (svg 180, webp 64, jpg 7, png 6)
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 8
Observed 23
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- HTTP/2 negotiated
- HTML compressed
- Modern image formats in use
- Offscreen images lazy-loaded
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Own telekom.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: telekom.de. This profile covers configuration only.