Audit overview
Accessibility needs attention; the rest of the categories are in good shape.
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)
1 image(s) missing alt attribute
Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.
1 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.
2 control(s) without accessible label
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
6 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.
144 third-party resources (90% of weight)
Informational: third-party resource count and their share of page weight. High share caps perf gains from frontend optimization.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
$350 investment → $17,146/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
9 barrier(s) likely increasing bounce by ~36%.
- Page takes 4.4s to loadUsers abandon at ~3s — you're 1.9s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 3.6sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- Mixed content on HTTPS pageBrowsers block insecure subresources — broken images, missing scripts, warning badge→ Change http:// URLs inside the page to https:// (or protocol-relative)
- 6 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 HSTS headerReturning visitors are briefly exposed to downgrade attacks on first request→ Set Strict-Transport-Security: max-age=31536000; includeSubDomains
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
- 1 advertising/retargeting trackers detectedCCPA/CPRA: USD 2,500 – USD 7,500
- Trackers detected but no cookie policy foundCCPA/CPRA: USD 2,500 – USD 7,500
Bounce-Rate Cost
$13,822 /mo
+36.4pp bounce · ~3,637 lost visitors/mo
CPC: USD 3.80
Bandwidth Waste
$0.58 /mo
7270.6 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~727 KB per page loadSaves $0.58/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 4 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.29 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
4.41 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
3.63 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.013
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.97 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.
19.69 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
369 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
894 ms
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
268 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.011
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.39 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.
4.01 s
Categories
8Performance
144 third-party resources (90% of weight)
Security
All checks pass
Accessibility
1 image(s) missing alt attribute
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 86+ on Compliance; you're at 78 — closing this gap is the highest-leverage improvement.
Top 10% of Amazon Route 53 sites score 86+ on Compliance; you're at 78 — closing this gap is the highest-leverage improvement.
Technology stack
WordPress, on PHP, hosted on Kinsta, with Cloudflare CDN
Stack Architecture
Facebook Pixel 2.9.303
Google Analytics 
Google Tag Manager 
Linkedin Insight Tag 
Microsoft Advertising 
VWO 
Yoast SEO 
WordPress 
Cloudflare Bot Management Facebook SDK Google Search Console Google Workspace HSTS 
HTTP/3 Hotjar 
LazySizes 
MySQL OneTrust 
Open Graph 
Priority Hints 
RSS 
Segment 1.81.0
YouTube 
core-js 3.32.2
jQuery 3.7.1
PHP Cloudflare 
Cloudinary 
PartnerStack 
Kinsta 
Snowplow Analytics All Detected Technologies (32)
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Cloudinary is an end-to-end image- and video-management solution for websites and mobile apps, covering everything from image and video uploads, storage, manipulations, optimisations to delivery.
PartnerStack is a platform facilitating SaaS brand growth through streamlined partner management.
Kinsta is a managed WordPress hosting provider leveraging the Google Cloud Platform to offer high-performance, secure, and user-friendly hosting solutions for WordPress websites.
Snowplow is an open-source behavioral data management platform for businesses.
PHP is a general-purpose scripting language used for web development.
WordPress is a free and open-source content management system written in PHP and paired with a MySQL or MariaDB database. Features include a plugin architecture and a template system.
Cloudflare bot management solution identifies and mitigates automated traffic to protect websites from bad bots.
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.
LazySizes is a JavaScript library used to delay the loading of images (iframes, scripts, etc) until they come into view.
MySQL is an open-source relational database management system.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Priority Hints exposes a mechanism for developers to signal a relative priority for browsers to consider when fetching resources.
RSS is a family of web feed formats used to publish frequently updated works—such as blog entries, news headlines, audio, and video—in a standardized format.
Segment is a customer data platform (CDP) that helps you collect, clean, and control your customer data.
YouTube is a video sharing service where users can create their own profile, upload videos, watch, like and comment on other videos.
core-js is a modular standard library for JavaScript, with polyfills for cutting-edge ECMAScript features.
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.
Facebook pixel is an analytics tool that allows you to measure the effectiveness of your advertising.
Google Analytics is a free web analytics service that tracks and reports website traffic.
Google Tag Manager is a tag management system (TMS) that allows you to quickly and easily update measurement codes and related code fragments collectively known as tags on your website or mobile app.
LinkedIn Insight Tag is a lightweight JavaScript tag that powers conversion tracking, website audiences, and website demographics.
Microsoft Advertising is an online advertising platform developed by Microsoft.
VWO is a website testing and conversion optimisation platform.
Yoast SEO is a search engine optimisation plugin for WordPress and other platforms.
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
32 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/3a06905d-bd66-4a79-aa0d-2f4fccbddc55)<a href="https://beavercheck.com/results/3a06905d-bd66-4a79-aa0d-2f4fccbddc55"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Funbounce.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Funbounce.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 · 4h total → projected B (83)
Sprint 1: Quick Wins
+4Highest ROI — low effort, high impact
- · 1 link(s) with no accessible text
- · 6 button(s) with no accessible text
- · 144 third-party resources (90% of weight)
Sprint 2: Core Fixes
+2Medium effort, high structural impact
- · 2 control(s) without accessible label
- · 1 image(s) missing alt attribute