Audit overview
3 categories need attention: Security, and 2 others.
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.
/.env is publicly accessible
Sensitive resource publicly accessible — restrict access or remove.
/.env.local is publicly accessible
Sensitive resource publicly accessible — restrict access or remove.
/.env.production is publicly accessible
Sensitive resource publicly accessible — restrict access or remove.
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.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
$950 investment → $16,410/month returns + USD 157,500 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
10 barrier(s) likely increasing bounce by ~37%.
- Page takes 8.5s to loadUsers abandon at ~3s — you're 6.0s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- No viewport meta tagMobile browsers render at desktop width and shrink — text unreadable, tap targets miniature→ Add <meta name="viewport" content="width=device-width, initial-scale=1">
- High main-thread blocking timePage is non-interactive for 331ms after first paint→ Defer third-party scripts and split large bundles
- 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
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
$157,500
- 1 tracking cookie(s) set before consent interactionCCPA/CPRA: USD 2,500 – USD 7,500
- No <nav> landmark foundADA Title III: USD 25,000 – USD 150,000
- Skip navigation link is missing (WCAG 2.4.1)ADA Title III: USD 25,000 – USD 150,000
Bounce-Rate Cost
$10,021 /mo
+37.3pp bounce · ~3,725 lost visitors/mo
CPC: USD 2.69
Bandwidth Waste
$0.22 /mo
2735.3 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~274 KB per page loadSaves $0.22/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 5 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.69 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
8.48 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
331 ms
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.
6.17 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.
9.79 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.56 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.84 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
110 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.
1.56 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.
2.85 s
Categories
8Performance
All checks pass
Security
'unsafe-eval' found in script source
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 HSTS sites score 83+ on Security; you're at 61 — closing this gap is the highest-leverage improvement.
Top 10% of HTTP/3 sites score 96+ on Content; you're at 67 — closing this gap is the highest-leverage improvement.
Technology stack
HSTS
Stack Architecture
HTTP/3 All Detected Technologies (2)
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Observations (2)
No build tool detected
A framework (HSTS) 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.
Minimal technology footprint
Only 2 technologies detected. This suggests a simple setup with minimal dependencies — excellent for performance and security.
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/sites/facebook.com)<a href="https://beavercheck.com/sites/facebook.com"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fm.facebook.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fm.facebook.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
3 sprints · 10h total → projected B (81)
Sprint 1: Quick Wins
+1Highest ROI — low effort, high impact
- · 1 button(s) with no accessible text
Sprint 2: Core Fixes
+6Medium effort, high structural impact
- · /.env is publicly accessible
- · /.env.local is publicly accessible
- · /.env.production is publicly accessible
Sprint 3: Strategic Improvements
+2Higher effort, long-term payoff
- · 'unsafe-eval' found in script source