Skip to content
DE · EUR (€) · Estimated Applicable regulations: DSGVO · ePrivacy Directive · EAA Dev cost: €90/hr How jurisdiction is detected
Scanned
2026-05-10 13:44 UTC
Worker
🇪🇸 Madrid
Duration
38.00s
Vs prev

Global Performance

6/6 locations

High global latency — average 752ms across 6 locations, fastest from Amsterdam (79ms), slowest from Santa Clara (1960ms). No CDN detected. Cache-Control header is missing. 4 locations above the 500ms target.

Spain - Madrid
Full audit
145ms
DNS 44ms · TLS 42ms
Netherlands - Amsterdam
79ms
DNS 30ms · TLS 26ms
United Stated - New York
510ms
DNS 228ms · TLS 100ms
Brazil - Sao Paulo
979ms
DNS 357ms · TLS 217ms
United States - Santa Clara
1960ms
DNS 348ms · TLS 564ms
Singapore - Singapore
838ms
DNS 347ms · TLS 172ms
CDN: No CDN · Avg TTFB: 752ms · Cache: No cache headers

Audit overview

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

Fix Priority Matrix

5 findings

Quick Wins

0

High impact, low effort — start here.

Nothing in this quadrant — good news.

Strategic

5

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Screenshots

DESKTOP + MOBILE
Desktop
Desktop screenshot
Mobile
Mobile screenshot

Top Priorities (5)

Sorted by impact
Critical: 1

Content-Security-Policy header is missing

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

Security › Security Headers
Critical: 2

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
Critical: 3

4 control(s) without accessible label

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Accessibility › Form Accessibility
Warning: 4

1 `@font-face` rule(s) without `font-display` -- causes FOIT

Performance issues directly impact user engagement and conversion rates.

Performance › CSS Performance Depth
Warning: 5

2 render-blocking <script src> tag(s) without async/defer

Performance issues directly impact user engagement and conversion rates.

Performance › JavaScript Blocking
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 4.6s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute to it. Addressing the critical issues below would have the most immediate impact on your user trust.
2 security gaps detected — browsers may warn visitors about your site.
1 accessibility issue excludes users who rely on assistive technology.
Your LCP is 4.6s — fixing the 2 performance criticals 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

€990 investment → €8,936/month returns + EUR 500,000 risk avoided

Investment
€990
11.0 h · 5 findings
Monthly returns
€8,936
€107,230/yr
Payback
0.1 mo
+10731% Y1
Regulatory risk avoided EUR 500,000
Or — fix only the top 3 findings
€6300.1 mo payback · +16921% 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.

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 ~28%.

Barriers
7
2 crit 5 warn
Bounce delta
+28pp
added vs baseline
Score
65
C
Speed
1
Trust
2
Usability
1
Content
2
Nav
1
  • Page takes 4.6s to load
    Users abandon at ~3s — you're 2.1s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • 4 form field(s) without a label
    Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes
    → Associate every input with a visible <label for="…">; add autocomplete attributes
  • 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 Open Graph tags
    Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
    → Add og:title, og:description, og:image, og:url to the page head

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

Remediation cost

€990 11.0 developer hours at €90/hr

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.

/hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

Cost of inaction

€47,886 / month at risk ~€574,636 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

€500,000

EAA
  • Skip navigation link is missing (WCAG 2.4.1)
    EAA: EUR 1,000 – EUR 500,000
  • 1 image(s) with generic alt text
    EAA: EUR 1,000 – EUR 500,000
  • 4 control(s) without accessible label
    EAA: EUR 1,000 – EUR 500,000

Bounce-Rate Cost

€6,219 /mo

+28.3pp bounce · ~2,827 lost visitors/mo

CPC: EUR 2.20

Bandwidth Waste

€0.21 /mo

2807.9 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~281 KB per page load
    Saves €0.21/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

Unique monthly visitors from your analytics

Purchases, signups, or key actions

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

78
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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

3.02 s

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

4.64 s

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

41 ms

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

0.002

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

3.02 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.73 s

Desktop

95
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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

1.01 s

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

1.33 s

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

0 ms

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

0.021

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

1.01 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.

1.33 s

Categories

8
Avg score 82.5

How you compare

Where this site stands against peers running the same stack.

Cookie Control · 98 peers
You 83
·
Avg 74
+9 above average
0 50 100
Better than 97% of Cookie Control sites See full Cookie Control benchmark →
Cookiebot · 76 peers
You 83
·
Avg 74
+9 above average
0 50 100
Better than 97% of Cookiebot sites See full Cookiebot benchmark →

Technology stack

Cookie Control, hosted on Hetzner, with Nginx CDN

10 technologies detected 4 stack layers 2 with CPE identifier Enterprise

Stack Architecture

Analytics
Matomo Analytics
Framework
Cookie Control Cookiebot 1 Cybot HSTS Microsoft Microsoft 365 Swiper
CDN
Nginx
Hosting
Hetzner

All Detected Technologies (10)

Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.

Categories Web servers, Reverse proxies Website https://nginx.org/en Detected by BeaverCheck Evidence Server header: nginx
This technology has a CPE identifier — check for known vulnerabilities Search NVD →
Categories Hosting Detected by BeaverCheck Evidence NS record: hydrogen.ns.hetzner.com
Categories Cookie compliance Website https://www.civicuk.com/cookie-control Detected by BeaverCheck

Cookiebot is a cloud-driven solution that automatically controls cookies and trackers, enabling full GDPR/ePrivacy and CCPA compliance for websites.

Categories Cookie compliance Website https://www.cookiebot.com Detected by BeaverCheck

Cybot is a tool that facilitates compliance with data privacy laws for website operators and marketers.

Categories Cookie compliance Website https://www.cybot.com/ Detected by BeaverCheck

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
Categories Analytics Detected by BeaverCheck · Low Evidence TXT record: MS=ms28619273
Categories Email Detected by BeaverCheck Evidence MX record: bzhfreiburg-de0i.mail.protection.outlook.com

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

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

Matomo Analytics is a free and open-source web analytics application, that runs on a PHP/MySQL web-server.

Categories Analytics Website https://matomo.org Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Observations (2)

No build tool detected

A framework (Cookie Control) was detected but no bundler was identified. The build tool may not be detectable from output patterns, or the site may use the framework's built-in bundler.

Complex technology stack detected

10 technologies identified. A complex stack increases maintenance burden and attack surface. Consider whether all components are actively needed.

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.

BeaverCheck badge

This badge auto-updates with your latest scan result.

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fbzh-freiburg.de)](https://beavercheck.com/results/0c3112ca-b8ec-4a74-872a-d2a07194b876)
<a href="https://beavercheck.com/results/0c3112ca-b8ec-4a74-872a-d2a07194b876"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fbzh-freiburg.de" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fbzh-freiburg.de

Export & share

Download the audit, share with your team, or grab a fix plan ready to copy into your tracker.

Share

Copies markdown to clipboard

Export
Download Markdown Report Download JSON

Fix Plan

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

Three-week fix plan

1 sprints · 11h total → projected A (91)

Sprint 2: Core Fixes

+8

Medium effort, high structural impact

5 findings 11h → A (91)
  • · 4 control(s) without accessible label
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found
  • · 1 `@font-face` rule(s) without `font-display` -- causes FOIT
  • · 2 render-blocking <script src> tag(s) without async/defer

Send Feedback