Audit overview
4 categories need attention: Security, and 3 others.
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)
'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.
Cookie 'locale' is missing the Secure flag
A cookie without the Secure flag can leak over HTTP — in HSTS-protected sites, this is still a defense-in-depth gap.
Page weighs 18.0 MB (11.4 MB transferred)
Informational: total page weight (uncompressed) and bytes actually transferred over the wire.
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
$1,275 investment → $15,782/month returns + USD 7,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
7 barrier(s) likely increasing bounce by ~30%.
- Page takes 5.6s to loadUsers abandon at ~3s — you're 3.1s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 3.3sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- 20 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 Open Graph tagsLinks shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop→ Add og:title, og:description, og:image, og:url to the page head
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
$7,500
- No privacy policy link detectedCCPA/CPRA: USD 2,500 – USD 7,500
- Privacy Policy not detectedCCPA/CPRA: USD 2,500 – USD 7,500
Bounce-Rate Cost
$11,528 /mo
+30.3pp bounce · ~3,034 lost visitors/mo
CPC: USD 3.80
Bandwidth Waste
$2.87 /mo
35879.3 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~3.6 MB per page loadSaves $2.87/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.
2.87 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
5.64 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
3.31 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.053
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
6.63 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.
21.03 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.07 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.63 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
601 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.023
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.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.
9.80 s
Categories
8Performance
Page weighs 18.0 MB (11.4 MB transferred)
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 92+ on Sustainability; you're at 56 — closing this gap is the highest-leverage improvement.
Top 10% of HTTP/3 sites score 96+ on Sustainability; you're at 56 — closing this gap is the highest-leverage improvement.
Technology stack
HSTS, with Envoy CDN
Stack Architecture
Google Sign-in 
PayPal 
HTTP/3 
Lenis 1.0.42
Lodash 
Paper.js 
Priority Hints 
React 
RequireJS 
RxJS 
Sentry 
Wink 
jQuery 
Envoy All Detected Technologies (15)
Envoy is an open-source edge and service proxy, designed for cloud-native applications.
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.
Lenis is a smooth scroll library to normalise the scrolling experience across devices.
Lodash is a JavaScript library which provides utility functions for common programming tasks using the functional programming paradigm.
Paper.js is an open-source vector graphics scripting framework that operates on the HTML5 Canvas.
Priority Hints exposes a mechanism for developers to signal a relative priority for browsers to consider when fetching resources.
RequireJS is a JavaScript library and file loader which manages the dependencies between JavaScript files and in modular programming.
RxJS is a reactive library used to implement reactive programming to deal with async implementation, callbacks, and event-based programs.
Sentry is an open-source platform for workflow productivity, aggregating errors from across the stack in real time.
Wink Toolkit is a JavaScript toolkit used to build mobile web apps.
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 Sign-In is a secure authentication system that reduces the burden of login for users, by enabling them to sign in with their Google account.
PayPal is an online payments system that supports online money transfers and serves as an electronic alternative to traditional paper methods like checks and money orders.
Observations (3)
jQuery loaded alongside a modern framework
Both jQuery and React are loaded. Modern frameworks handle DOM manipulation natively. jQuery may be unnecessary and adds ~30KB to the page weight. Check the Performance tab for bundle analysis.
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.
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/48a24ff3-6aa4-41d9-b02a-2d8212a6ee37)<a href="https://beavercheck.com/results/48a24ff3-6aa4-41d9-b02a-2d8212a6ee37"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.dropbox.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.dropbox.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
2 sprints · 13h total → projected B (83)
Sprint 1: Quick Wins
+7Highest ROI — low effort, high impact
- · Page weighs 18.0 MB (11.4 MB transferred)
- · Cookie 'locale' is missing the Secure flag
- · 1 button(s) with no accessible text
Sprint 3: Strategic Improvements
+3Higher effort, long-term payoff
- · 'unsafe-eval' found in script source
- · 'unsafe-inline' found in script source