Audit overview
3 categories need attention: Accessibility, and 2 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)
'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.
Page weighs 14.8 MB (6.5 MB transferred)
Informational: total page weight (uncompressed) and bytes actually transferred over the wire.
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.
Cookie 'XSRF-TOKEN' is missing the HttpOnly flag
Without HttpOnly, JavaScript can read the cookie — an XSS bug becomes a session-stealing attack.
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
€595 investment → €6,676/month returns + EUR 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 21.2s to loadUsers abandon at ~3s — you're 18.7s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 2.6sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- 7 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 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
€500.000
- Skip navigation link is missing (WCAG 2.4.1)EAA: EUR 1.000 – EUR 500.000
- Heading level skipped: H1 → H5 (missing H2)EAA: EUR 1.000 – EUR 500.000
- Heading level skipped: H3 → H5 (missing H4)EAA: EUR 1.000 – EUR 500.000
Bounce-Rate Cost
€6.674 /mo
+30.3pp bounce · ~3,034 lost visitors/mo
CPC: EUR 2.20
Bandwidth Waste
€1,51 /mo
20397.8 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~2.0 MB per page loadSaves €1,51/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.
16.54 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
21.24 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
2.58 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.
16.54 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.
25.34 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.11 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
4.09 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
556 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.002
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.26 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.
4.57 s
Categories
8Performance
Page weighs 14.8 MB (6.5 MB transferred)
Security
'unsafe-inline' found in script source
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.
Top 10% of Cloudflare Bot Management sites score 95+ on Content; you're at 61 — closing this gap is the highest-leverage improvement.
Technology stack
Axios, with Cloudflare CDN
Stack Architecture
Paddle 
Profitwell 
Stripe 3
Axios 
Cloudflare Bot Management Cloudflare Turnstile Facebook 
Font Awesome 
Google Font API Google Search Console Google Workspace HSTS 
HTTP/3 
Lodash 4.18.1
Moment.js 2.30.1
Vue.js 
core-js 3.9.1 Cloudflare All Detected Technologies (18)
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Promise based HTTP client for the browser and node.js
Cloudflare bot management solution identifies and mitigates automated traffic to protect websites from bad bots.
Turnstile is Cloudflare's smart CAPTCHA alternative.
Font Awesome is a font and icon toolkit based on CSS and Less.
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.
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Lodash is a JavaScript library which provides utility functions for common programming tasks using the functional programming paradigm.
Moment.js is a free and open-source JavaScript library that removes the need to use the native JavaScript Date object directly.
Vue.js is an open-source model–view–viewmodel JavaScript framework for building user interfaces and single-page applications.
core-js is a modular standard library for JavaScript, with polyfills for cutting-edge ECMAScript features.
Paddle is a billing and payment gateway for B2B SaaS companies.
Stripe offers online payment processing for internet businesses as well as fraud prevention, invoicing and subscription management.
Observations (2)
No build tool detected
A framework (Axios) 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
18 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/a7e546ad-547c-4125-a425-d6ae6dbfed43)<a href="https://beavercheck.com/results/a7e546ad-547c-4125-a425-d6ae6dbfed43"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ftinyurl.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Ftinyurl.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 · 7h total → projected B (86)
Sprint 1: Quick Wins
+6Highest ROI — low effort, high impact
- · Page weighs 14.8 MB (6.5 MB transferred)
- · 1 button(s) with no accessible text
- · Cookie 'XSRF-TOKEN' is missing the HttpOnly flag
- · Cookie '__cf_bm' has no SameSite attribute
Sprint 3: Strategic Improvements
+1Higher effort, long-term payoff
- · 'unsafe-inline' found in script source