Audit overview
3 categories need attention: Security, and 2 others.
Fix Priority Matrix
5 findingsQuick Wins
3High impact, low effort — start here.
Strategic
2High 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)
Content-Security-Policy header is missing
Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.
Cookie 'JSESSIONID' is missing the Secure flag
A cookie without the Secure flag can leak over HTTP — in HSTS-protected sites, this is still a defense-in-depth gap.
HSTS header is missing
Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.
No Content-Security-Policy header found
Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.
11 link(s) with no accessible text
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
CHF 910 investment → CHF 7,786/month returns + CHF 250,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
7 barrier(s) likely increasing bounce by ~24%.
- Page takes 15.4s to loadUsers abandon at ~3s — you're 12.9s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- 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
- No structured dataNo 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, …)
- Content is hard to readGraduate-level reading difficulty — limits the addressable audience for product or blog pages→ Shorten sentences; replace jargon with plain language; target Flesch ease ≥60
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
CHF 250’000
- No privacy policy link detectednDSG/FADP: CHF 1’000 – CHF 250’000
- Trackers detected but no cookie policy foundnDSG/FADP: CHF 1’000 – CHF 250’000
- Trackers detected but no privacy policy foundnDSG/FADP: CHF 1’000 – CHF 250’000
Bounce-Rate Cost
CHF 7’785 /mo
+24.3pp bounce · ~2,433 lost visitors/mo
CPC: CHF 3.20
Bandwidth Waste
CHF 0.77 /mo
10867.1 MB/mo × 0.071 CHF/GB
- Optimize transfer: save ~1.1 MB per page loadSaves CHF 0.77/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 5 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.
2.83 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
15.44 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
52 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.
8.12 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.
15.99 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
665 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.68 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.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.23 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.69 s
Categories
8Performance
All checks pass
Security
Content-Security-Policy header is missing
Accessibility
11 link(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 core-js sites score 75+ on Security; you're at 58 — closing this gap is the highest-leverage improvement.
Technology stack
Magnolia CMS, on Apache/Java, hosted on Apache HTTP Server
Stack Architecture
Piwik PRO Core 
Magnolia CMS 
Issuu 
LazySizes Microsoft 365 
Open Graph 
Swiper 
core-js 3.25.5
jQuery 3.7.1 jQuery Migrate 3.5.2
Java 
Apache Apache HTTP Server All Detected Technologies (14)
Apache is a free and open-source cross-platform web server software.
Java is a class-based, object-oriented programming language that is designed to have as few implementation dependencies as possible.
Magnolia CMS is a Java-based, open-source content management system that employs a modular architecture and JCR (Java Content Repository) standards, facilitating the creation, storage, and retrieval of digital content within a customisable framework.
Issuu is a digital discovery and publishing platform.
LazySizes is a JavaScript library used to delay the loading of images (iframes, scripts, etc) until they come into view.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Swiper is a JavaScript library that creates modern touch sliders with hardware-accelerated transitions.
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.
Query Migrate is a javascript library that allows you to preserve the compatibility of your jQuery code developed for versions of jQuery older than 1.9.
Piwik PRO Core is a free alternative to Google Analytics that is privacy & compliance focused.
Observations (2)
No build tool detected
A framework (Google Search Console) 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
14 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/64d58202-c6f3-4e9d-81f1-c13afc0889d0)<a href="https://beavercheck.com/results/64d58202-c6f3-4e9d-81f1-c13afc0889d0"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fuzh.ch" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fuzh.chExport & 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
2 sprints · 7h total → projected B (82)
Sprint 1: Quick Wins
+7Highest ROI — low effort, high impact
- · Cookie 'JSESSIONID' is missing the Secure flag
- · HSTS header is missing
- · 11 link(s) with no accessible text
Sprint 2: Core Fixes
+2Medium effort, high structural impact
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found