Global Performance
5/5 locations ✓Acceptable global latency — average 454ms across 5 locations, fastest from Amsterdam (62ms), slowest from Singapore (844ms). Assets on AWS CloudFront (host cuatro.sim-cdn.nl, 76 assets); document served directly from origin (AWS). Cache-Control header is missing. 2 locations above the 500ms target.
Audit overview
Compliance 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)
Content-Security-Policy header is missing
Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.
16 render-blocking stylesheet(s) -- recommended: <=3
Informational: a Permissions-Policy directive showing feature -> allowed origins.
2 render-blocking <script src> tag(s) without async/defer
Performance issues directly impact user engagement and conversion rates.
98 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
€510 investment → €8,550/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
4 barrier(s) likely increasing bounce by ~23%.
- Page takes 8.5s to loadUsers abandon at ~3s — you're 6.0s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 1.4sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- 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 skip-to-content linkKeyboard and screen-reader users must tab through the entire header on every page→ Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
Remediation cost
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 found (page links and common paths checked)AVG: EUR 10.000 – EUR 20.000.000
- Trackers detected but no cookie policy foundAVG: EUR 5.000 – EUR 10.000.000
- Trackers detected but no cookie policy foundAVG: EUR 10.000 – EUR 20.000.000
Bounce-Rate Cost
€5.161 /mo
+23.5pp bounce · ~2,346 lost visitors/mo
CPC: EUR 2.20
Bandwidth Waste
€0,66 /mo
8879.4 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~888 KB per page loadSaves €0,66/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 1 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.
4.22 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
8.46 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.35 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.008
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
4.22 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.
11.62 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.75 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
6.26 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
208 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.012
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.29 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.
6.37 s
Categories
8Performance
16 render-blocking stylesheet(s) -- recommended: <=3
Security
Content-Security-Policy header is missing
Accessibility
All checks pass
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 Apple sites score 86+ on Compliance; you're at 68 — closing this gap is the highest-leverage improvement.
Technology stack
Apple, on Turbopack, hosted on Next.js, with Bunny CDN
Stack Architecture
Matomo Analytics Matomo Tag Manager 
Mautic 
Siteimprove 
Bunny Fonts 
Font Awesome HSTS Microsoft Microsoft 365 
Open Graph 
React 
ReadSpeaker 3.8.11
Webpack 
Turbopack Bunny 
Next.js 16.3.8All Detected Technologies (17)
Next.js is a React framework for developing single page Javascript applications.
Turbopack is an incremental bundler for JavaScript and TypeScript, written in Rust and integrated into the Next.js framework for optimized build performance.
Bunny Fonts is an open-source, privacy-first web font platform designed to put privacy back into the internet.
Font Awesome is a font and icon toolkit based on CSS and Less.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Open Graph is a protocol that is used to integrate any web page into the social graph.
React is an open-source JavaScript library for building user interfaces or UI components.
ReadSpeaker is an intuitive text-to-speech API that converts text into natural-sounding audio files for websites and applications.
Webpack is an open-source JavaScript module bundler.
Matomo Analytics is a free and open-source web analytics application, that runs on a PHP/MySQL web-server.
Matomo Tag Manager manages tracking and marketing tags.
Mautic is a free and open-source marketing automation tool for Content Management, Social Media, Email Marketing, and can be used for the integration of social networks, campaign management, forms, questionnaires, reports, etc.
Siteimprove is a digital analytics and content QA platform.
Observations (2)
No build tool detected
A framework (Apple) 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/sites/bergenopzoom.nl)<a href="https://beavercheck.com/sites/bergenopzoom.nl"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fbergenopzoom.nl" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fbergenopzoom.nlExport & 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 · 6h total → projected B (88)
Sprint 1: Quick Wins
+2Highest ROI — low effort, high impact
- · 16 render-blocking stylesheet(s) -- recommended: <=3
- · 98 third-party resources (100% of weight)
Sprint 2: Core Fixes
+4Medium effort, high structural impact
- · Content-Security-Policy header is missing
- · Cross-Origin-Embedder-Policy header is missing
- · 2 render-blocking <script src> tag(s) without async/defer