Audit overview
4 categories need attention: Security, and 3 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)
Access-Control-Allow-Origin: * with credentials — critical misconfiguration
ACAO '*' combined with Allow-Credentials is rejected by browsers — your CORS LOOKS permissive but credentialed requests fail silently.
Page weighs 15.8 MB (4.0 MB transferred)
Informational: total page weight (uncompressed) and bytes actually transferred over the wire.
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.
256 HTTP requests — consider bundling or reducing
High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.
Cookie 'datadome' is missing the HttpOnly flag
Without HttpOnly, JavaScript can read the cookie — an XSS bug becomes a session-stealing attack.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
€393 investment → €12,174/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
9 barrier(s) likely increasing bounce by ~32%.
- Page takes 8.9s to loadUsers abandon at ~3s — you're 6.4s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 11.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
€20.500.000
- No privacy policy link detectedRGPD: EUR 10.000 – EUR 20.000.000
- Privacy Policy not detectedRGPD: EUR 10.000 – EUR 20.000.000
- No <main> landmark foundEAA: EUR 1.000 – EUR 500.000
Bounce-Rate Cost
€6.953 /mo
+31.6pp bounce · ~3,161 lost visitors/mo
CPC: EUR 2.20
Bandwidth Waste
€0,93 /mo
12507.7 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~1.3 MB per page loadSaves €0,93/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
Categories
8Performance
Page weighs 15.8 MB (4.0 MB transferred)
Security
Access-Control-Allow-Origin: * with credentials — critical misconfiguration
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 HSTS sites score 82+ on Security; you're at 60 — closing this gap is the highest-leverage improvement.
Technology stack
DataDome, hosted on AWS, with AWS CloudFront CDN
Stack Architecture
DataDome HSTS 
AWS CloudFront Amazon CloudFront 
AWS Amazon Web Services All Detected Technologies (6)
Amazon CloudFront is a fast content delivery network (CDN) service that securely delivers data, videos, applications, and APIs to customers globally with low latency, high transfer speeds.
Amazon Web Services (AWS) is a comprehensive cloud services platform offering compute power, database storage, content delivery and other functionality.
DataDome is a cybersecurity platform that specialises in bot protection and mitigation, offering advanced solutions to safeguard websites and mobile applications against malicious bot traffic, credential stuffing, scraping, and other automated threats.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Observations (1)
No build tool detected
A framework (DataDome) 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.
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/0b21b39f-9ce7-ce6e-d57d-521cc4ae384e)<a href="https://beavercheck.com/results/0b21b39f-9ce7-ce6e-d57d-521cc4ae384e"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.leboncoin.fr" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.leboncoin.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 · 5h total → projected C (76)
Sprint 1: Quick Wins
+7Highest ROI — low effort, high impact
- · Page weighs 15.8 MB (4.0 MB transferred)
- · No <main> landmark found
- · Access-Control-Allow-Origin: * with credentials — critical misconfiguration
- · Cookie 'datadome' is missing the HttpOnly flag
Sprint 2: Core Fixes
+1Medium effort, high structural impact
- · 256 HTTP requests — consider bundling or reducing