Audit overview
3 categories need attention: Security, and 2 others.
Fix Priority Matrix
5 findingsQuick Wins
4High impact, low effort — start here.
Strategic
1High 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)
Access-Control-Allow-Origin: * with credentials — critical misconfiguration
ACAO '*' combined with Allow-Credentials is rejected by browsers — your CORS LOOKS permissive but credentialed requests fail silently.
No <main> landmark found
Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.
93 third-party resources (97% of weight)
Informational: third-party resource count and their share of page weight. High share caps perf gains from frontend optimization.
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.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
$192 investment → $11,830/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
6 barrier(s) likely increasing bounce by ~27%.
- Page takes 9.5s to loadUsers abandon at ~3s — you're 7.0s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- 7 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
- 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, …)
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
$7,202 /mo
+26.8pp bounce · ~2,677 lost visitors/mo
CPC: USD 2.69
Bandwidth Waste
$0.39 /mo
4922.4 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~492 KB per page loadSaves $0.39/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.
3.30 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
9.52 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
90 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.
5.15 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.58 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
979 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.10 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
0 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.214
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
979 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.
1.10 s
Categories
8Performance
93 third-party resources (97% of weight)
Security
Access-Control-Allow-Origin: * with credentials — critical misconfiguration
Accessibility
No <main> landmark found
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 WordPress sites score 97+ on Content; you're at 61 — closing this gap is the highest-leverage improvement.
Top 10% of Amazon Route 53 sites score 96+ on Content; you're at 61 — closing this gap is the highest-leverage improvement.
Technology stack
WordPress
Stack Architecture
WordPress 
Nuxt.js 
Pinia 
Priority Hints 
Product Hunt 
Vue.js All Detected Technologies (11)
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Nuxt is a Vue framework for developing modern web applications.
Pinia is a state management library for Vue.js.
Priority Hints exposes a mechanism for developers to signal a relative priority for browsers to consider when fetching resources.
Product Hunt is a community-based website that allows makers and marketers to launch their products or services and get in touch with their first real users.
Vue.js is an open-source model–view–viewmodel JavaScript framework for building user interfaces and single-page applications.
Observations (3)
WordPress detected — review security configuration
WordPress sites benefit from: protecting wp-login.php, disabling XML-RPC if unused, restricting REST API access, and keeping all plugins and themes up to date. Check the Security tab for specific findings.
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
11 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/5caf3a26-4ed5-4afd-b32a-7dfe2560224e)<a href="https://beavercheck.com/results/5caf3a26-4ed5-4afd-b32a-7dfe2560224e"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ficons8.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Ficons8.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 · 2h total → projected B (81)
Sprint 1: Quick Wins
+6Highest ROI — low effort, high impact
- · No <main> landmark found
- · Access-Control-Allow-Origin: * with credentials — critical misconfiguration
- · 93 third-party resources (97% of weight)
- · Cross-Origin-Opener-Policy header is missing
Sprint 2: Core Fixes
Medium effort, high structural impact
- · Cross-Origin-Embedder-Policy header is missing