Audit overview
Accessibility needs attention; the rest of the categories are in good shape.
Fix Priority Matrix
5 findingsQuick Wins
2High impact, low effort — start here.
Strategic
3High impact, requires investment.
Easy Improvements
0Small gains, minimal effort.
Nothing in this quadrant — good news.
Deprioritize
0Low impact, high effort — do last.
Nothing in this quadrant — good news.
Screenshots
Top Priorities (5)
'unsafe-eval' found in script source
Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.
'unsafe-inline' found in script source
Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.
4 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.
39 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.
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.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
€1,215 investment → €10,090/month returns + EUR 120,500,000 risk avoided
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
6 barrier(s) likely increasing bounce by ~28%.
- Page takes 10.3s to loadUsers abandon at ~3s — you're 7.8s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 680msClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- 12 broken link(s) on the pageClicks land on 404s — trust drops and the session often ends→ Fix or remove the broken destinations surfaced on the Content tab
- No HSTS headerReturning visitors are briefly exposed to downgrade attacks on first request→ Set Strict-Transport-Security: max-age=31536000; includeSubDomains
- No Content-Security-Policy headerHigher XSS blast radius — one compromised script can exfiltrate the checkout form→ Ship a reporting-only CSP first, then enforce once violations are clean
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
Remediation cost
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.
Rates reflect fully-loaded developer cost including overhead
Warning:Cost of inaction
Compliance Risk
€120.500.000
- No privacy policy link detectedDSGVO: EUR 10.000 – EUR 20.000.000
- Trackers detected but no cookie policy foundDSGVO: EUR 5.000 – EUR 10.000.000
- Trackers detected but no cookie policy foundDSGVO: EUR 10.000 – EUR 20.000.000
Bounce-Rate Cost
€6.219 /mo
+28.3pp bounce · ~2,827 lost visitors/mo
CPC: EUR 2.20
Bandwidth Waste
€0,37 /mo
4997.8 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~500 KB per page loadSaves €0,37/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.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
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
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.
5.43 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
10.35 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
680 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.
11.63 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.
10.84 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.20 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.03 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
56 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.003
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.76 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.
2.18 s
Categories
8Performance
39 third-party resources (100% of weight)
Security
'unsafe-eval' found in script source
Accessibility
4 button(s) with no accessible text
SEO
All checks pass
Infrastructure
All checks pass
Compliance
All checks pass
Content
All checks pass
Sustainability
All checks pass
How you compare
Where this site stands against peers running the same stack.
Top 10% of Bootstrap sites score 95+ on Infrastructure; you're at 77 — closing this gap is the highest-leverage improvement.
Technology stack
Plone, on Python
Stack Architecture
Matomo Analytics 
Plone 
Bootstrap 5.3.8
Bulma 
Dropzone 5.9.3Google Search Console HSTS 
LazySizes 
Leaflet 1.9.4
Livefyre 1.9.4Masonry 
MathJax 4.0.0
Open Graph 
core-js 3.9.0
jQuery 3.7.1
jQuery UI 1.13.3
Python All Detected Technologies (17)
Python is an interpreted and general-purpose programming language.
Plone is a free and open source content management system (CMS) built on top of the Zope application server.
Bootstrap is a free and open-source CSS framework directed at responsive, mobile-first front-end web development. It contains CSS and JavaScript-based design templates for typography, forms, buttons, navigation, and other interface components.
Dropzone is a JavaScript library that turns any HTML element into a dropzone.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
LazySizes is a JavaScript library used to delay the loading of images (iframes, scripts, etc) until they come into view.
Leaflet is the open-source JavaScript library for mobile-friendly interactive maps.
Livefyre is a platform that integrates with the social web to boost social interaction.
Masonry is a JavaScript library that enables a cascading grid layout, positioning elements based on available vertical space for an optimized, gap-free arrangement.
MathJax is a cross-browser JavaScript library that displays mathematical notation in web browsers, using MathML, LaTeX and ASCIIMathML markup.
Open Graph is a protocol that is used to integrate any web page into the social graph.
core-js is a modular standard library for JavaScript, with polyfills for cutting-edge ECMAScript features.
jQuery is a JavaScript library which is a free, open-source software designed to simplify HTML DOM tree traversal and manipulation, as well as event handling, CSS animation, and Ajax.
jQuery UI is a collection of GUI widgets, animated visual effects, and themes implemented with jQuery, Cascading Style Sheets, and HTML.
Matomo Analytics is a free and open-source web analytics application, that runs on a PHP/MySQL web-server.
Observations (2)
No build tool detected
A framework (Bootstrap) 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
17 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.
This badge auto-updates with your latest scan result.
[](https://beavercheck.com/results/9a3c27d8-2499-43f2-9620-fe0c917f04b0)<a href="https://beavercheck.com/results/9a3c27d8-2499-43f2-9620-fe0c917f04b0"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Funi-bonn.de" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Funi-bonn.deExport & share
Download the audit, share with your team, or grab a fix plan ready to copy into your tracker.
Copies markdown to clipboard
Fix Plan
Three-week roadmap to ship the audit's findings, with one-click copy targets for your tracker.
Three-week fix plan
3 sprints · 14h total → projected B (82)
Sprint 1: Quick Wins
+2Highest ROI — low effort, high impact
- · 4 button(s) with no accessible text
- · 39 third-party resources (100% of weight)
Sprint 2: Core Fixes
+1Medium effort, high structural impact
- · Cross-Origin-Embedder-Policy header is missing
Sprint 3: Strategic Improvements
+4Higher effort, long-term payoff
- · 'unsafe-eval' found in script source
- · 'unsafe-inline' found in script source