Audit overview
Security and Accessibility need attention; the other 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)
Content-Security-Policy header is missing
Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.
No Content-Security-Policy header found
Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.
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.
2 image-only link(s) without alt text
Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.
282 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.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
€560 investment → €6,480/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
5 barrier(s) likely increasing bounce by ~28%.
- Page takes 14.4s to loadUsers abandon at ~3s — you're 11.9s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 2.0sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- 58 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 skip-to-content linkKeyboard and screen-reader users must tab through the entire header on every page→ Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
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 detectedRGPD: EUR 10.000 – EUR 20.000.000
- 2 advertising/retargeting trackers detectedRGPD: EUR 10.000 – EUR 20.000.000
- Trackers detected but no cookie policy foundRGPD: EUR 5.000 – EUR 10.000.000
Bounce-Rate Cost
€6.057 /mo
+27.5pp bounce · ~2,753 lost visitors/mo
CPC: EUR 2.20
Bandwidth Waste
€0,42 /mo
5643.4 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~564 KB per page loadSaves €0,42/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 4 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.
5.00 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
14.42 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
2.05 s
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.
5.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.
14.52 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.65 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.87 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
393 ms
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.
2.29 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.00 s
Categories
8Performance
282 third-party resources (100% of weight)
Security
Content-Security-Policy header is missing
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 Amazon Route 53 sites score 86+ on Compliance; you're at 72 — closing this gap is the highest-leverage improvement.
Top 10% of Bootstrap sites score 86+ on Compliance; you're at 72 — closing this gap is the highest-leverage improvement.
Technology stack
Amazon Route 53
Stack Architecture
Batch 
DoubleClick Floodlight 
Google Publisher Tag 
Google Tag Manager 
Bootstrap 
Didomi Facebook Google Search Console HSTS 
Open Graph 
Priority Hints 
Svelte SvelteKit 
Vite All Detected Technologies (15)
Bootstrap is a free and open-source CSS framework directed at responsive, mobile-first front-end web development. It contains CSS and JavaScript-based design templates for typography, forms, buttons, navigation, and other interface components.
Didomi is a consent management platform helping brands and businesses collect, store and leverage their customer consents.
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.
Svelte is a free and open-source front end compiler created by Rich Harris and maintained by the Svelte core team members.
SvelteKit is the official Svelte framework for building web applications with a flexible filesystem-based routing.
Vite is a rapid development tool for modern web projects.
Batch is a web-push notifications technology provider.
Google Publisher Tag (GPT) is an ad tagging library for Google Ad Manager which is used to dynamically build ad requests.
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.
Observations (2)
No build tool detected
A framework (Amazon Route 53) 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/930bcdc5-8128-4a50-9b7e-9fc98707d194)<a href="https://beavercheck.com/results/930bcdc5-8128-4a50-9b7e-9fc98707d194"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ffrancebleu.fr" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Ffrancebleu.frExport & 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 (81)
Sprint 1: Quick Wins
+4Highest ROI — low effort, high impact
- · 1 button(s) with no accessible text
- · 2 image-only link(s) without alt text
- · 282 third-party resources (100% of weight)
Sprint 2: Core Fixes
+5Medium effort, high structural impact
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found