Audit overview
Security and Accessibility need attention; the other categories are in good shape.
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.
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.
Cross-Origin-Opener-Policy header is missing
COOP isolates your top-level browsing context from cross-origin windows — without it, popup-based side-channel attacks remain possible.
External script from redux-docs-umami.up.railway.app lacks integrity attribute
External resource without SRI — if the third-party CDN is compromised, your site executes attacker-controlled code.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
$775 investment → $4,632/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 ~17%.
- High main-thread blocking timePage is non-interactive for 366ms 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
- No structured dataNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices→ Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
- 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
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
$4,632 /mo
+17.2pp bounce · ~1,722 lost visitors/mo
CPC: USD 2.69
Bandwidth Waste
$0.08 /mo
995.1 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~100 KB per page loadSaves $0.08/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.
1.05 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.13 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
366 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.05 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.06 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
288 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
456 ms
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
18 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.005
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
288 ms
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
624 ms
Categories
8Performance
All checks pass
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 HSTS sites score 82+ on Security; you're at 59 — closing this gap is the highest-leverage improvement.
Technology stack
Docusaurus 3.6.3, with Netlify CDN
Stack Architecture
Umami 
Docusaurus 3.6.3HSTS 
JS.org 
Open Graph 
React 
Redux 
Webpack 
lit-element 4.0.6 lit-html 3.1.4
Netlify Netlify CDN All Detected Technologies (12)
Netlify providers hosting and server-less backend services for web applications and static websites.
Docusaurus is a tool for teams to publish documentation websites.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
JS.org is a provider of free subdomains for JavaScript-based projects.
Open Graph is a protocol that is used to integrate any web page into the social graph.
React is an open-source JavaScript library for building user interfaces or UI components.
Redux is a predictable state container for JavaScript applications.
Webpack is an open-source JavaScript module bundler.
lit-element is a simple base class for creating web components that work in any web page with any framework. lit-element uses lit-html to render into shadow DOM, and adds API to manage properties and attributes.
lit-html is a simple, modern, safe, small and fast HTML templating library for JavaScript.
Umami is a self-hosted web analytics solution. It's goal is to provide a friendlier, privacy-focused alternative to Google Analytics and a free, open-sourced alternative to paid solutions.
Observations (2)
No build tool detected
A framework (Docusaurus) 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/444ca29f-7a95-4aba-a6a6-0a7615522ddc)<a href="https://beavercheck.com/results/444ca29f-7a95-4aba-a6a6-0a7615522ddc"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fredux.js.org" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fredux.js.orgExport & 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 (85)
Sprint 1: Quick Wins
+2Highest ROI — low effort, high impact
- · Cross-Origin-Opener-Policy header is missing
- · External script from redux-docs-umami.up.railway.app lacks integrity attribute
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