Audit overview
Performance and Accessibility need attention; the other categories are in good shape.
Fix Priority Matrix
5 findingsQuick Wins
1High impact, low effort — start here.
Strategic
4High 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)
30 image(s) missing alt attribute
Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.
5 control(s) without accessible label
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
188 third-party resources (67% of weight)
Informational: third-party resource count and their share of page weight. High share caps perf gains from frontend optimization.
241 HTTP requests — consider bundling or reducing
High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.
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
€638 investment → €1,975/month returns + EUR 20,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
8 barrier(s) likely increasing bounce by ~33%.
- Page takes 22.9s to loadUsers abandon at ~3s — you're 20.4s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 3.8sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- 5 form field(s) without a labelScreen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes→ Associate every input with a visible <label for="…">; add autocomplete attributes
- 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 HSTS headerReturning visitors are briefly exposed to downgrade attacks on first request→ Set Strict-Transport-Security: max-age=31536000; includeSubDomains
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
€20.500.000
- 1 advertising/retargeting trackers detectedGDPR: EUR 10.000 – EUR 20.000.000
- Skip navigation link is missing (WCAG 2.4.1)EAA: EUR 1.000 – EUR 500.000
- Heading level skipped: H2 → H4 (missing H3)EAA: EUR 1.000 – EUR 500.000
Bounce-Rate Cost
€1.974 /mo
+32.8pp bounce · ~3,279 lost visitors/mo
CPC: EUR 0.60
Bandwidth Waste
€0,89 /mo
12063.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.
6.98 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
22.87 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
3.84 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.
11.93 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.
24.56 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.04 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
4.40 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
563 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.
2.71 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.88 s
Categories
8Performance
188 third-party resources (67% of weight)
Security
Cross-Origin-Embedder-Policy header is missing
Accessibility
30 image(s) missing alt attribute
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 Amazon Route 53 sites score 85+ on Performance; you're at 68 — closing this gap is the highest-leverage improvement.
Top 10% of Apple sites score 84+ on Performance; you're at 68 — closing this gap is the highest-leverage improvement.
Technology stack
Amazon Route 53, with Netlify CDN
Stack Architecture
Clearbit Reveal 
Google Analytics 
Google Tag Manager 
Microsoft Advertising 
LaunchDarkly 
Bulma 
Cookiebot Facebook 
Gatsby 4.25.7Google Search Console Google Workspace HSTS Microsoft 
React 
Webpack 
jQuery 
Netlify Netlify CDN jsDelivr CDN All Detected Technologies (21)
Netlify providers hosting and server-less backend services for web applications and static websites.
Cookiebot is a cloud-driven solution that automatically controls cookies and trackers, enabling full GDPR/ePrivacy and CCPA compliance for websites.
Gatsby is a React-based open-source framework with performance, scalability and security built-in.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
React is an open-source JavaScript library for building user interfaces or UI components.
Webpack is an open-source JavaScript module bundler.
jQuery is a JavaScript library which is a free, open-source software designed to simplify HTML DOM tree traversal and manipulation, as well as event handling, CSS animation, and Ajax.
Clearbit Reveal identifies anonymous visitors to websites.
Google Analytics is a free web analytics service that tracks and reports website traffic.
Google Tag Manager is a tag management system (TMS) that allows you to quickly and easily update measurement codes and related code fragments collectively known as tags on your website or mobile app.
Microsoft Advertising is an online advertising platform developed by Microsoft.
LaunchDarkly is a continuous delivery and feature flags as a service platform that integrates into a company's current development cycle.
Observations (2)
jQuery loaded alongside a modern framework
Both jQuery and React are loaded. Modern frameworks handle DOM manipulation natively. jQuery may be unnecessary and adds ~30KB to the page weight. Check the Performance tab for bundle analysis.
Complex technology stack detected
21 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/c98004d0-fe32-4cc6-ba76-19680f5d9f6f)<a href="https://beavercheck.com/results/c98004d0-fe32-4cc6-ba76-19680f5d9f6f"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Flaunchdarkly.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Flaunchdarkly.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 · 8h total → projected B (83)
Sprint 1: Quick Wins
+1Highest ROI — low effort, high impact
- · 188 third-party resources (67% of weight)
Sprint 2: Core Fixes
+5Medium effort, high structural impact
- · 5 control(s) without accessible label
- · 30 image(s) missing alt attribute
- · Cross-Origin-Embedder-Policy header is missing
- · 241 HTTP requests — consider bundling or reducing