Audit overview
Security and Accessibility 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)
/.env is publicly accessible
Sensitive resource publicly accessible — restrict access or remove.
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.
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.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
ISK 89,000 investment → ISK 1,019,437/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 ~27%.
- Page takes 20.9s to loadUsers abandon at ~3s — you're 18.4s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 731msClicks 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 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
ISK 1,019,306 /mo
+27.3pp bounce · ~2,728 lost visitors/mo
CPC: ISK 373.61
Bandwidth Waste
ISK 131 /mo
11826.8 MB/mo × 11.111 ISK/GB
- Optimize transfer: save ~1.2 MB per page loadSaves ISK 131/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.
1.21 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
20.85 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
731 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.074
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.83 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.
21.77 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
621 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
4.35 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.008
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
924 ms
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.35 s
Categories
8Performance
All checks pass
Security
/.env is publicly accessible
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 72+ on Accessibility; you're at 58 — closing this gap is the highest-leverage improvement.
Technology stack
Cloudflare Bot Management, on Stitches, hosted on Google Cloud, with Cloudfla...
Stack Architecture
Cloudflare Bot Management 
Goober Google Search Console Google Workspace 
HTTP/3 
Open Graph 
Priority Hints 
React 
Webpack 
Stitches Cloudflare 
Google Cloud CDN 
Google Cloud 
Next.js 14.1.1 Next.js App Router All Detected Technologies (15)
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Cloud CDN uses Google's global edge network to serve content closer to users.
Google Cloud is a suite of cloud computing 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.
Stitches is a is a CSS-in-JS styling framework with near-zero runtime, SSR, and multi-variant support.
Cloudflare bot management solution identifies and mitigates automated traffic to protect websites from bad bots.
Goober is a minified CSS-in-JS styling solution.
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
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.
Webpack is an open-source JavaScript module bundler.
Observations (2)
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
15 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/40247afa-7664-2e18-7e11-1e79b161ef4f)<a href="https://beavercheck.com/results/40247afa-7664-2e18-7e11-1e79b161ef4f"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fcodesandbox.io" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fcodesandbox.ioExport & 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 (85)
Sprint 1: Quick Wins
+4Highest ROI — low effort, high impact
- · No <main> landmark found
- · HSTS header is missing
Sprint 2: Core Fixes
+5Medium effort, high structural impact
- · /.env is publicly accessible
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found