Audit overview
Accessibility needs attention; the rest of the categories are in good shape.
Fix Priority Matrix
5 findingsQuick Wins
3High impact, low effort — start here.
Strategic
2High 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)
HSTS header is missing
Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.
2 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.
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.
Cross-Origin-Opener-Policy header is missing
COOP isolates your top-level browsing context from cross-origin windows — without it, popup-based side-channel attacks remain possible.
JavaScript is 737 KB — consider code splitting or lazy loading
JavaScript bundle is large — code-split routes and lazy-load off-screen components to defer.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
€850 investment → €9,218/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
6 barrier(s) likely increasing bounce by ~27%.
- Page takes 6.8s to loadUsers abandon at ~3s — you're 4.3s 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 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
- Layout shifts during page loadContent movement causes mis-clicks on CTAs and form fields→ Add width/height to images; reserve space for late-loading embeds
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
€5.890 /mo
+26.8pp bounce · ~2,677 lost visitors/mo
CPC: EUR 2.20
Bandwidth Waste
€0,89 /mo
12052.0 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~1.2 MB per page loadSaves €0,89/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.
1.47 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
6.75 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.36 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.248
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.98 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.78 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
439 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
789 ms
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
98 ms
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.
766 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.
1.46 s
Categories
8Performance
JavaScript is 737 KB — consider code splitting or lazy loading
Security
HSTS header is missing
Accessibility
2 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 85+ on Compliance; you're at 79 — closing this gap is the highest-leverage improvement.
Technology stack
Google Search Console, on styled-components, hosted on Next.js, with Cloudfla...
Stack Architecture
Lucide 
Open Graph 
Product Hunt 
React 
Sentry 
Tally 
Webpack 
dc.js 
styled-components 6.4.0
Cloudflare 
Next.js 16.2.4All Detected Technologies (13)
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.
Styled components is a CSS-in-JS styling framework that uses tagged template literals in JavaScript.
Lucide is an open-source icon library that provides 1000+ vector (svg) files for displaying icons and symbols in digital and non-digital projects.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Product Hunt is a community-based website that allows makers and marketers to launch their products or services and get in touch with their first real users.
React is an open-source JavaScript library for building user interfaces or UI components.
Sentry is an open-source platform for workflow productivity, aggregating errors from across the stack in real time.
Tally is the simplest way to create free forms & surveys. Create any type of form in seconds, without knowing how to code, and for free.
Webpack is an open-source JavaScript module bundler.
A multi-dimensional charting library built to work natively with crossfilter and rendered using d3.js
Observations (3)
Runtime exposed via X-Powered-By header
The X-Powered-By header reveals 'styled-components 6.4.0'. Remove this header in production to reduce information leakage.
No build tool detected
A framework (Google Search Console) 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
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/d210b479-874b-4feb-9d49-60de9a083836)<a href="https://beavercheck.com/results/d210b479-874b-4feb-9d49-60de9a083836"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ftally.so" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Ftally.soExport & 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 · 10h total → projected B (87)
Sprint 1: Quick Wins
+5Highest ROI — low effort, high impact
- · HSTS header is missing
- · 2 link(s) with no accessible text
- · Cross-Origin-Opener-Policy header is missing
Sprint 2: Core Fixes
Medium effort, high structural impact
- · Cross-Origin-Embedder-Policy header is missing
Sprint 3: Strategic Improvements
+1Higher effort, long-term payoff
- · JavaScript is 737 KB — consider code splitting or lazy loading