Audit overview
All categories sit comfortably above the 70 threshold; this is a clean audit.
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)
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.
173 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.
174 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
€880 investment → €7,187/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 ~31%.
- Page takes 12.8s to loadUsers abandon at ~3s — you're 10.3s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 5.4sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- 10 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
- Thin contentUnder 300 words — visitors bounce looking for substance, search engines rank competitors first→ Add a substantive FAQ, product detail, or case-study section
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
€120.500.000
- No privacy policy link detectedRGPD: EUR 10.000 – EUR 20.000.000
- Trackers detected but no cookie policy foundRGPD: EUR 5.000 – EUR 10.000.000
- Trackers detected but no cookie policy foundRGPD: EUR 10.000 – EUR 20.000.000
Bounce-Rate Cost
€6.816 /mo
+31.0pp bounce · ~3,098 lost visitors/mo
CPC: EUR 2.20
Bandwidth Waste
€0,84 /mo
11349.0 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~1.1 MB per page loadSaves €0,84/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.
2.77 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
12.78 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
5.39 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.021
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
7.97 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.
18.17 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
773 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.79 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
605 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.011
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.75 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.
3.94 s
Categories
8Performance
173 third-party resources (100% of weight)
Security
Content-Security-Policy header is missing
Accessibility
All checks pass
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 73 — closing this gap is the highest-leverage improvement.
Top 10% of Facebook sites score 85+ on Compliance; you're at 73 — closing this gap is the highest-leverage improvement.
Technology stack
Amazon Route 53, on Ruby, with Nginx CDN
Stack Architecture
Open Graph 
RequireJS 
Ruby on Rails iOS app 
Ruby 
Nginx All Detected Technologies (12)
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Ruby is an open-source object-oriented programming language.
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.
RequireJS is a JavaScript library and file loader which manages the dependencies between JavaScript files and in modular programming.
Ruby on Rails is a server-side web application framework written in Ruby under the MIT License.
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
12 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/203aa776-a30c-4174-8b54-825afb2aa0c5)<a href="https://beavercheck.com/results/203aa776-a30c-4174-8b54-825afb2aa0c5"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fairbnb.fr" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fairbnb.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 · 11h total → projected B (81)
Sprint 1: Quick Wins
+1Highest ROI — low effort, high impact
- · 173 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
- · Cross-Origin-Embedder-Policy header is missing
- · 174 HTTP requests — consider bundling or reducing