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.
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.
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.
90 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
CZK 7,975 investment → CZK 125,495/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
9 barrier(s) likely increasing bounce by ~27%.
- Page takes 8.2s to loadUsers abandon at ~3s — you're 5.7s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- High main-thread blocking timePage is non-interactive for 496ms after first paint→ Defer third-party scripts and split large bundles
- 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 Open Graph tagsLinks 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
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 detectedGDPR: EUR 10.000 – EUR 20.000.000
- Trackers detected but no cookie policy foundGDPR: EUR 5.000 – EUR 10.000.000
- Trackers detected but no cookie policy foundGDPR: EUR 10.000 – EUR 20.000.000
Bounce-Rate Cost
CZK 68.206 /mo
+27.3pp bounce · ~2,728 lost visitors/mo
CPC: CZK 25.00
Bandwidth Waste
CZK 13 /mo
6951.1 MB/mo × 1.860 CZK/GB
- Optimize transfer: save ~695 KB per page loadSaves CZK 13/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.
6.98 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
8.18 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
496 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.
9.37 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.
14.09 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
3.31 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.88 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.042
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
4.08 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.
3.88 s
Categories
8Performance
All checks pass
Security
Content-Security-Policy header is missing
Accessibility
1 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.
Technology stack
OpenCms, on Apache/Java, hosted on Apache HTTP Server
Stack Architecture
Google Analytics 
Google Tag Manager 
Plausible 
OpenCms 
CentOS 
Font Awesome 4.6.3Google Search Console 
MediaElement.js 2.20.1Microsoft Microsoft 365 
Modernizr 2.7.2
OWL Carousel 
OpenSSL 1.1.1k
Slick 
jQuery 1.11.0
jQuery UI 1.11.4
Java 
Apache 2.4.37 Apache HTTP Server 2.4.37All Detected Technologies (19)
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.
CentOS is a Linux distribution that provides a free, community-supported computing platform functionally compatible with its upstream source, Red Hat Enterprise Linux (RHEL).
Font Awesome is a font and icon toolkit based on CSS and Less.
MediaElement.js is a set of custom Flash plugins that mimic the HTML5 MediaElement API for browsers that don't support HTML5 or don't support the media codecs.
Modernizr is a JavaScript library that detects the features available in a user's browser.
OWL Carousel is an enabled jQuery plugin that lets you create responsive carousel sliders.
OpenSSL is a software library for applications that secure communications over computer networks against eavesdropping or need to identify the party at the other end.
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.
Google Analytics is a free web analytics service that tracks and reports website traffic.
Google Tag Manager is a tag management system (TMS) that allows you to quickly and easily update measurement codes and related code fragments collectively known as tags on your website or mobile app.
Plausible is an open-source alternative to Google Analytics.
Observations (4)
Server version exposed in headers
The Server header reveals 'Apache 2.4.37'. Exposing exact server versions helps attackers target known vulnerabilities. Consider configuring your server to hide version information.
No build tool detected
A framework (CentOS) 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.
jQuery version may be outdated
Detected jQuery 1.11.0. The current major version is 3. Consider updating for security patches and new features.
Complex technology stack detected
19 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/3767d21a-4091-45f7-8687-14243dcf63c2)<a href="https://beavercheck.com/results/3767d21a-4091-45f7-8687-14243dcf63c2"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fcas.cz" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fcas.czExport & 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 C (77)
Sprint 1: Quick Wins
+6Highest ROI — low effort, high impact
- · HSTS header is missing
- · 1 button(s) with no accessible text
- · 90 link(s) with no accessible text
Sprint 2: Core Fixes
+3Medium effort, high structural impact
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found