Audit overview
4 categories need attention: Security, and 3 others.
Fix Priority Matrix
5 findingsQuick Wins
2High impact, low effort — start here.
Strategic
3High 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.
1 control(s) without accessible label
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
2 link(s) with no accessible text
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Soft 404: server returns HTTP 200 for non-existent pages
Soft 404s (HTTP 200 for missing pages) confuse Google — it indexes the 'not found' page as real content and ranks it.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
$800 investment → $9,117/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
8 barrier(s) likely increasing bounce by ~24%.
- 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
- Page loads in 3.9sEvery additional 100ms above 2.5s costs conversions — you're 1.4s over→ Target <2.5s LCP: defer non-critical scripts and optimize the hero image
- 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
- 1 form field(s) without a labelScreen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes→ Associate every input with a visible <label for="…">; add autocomplete attributes
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
- No privacy policy link detectedCCPA/CPRA: USD 2,500 – USD 7,500
- Trackers detected but no cookie policy foundCCPA/CPRA: USD 2,500 – USD 7,500
- Trackers detected but no privacy policy foundCCPA/CPRA: USD 2,500 – USD 7,500
Bounce-Rate Cost
$6,467 /mo
+24.0pp bounce · ~2,404 lost visitors/mo
CPC: USD 2.69
Bandwidth Waste
$0.60 /mo
7447.4 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~745 KB per page loadSaves $0.60/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.
3.91 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.91 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
2.04 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.
3.91 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.
16.24 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.29 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.29 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
88 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.133
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.29 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.57 s
Categories
8Performance
All checks pass
Security
Content-Security-Policy header is missing
Accessibility
1 control(s) without accessible label
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 93+ on Infrastructure; you're at 80 — closing this gap is the highest-leverage improvement.
Technology stack
Contentful, on styled-components, hosted on AWS, with AWS CloudFront CDN
Stack Architecture
Statsig 3.12.0
Contentful 
Loadable-Components 
OneTrust Proofpoint 
React 
React Router 6
Sentry 
reCAPTCHA 
styled-components 5.3.3
AWS CloudFront Amazon CloudFront 
AWS Amazon Web Services All Detected Technologies (19)
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.
Styled components is a CSS-in-JS styling framework that uses tagged template literals in JavaScript.
Contentful is an API-first content management platform to create, manage and publish content on any digital channel.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Loadable-Components is a library to solve the React code-splitting client-side and server-side.
OneTrust is a cloud-based data privacy management compliance platform.
React is an open-source JavaScript library for building user interfaces or UI components.
React Router provides declarative routing for React.
Sentry is an open-source platform for workflow productivity, aggregating errors from across the stack in real time.
reCAPTCHA is a free service from Google that helps protect websites from spam and abuse.
Statsig is a modern product experimentation platform that helps product teams continuously measure impact of every single feature they launch.
Observations (3)
Runtime exposed via X-Powered-By header
The X-Powered-By header reveals 'styled-components 5.3.3'. Remove this header in production to reduce information leakage.
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
19 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/b2afdeb4-c100-3934-143f-3f3bed7f0bc6)<a href="https://beavercheck.com/results/b2afdeb4-c100-3934-143f-3f3bed7f0bc6"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.trello.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.trello.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 · 8h total → projected B (80)
Sprint 1: Quick Wins
+3Highest ROI — low effort, high impact
- · 2 link(s) with no accessible text
- · Soft 404: server returns HTTP 200 for non-existent pages
Sprint 2: Core Fixes
+5Medium effort, high structural impact
- · 1 control(s) without accessible label
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found