Audit overview
Accessibility and Content need attention; the other 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.
1 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.
73 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
CHF 1,755 investment → CHF 10,781/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
9 barrier(s) likely increasing bounce by ~31%.
- Page takes 13.8s to loadUsers abandon at ~3s — you're 11.3s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 1.8sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- 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
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 9’982 /mo
+31.2pp bounce · ~3,119 lost visitors/mo
CPC: CHF 3.20
Bandwidth Waste
CHF 0.47 /mo
6681.2 MB/mo × 0.071 CHF/GB
- Optimize transfer: save ~668 KB per page loadSaves CHF 0.47/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.
3.66 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
13.83 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.80 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.037
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
6.69 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.59 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.70 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.63 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
81 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.212
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.11 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.67 s
Categories
8Performance
73 third-party resources (100% of weight)
Security
'unsafe-eval' found in script source
Accessibility
1 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 Google Search Console sites score 95+ on Infrastructure; you're at 78 — closing this gap is the highest-leverage improvement.
Technology stack
Sitecore, hosted on Next.js
Stack Architecture
Dynatrace 
Sitecore 
GSAP Google Search Console HSTS Microsoft 365 
Microsoft ASP.NET 
OneTrust 
React 
Webpack 
lit-element 3.3.3 lit-html 2.8.0
Next.js 12.3.5All Detected Technologies (13)
Next.js is a React framework for developing single page Javascript applications.
Sitecore provides web content management, and multichannel marketing automation software.
GSAP is an animation library that allows you to create animations with JavaScript.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
ASP.NET is an open-source, server-side web-application framework designed for web development to produce dynamic web pages.
OneTrust is a cloud-based data privacy management compliance platform.
React is an open-source JavaScript library for building user interfaces or UI components.
Webpack is an open-source JavaScript module bundler.
lit-element is a simple base class for creating web components that work in any web page with any framework. lit-element uses lit-html to render into shadow DOM, and adds API to manage properties and attributes.
lit-html is a simple, modern, safe, small and fast HTML templating library for JavaScript.
Dynatrace is a technology company that produces a software intelligence platform based on artificial intelligence to monitor and optimise application performance and development, IT infrastructure, and user experience for businesses and government agencies throughout the world.
Observations (3)
No build tool detected
A framework (GSAP) 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.
Next.js version may be outdated
Detected Next.js 12.3.5. The current major version is 14. Consider updating for security patches and new features.
Complex technology stack detected
13 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/7e375f1e-6ee6-467d-80db-cad85cfadbd7)<a href="https://beavercheck.com/results/7e375f1e-6ee6-467d-80db-cad85cfadbd7"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fadecco.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fadecco.comExport & 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 (83)
Sprint 1: Quick Wins
+3Highest ROI — low effort, high impact
- · 1 link(s) with no accessible text
- · 73 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
+3Higher effort, long-term payoff
- · 'unsafe-eval' found in script source
- · 'unsafe-inline' found in script source