https://bundesgesundheitsministerium.de Export & share

DE · EUR (€) · Estimated Applicable regulations: DSGVO · ePrivacy Directive · EAA Dev cost: €90/hr How jurisdiction is detected

Scanned

2026-04-22 21:39 UTC

Worker

🇪🇸 Madrid

Duration

51.00s

Vs prev

—

Audit overview

Accessibility needs attention; the rest of the categories are in good shape.

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Screenshots

DESKTOP + MOBILE

Desktop

Mobile

Top Priorities (5)

Sorted by impact

Content-Security-Policy header is missing

Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.

Security › Security Headers

No Content-Security-Policy header found

Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.

Security › Content Security Policy

1 button(s) with no accessible text

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Accessibility › Link & Button Quality

31 third-party resources (100% of weight)

Informational: third-party resource count and their share of page weight. High share caps perf gains from frontend optimization.

Performance › Page Weight Inventory

Cross-Origin-Embedder-Policy header is missing

COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.

Security › Security Headers

What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 3.3s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.

1 accessibility issue excludes users who rely on assistive technology.

Your LCP is 3.3s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Business case

What fixing the audit's findings is worth -- and what ignoring them keeps costing.

Return on investment

€675 investment → €5,707/month returns + EUR 120,500,000 risk avoided

Investment

€675

7.5 h · 4 findings

Monthly returns

€5.707

€68.489/yr

Payback

0.1 mo

+10047% Y1

Regulatory risk avoided EUR 120.500.000

Or — fix only the top 3 findings

€585 → 0.1 mo payback · +11608% Y1

Optimistic scenario assuming the top 3 capture most of the upside. Real-world recovery typically falls between this projection and the full-fix ROI above.

€45 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Conversion barriers

7 barrier(s) likely increasing bounce by ~20%.

Barriers

7 warn

Bounce delta

+20pp

added vs baseline

Score

Speed

Trust

Usability

Content

Nav

Page loads in 3.3s
Every additional 100ms above 2.5s costs conversions — you're 848ms over
→ Target <2.5s LCP: defer non-critical scripts and optimize the hero image
High main-thread blocking time
Page is non-interactive for 355ms after first paint
→ Defer third-party scripts and split large bundles
No HSTS header
Returning visitors are briefly exposed to downgrade attacks on first request
→ Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
Higher XSS blast radius — one compromised script can exfiltrate the checkout form
→ Ship a reporting-only CSP first, then enforce once violations are clean
No structured data
No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
→ Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Remediation cost

€675 7.5 developer hours at €90/hr

Quick wins

€45 1 fixes in ~30 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Team composition

Multiplier applied to dev hours to reflect QA, design, and PM overhead. Use Dev only for solo work; Full team for projects with formal review processes.

Custom rate

€ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

Warning:Cost of inaction

€4.402 / month at risk ~€52.824 / year if left unfixed

Compliance Risk

€120.500.000

ePrivacy DirectiveDSGVOEAA

No privacy policy link detected
DSGVO: EUR 10.000 – EUR 20.000.000
Trackers detected but no cookie policy found
DSGVO: EUR 5.000 – EUR 10.000.000
Trackers detected but no cookie policy found
DSGVO: EUR 10.000 – EUR 20.000.000

Bounce-Rate Cost

€4.402 /mo

+20.0pp bounce · ~2,001 lost visitors/mo

CPC: EUR 2.20

Bandwidth Waste

€0,12 /mo

1569.7 MB/mo × 0.074 EUR/GB

Optimize transfer: save ~157 KB per page load
Saves €0,12/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 3 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Lighthouse

Mobile

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.95 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

3.35 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

355 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.95 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

4.04 s

Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

718 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.12 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

50 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.016

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

806 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.13 s

Categories

Better than 82% of TYPO3 CMS sites See full TYPO3 CMS benchmark →

Google Search Console · 3817 peers

You 79

Avg 73

+6 above average

0 50 100

Performance P87SEO P82Sustainability P80Security P78Infrastructure P36Content P57Compliance P56Accessibility P45

Top 10% of Google Search Console sites score 95+ on Infrastructure; you're at 86 — closing this gap is the highest-leverage improvement.

Better than 87% of Google Search Console sites See full Google Search Console benchmark →

Technology stack

TYPO3 CMS, on PHP

7 technologies detected 4 stack layers 2 with CPE identifier Complex

Stack Architecture

CMS

TYPO3 CMS

Build

Webpack

Framework

Google Search Console HSTS

Open Graph

Swiper

Runtime

PHP

All Detected Technologies (7)

PHP is a general-purpose scripting language used for web development.

Categories Programming languages Website https://php.net Detected by BeaverCheck

This technology has a CPE identifier — check for known vulnerabilities Search NVD →

TYPO3 is a free and open-source Web content management system written in PHP.

Categories CMS Website https://typo3.org/ Detected by BeaverCheck

This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=KJAYLLCiArN_v6deJkReVcWRY_zTSkhBsSBwzLU6JAQ

HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.

Categories Security Website https://www.rfc-editor.org/rfc/rfc6797#section-6.1 Detected by BeaverCheck

Open Graph is a protocol that is used to integrate any web page into the social graph.

Categories Miscellaneous Website https://ogp.me Detected by BeaverCheck

Swiper is a JavaScript library that creates modern touch sliders with hardware-accelerated transitions.

Categories JavaScript libraries Website https://swiperjs.com Detected by BeaverCheck

Categories Build Tool Website https://webpack.js.org Detected by BeaverCheck · Medium Evidence Chunk pattern: https://bundesgesundheitsministerium.de/assets/js/main.0bfc893059e856bc9f79.js

Observations (0)

No specific observations.

Show your score

Drop this badge on your README, marketing site, or status page. It auto-updates every time the audit re-runs and links back to this report.

This badge auto-updates with your latest scan result.

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fbundesgesundheitsministerium.de)](https://beavercheck.com/results/88406156-d8d1-45ad-983b-becd30509e2b)

HTML

<a href="https://beavercheck.com/results/88406156-d8d1-45ad-983b-becd30509e2b"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fbundesgesundheitsministerium.de" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fbundesgesundheitsministerium.de

Fix Plan

Three-week roadmap to ship the audit's findings, with one-click copy targets for your tracker.

Three-week fix plan

2 sprints · 8h total → projected B (87)

Sprint 1: Quick Wins

Highest ROI — low effort, high impact

2 findings 0h → B (82)

· 1 button(s) with no accessible text
· 31 third-party resources (100% of weight)

Sprint 2: Core Fixes

Medium effort, high structural impact

3 findings 7h → B (87)

· Content-Security-Policy header is missing
· No Content-Security-Policy header found
· Cross-Origin-Embedder-Policy header is missing