bundestag.de

Readiness by lane

Green: bundestag.de. Thin bar: Government Services peer median.

Priority fixes for bundestag.de

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

1. Priority 1 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 2 external scripts without async or defer.

   Why it matters: A plain <script src> in the head stops the browser from showing anything until that file has downloaded and run.

   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.

   39% of Government Services peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

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

2. Priority 2 · Accelerate

   Modern image formats in use

   Observed: The homepage had 13 images and none used WebP or AVIF.

   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.

   15% of Government Services peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

3. Priority 3 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   41% of Government Services peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

4. Priority 4 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 13 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   36% of Government Services peers do this.

   Guide: Lazy Loading Without Broken Pages

What bundestag.de already does well

Practices fewer than half of Government Services peers use.

• security.txt publishedsecurity.txt with a contact found.8% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.30% of peers
• Certificate lifetime of 100 days or lessShort-lived 89-day certificate from Let's Encrypt, already inside the 2027 limit.34% of peers

What we saw

Homepage checked

https://www.bundestag.de/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days

DMARC policy

p=reject

Homepage HTML

332 KB, gzip

Images on homepage

13 (svg 12)

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 Government Services sites

• gov-online.go.jp73
• migrationsverket.se73
• pa.gov74
• pensionsmyndigheten.se74
• sec.gov74

Government Services readiness benchmark