Website readiness profile · Snapshot 23 October 2026
haspa.de
haspa.de's public homepage, certificate and DNS checked against 31 practices and compared with 549 Banking & Finance sites.
- Readiness index
- 63/100
- Ahead of
- 38%
- Practices observed
- 18/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: haspa.de. Thin bar: Banking & Finance peer median.
Enable
79/100
Peers 78
Harden
69/100
Peers 64
Accelerate
35/100
Peers 55
Recover
100/100
Peers 21
Priority fixes for haspa.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 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for haspa.de was p=none, which asks receivers to take no action on failing mail.
What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.
70% of Banking & Finance peers do this.
Priority 3 · Accelerate
Modern image formats in use
Observed: The homepage had 22 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.
37% of Banking & Finance peers do this.
Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format
Priority 4 · Accelerate
No render-blocking scripts in <head>
Observed: The homepage <head> loaded 2 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.
36% of Banking & Finance peers do this.
Guide: Control Third-Party Scripts Before They Control Your Page
What haspa.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
- Referrer-Policy setReferrer-Policy present.36% of peers
- Static files cached for 30 days or moreLong-lived caching on static files.43% of peers
What we saw
- Homepage checked
- https://www.haspa.de/
- Homepage response
- HTTP 200, after 1 redirect
- TLS
- TLSv1.3
- Certificate
- DigiCert, 323-day validity, expiring 2026-12-01
- Platform or framework
- Adobe Experience Manager
- DNS operators
- 2 self-run or other nameserver domains
- HSTS
- max-age 365 days
- DMARC policy
- p=none
- Homepage HTML
- 131 KB, gzip
- Images on homepage
- 22 (jpg 10, svg 6, png 5)
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 13
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- HTTP/2 negotiated
- HTTP/3 advertised
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- Reachable over IPv6
- Structured data present
- Social preview image set
Observed 18
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTML compressed
- Static files cached for 30 days or more
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Own haspa.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: haspa.de. This profile covers configuration only.