Audit overview
4 categories need attention: Performance, and 3 others.
Fix Priority Matrix
5 findingsQuick Wins
4High impact, low effort — start here.
Strategic
1High 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)
Page weighs 28.3 MB (16.7 MB transferred)
Informational: total page weight (uncompressed) and bytes actually transferred over the wire.
No <main> landmark found
Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.
170 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.
174 HTTP requests — consider bundling or reducing
High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.
Cookie '__cf_bm' has no SameSite attribute
Without SameSite, cookies ride along on cross-site requests — enabling CSRF attacks that SameSite=Lax blocks for free.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
€375 investment → €6,678/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
7 barrier(s) likely increasing bounce by ~30%.
- Page takes 16.3s to loadUsers abandon at ~3s — you're 13.8s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 9.7sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- 91 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 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, …)
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
€6.674 /mo
+30.3pp bounce · ~3,034 lost visitors/mo
CPC: EUR 2.20
Bandwidth Waste
€3,90 /mo
52601.8 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~5.3 MB per page loadSaves €3,90/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 2 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.79 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
16.35 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
9.72 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.001
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
9.25 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.
46.96 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.55 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
7.54 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.72 s
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.
3.36 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.36 s
Categories
8Performance
Page weighs 28.3 MB (16.7 MB transferred)
Security
Cookie '__cf_bm' has no SameSite attribute
Accessibility
No <main> landmark found
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 Cloudflare Bot Management sites score 96+ on Sustainability; you're at 62 — closing this gap is the highest-leverage improvement.
Technology stack
Builder.io, on styled-components, hosted on Next.js, with Cloudflare CDN
Stack Architecture
Datadog 
Builder.io 
Cloudflare Bot Management 
Elfsight 
Google Font API HSTS 
Open Graph 
Priority Hints 
React 
Tailwind CSS 
Transcend 
Varnish 
Webpack 
styled-components 6.1.19 Cloudflare 
Next.js 15.5.7 Next.js App Router All Detected Technologies (17)
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Next.js is a React framework for developing single page Javascript applications.
The Next.js App Router is a new paradigm for building applications using React's latest features.
Styled components is a CSS-in-JS styling framework that uses tagged template literals in JavaScript.
Builder.io is a headless CMS with a powerful drag-and-drop visual editor that lets you build and optimize digital experiences with speed and flexibility.
Cloudflare bot management solution identifies and mitigates automated traffic to protect websites from bad bots.
Elfsight is an all-in-one platform offering 70+ customisable widgets for websites.
Google Font API is a web service that supports open-source font files that can be used on your web designs.
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.
Priority Hints exposes a mechanism for developers to signal a relative priority for browsers to consider when fetching resources.
React is an open-source JavaScript library for building user interfaces or UI components.
Transcend is data privacy management compliance platform.
Varnish is a reverse caching proxy.
Webpack is an open-source JavaScript module bundler.
Datadog is a SaaS-based monitoring and analytics platform for large-scale applications and infrastructure.
Observations (3)
Runtime exposed via X-Powered-By header
The X-Powered-By header reveals 'styled-components 6.1.19'. Remove this header in production to reduce information leakage.
No build tool detected
A framework (Cloudflare Bot Management) 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/7f772b85-1a50-400c-9682-dc0d91442710)<a href="https://beavercheck.com/results/7f772b85-1a50-400c-9682-dc0d91442710"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fplayer.vimeo.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fplayer.vimeo.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
2 sprints · 4h total → projected C (77)
Sprint 1: Quick Wins
+6Highest ROI — low effort, high impact
- · Page weighs 28.3 MB (16.7 MB transferred)
- · No <main> landmark found
- · 170 third-party resources (100% of weight)
- · Cookie '__cf_bm' has no SameSite attribute
Sprint 2: Core Fixes
Medium effort, high structural impact
- · 174 HTTP requests — consider bundling or reducing