deutsche-rentenversicherung.de

Readiness by lane

Green: deutsche-rentenversicherung.de. Thin bar: Government Services peer median.

Priority fixes for deutsche-rentenversicherung.de

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (195 KB) was delivered without gzip, Brotli or zstd compression.

   Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.

   What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.

   74% of Government Services peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: How to Set a Website Performance Budget That Teams Can Keep

2. Priority 2 · Accelerate

   HTTP/2 negotiated

   Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

   What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

   55% of Government Services peers do this.

   Guide: CDN Guide for Website Owners

3. Priority 3 · Harden

   HSTS kept for at least a year

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

   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.

   51% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 1 days, 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.

   30% of Government Services peers do this.

   Guide: Browser Caching Guide for Website Owners

What deutsche-rentenversicherung.de already does well

Practices fewer than half of Government Services peers use.

• security.txt publishedsecurity.txt with a contact found.8% of peers
• Modern image formats in useWebP or AVIF images detected.15% of peers
• Nameservers spread across providersNameservers spread across more than one operator.25% of peers

What we saw

Homepage checked

https://www.deutsche-rentenversicherung.de/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, http/1.1

Certificate

Deutsche Telekom Security GmbH, 369-day validity, expiring 2026-11-08

DNS operators

2 self-run or other nameserver domains

DMARC policy

p=reject

Homepage HTML

195 KB, uncompressed

Images on homepage

49 (jpg 33, svg 8, png 1, webp 1)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Government Services sites

• borger.dk63
• edudel.nic.in63
• minvu.gob.cl63
• toronto.ca64
• ur.gov.iq64

Government Services readiness benchmark