Website readiness profile · Snapshot 23 October 2026
consorsbank.de
consorsbank.de's public homepage, certificate and DNS checked against 31 practices and compared with 549 Banking & Finance sites.
- Readiness index
- 73/100
- Ahead of
- 70%
- Practices observed
- 20/31
- Popularity band
- Top 50K
Banking & Finance median 66
of measured Banking & Finance sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: consorsbank.de. Thin bar: Banking & Finance peer median.
Enable
69/100
Peers 78
Harden
75/100
Peers 64
Accelerate
73/100
Peers 55
Recover
100/100
Peers 21
Priority fixes for consorsbank.de
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTTP/2 negotiated
Observed: The TLS handshake selected http/1.1 instead of HTTP/2.
Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.
What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.
73% of Banking & Finance peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · 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.
72% of Banking & Finance peers do this.
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 Banking & Finance peers do this.
Priority 4 · Enable
Structured data present
Observed: The homepage had no JSON-LD structured data.
What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.
49% of Banking & Finance peers do this.
What consorsbank.de already does well
Practices fewer than half of Banking & Finance peers use.
- Nameservers spread across providersNameservers spread across more than one operator.21% of peers
- No render-blocking scripts in <head>Head scripts load without blocking.36% of peers
- Modern image formats in useWebP or AVIF images detected.37% of peers
What we saw
- Homepage checked
- https://www.consorsbank.de/
- Homepage response
- HTTP 200, after 1 redirect
- TLS
- TLSv1.3, http/1.1
- Certificate
- DigiCert, 198-day validity, expiring 2027-01-06
- Platform or framework
- Adobe Experience Manager
- DNS operators
- 3 self-run or other nameserver domains
- HSTS
- max-age 730 days, includeSubDomains
- DMARC policy
- p=reject
- Homepage HTML
- 49 KB, gzip
- Images on homepage
- 22 (jpg 63, webp 56, svg 4)
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 11
Observed 20
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Meta description written
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Own consorsbank.de?
Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.
Live status for this site: Status Is Down: consorsbank.de. This profile covers configuration only.