Global Performance
6/6 locations ✓Acceptable global latency — average 392ms across 6 locations, fastest from Madrid (123ms), slowest from Sao Paulo (593ms). No CDN detected. 1 location above the 500ms target.
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)
'unsafe-eval' found in script source
Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.
'unsafe-inline' found in script source
Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.
Wildcard '*' found in script source
script-src * defeats the entire point of CSP — any host can load scripts on your page.
5 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.
1 render-blocking <script src> tag(s) without async/defer
Performance issues directly impact user engagement and conversion rates.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
€1,318 investment → €14,150/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
7 barrier(s) likely increasing bounce by ~27%.
- 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 2.0sClicks 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
- Content is hard to readGraduate-level reading difficulty — limits the addressable audience for product or blog pages→ Shorten sentences; replace jargon with plain language; target Flesch ease ≥60
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
Cost of inaction
Compliance Risk
€20,500,000
- Privacy Policy not detectedAVG: EUR 10,000 – EUR 20,000,000
- 2 of 2 <nav> elements are unlabeledEAA: EUR 1,000 – EUR 500,000
- Skip navigation link is missing (WCAG 2.4.1)EAA: EUR 1,000 – EUR 500,000
- 1 heading(s) are over 120 characters -- likely a misformatted paragraphEAA: EUR 1,000 – EUR 500,000
Bounce-Rate Cost
€8,676 /mo
+26.8pp bounce · ~2,677 lost visitors/mo
CPC: EUR 3.24
Bandwidth Waste
€0.64 /mo
8661.1 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~866 KB per page loadSaves €0.64/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.
2.91 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
8.89 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
2.00 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.
5.77 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.
15.28 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.18 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.67 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
116 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.64 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.07 s
Categories
8Performance
1 render-blocking <script src> tag(s) without async/defer
Security
'unsafe-eval' found in script source
Accessibility
5 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 Facebook sites score 85+ on Compliance; you're at 72 — closing this gap is the highest-leverage improvement.
Top 10% of Google Search Console sites score 85+ on Compliance; you're at 72 — closing this gap is the highest-leverage improvement.
Technology stack
Facebook, on Apache, hosted on Apache HTTP Server
Stack Architecture
All Detected Technologies (17)
Apache is a free and open-source cross-platform web server software.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Iframely is a uniform delivery service for rich media embeds and URL metadata across various platforms.
OneTrust is a cloud-based data privacy management compliance platform.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Select2 is a jQuery based replacement for select boxes. It supports searching, remote data sets, and infinite scrolling of results.
Swiper is a JavaScript library that creates modern touch sliders with hardware-accelerated transitions.
Zurb Foundation is used to prototype in the browser. Allows rapid creation of websites or applications while leveraging mobile and responsive technology. The front end framework is the collection of HTML, CSS, and Javascript containing design patterns.
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.
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.
Observations (1)
Complex technology stack detected
17 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/06ec86b5-1d78-424c-ae04-635abf8d13a2)<a href="https://beavercheck.com/results/06ec86b5-1d78-424c-ae04-635abf8d13a2"><img src="https://beavercheck.com/badge?url=https%3A%2F%2FBearingpoint.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2FBearingpoint.comFix Plan
Three-week roadmap to ship the audit's findings, with one-click copy targets for your tracker.
Three-week fix plan
3 sprints · 16h total → projected B (88)
Sprint 1: Quick Wins
+1Highest ROI — low effort, high impact
- · 5 button(s) with no accessible text
Sprint 2: Core Fixes
+4Medium effort, high structural impact
- · Wildcard '*' found in script source
- · 1 render-blocking <script src> tag(s) without async/defer
Sprint 3: Strategic Improvements
Higher effort, long-term payoff
- · 'unsafe-eval' found in script source
- · 'unsafe-inline' found in script source


