Audit overview
Accessibility needs attention; the rest of the 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.
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.
10 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.
4 control(s) without accessible label
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
€680 investment → €3,055/month returns + EUR 500,000 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 ~27%.
- 4 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
- 10 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
- Page loads in 2.6sEvery additional 100ms above 2.5s costs conversions — you're 116ms over→ Target <2.5s LCP: defer non-critical scripts and optimize the hero image
- High main-thread blocking timePage is non-interactive for 342ms 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
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
€500.000
- No <main> landmark foundEAA: EUR 1.000 – EUR 500.000
- 21 of 31 <nav> elements are unlabeledEAA: EUR 1.000 – EUR 500.000
- Skip navigation link is missing (WCAG 2.4.1)EAA: EUR 1.000 – EUR 500.000
Bounce-Rate Cost
€2.876 /mo
+26.8pp bounce · ~2,677 lost visitors/mo
CPC: EUR 1.07
Bandwidth Waste
€0,21 /mo
2769.0 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~277 KB per page loadSaves €0,21/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.50 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.62 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
342 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.
2.50 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.
6.49 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
651 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
696 ms
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
13 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.
907 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.62 s
Categories
8Performance
All checks pass
Security
Content-Security-Policy header is missing
Accessibility
1 link(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 Cart Functionality sites score 73+ on Accessibility; you're at 60 — closing this gap is the highest-leverage improvement.
Technology stack
Cloudflare Bot Management, on Ruby, with Cloudflare CDN
Stack Architecture
Datadog 
Cart Functionality 
WooCommerce 
Cloudflare Bot Management 
Cookie Control 
Cookiebot 1
Cybot Google Search Console HSTS 
Hammer.js 2.0.7
Open Graph 
RackCache 
Ruby on Rails 
Stimulus 
Turbo 
core-js 3.49.0
Ruby Cloudflare All Detected Technologies (18)
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Ruby is an open-source object-oriented programming language.
Websites that have a shopping cart or checkout page, either using a known ecommerce platform or a custom solution.
Cloudflare bot management solution identifies and mitigates automated traffic to protect websites from bad bots.
Cookiebot is a cloud-driven solution that automatically controls cookies and trackers, enabling full GDPR/ePrivacy and CCPA compliance for websites.
Cybot is a tool that facilitates compliance with data privacy laws for website operators and marketers.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Hammer.js is a JavaScript library for adding touch gestures like swipe, pinch, and rotate to web applications.
Open Graph is a protocol that is used to integrate any web page into the social graph.
RackCache is a quick drop-in component to enable HTTP caching for Rack-based applications.
Ruby on Rails is a server-side web application framework written in Ruby under the MIT License.
A modest JavaScript framework for the HTML you already have.
Turbo is a JavaScript framework for building fast web applications.
core-js is a modular standard library for JavaScript, with polyfills for cutting-edge ECMAScript features.
Datadog is a SaaS-based monitoring and analytics platform for large-scale applications and infrastructure.
Observations (2)
No build tool detected
A framework (Cloudflare Bot Management) 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
18 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/578610a0-8ee4-466b-8eff-5e5f969003ba)<a href="https://beavercheck.com/results/578610a0-8ee4-466b-8eff-5e5f969003ba"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fthemeforest.net" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fthemeforest.netExport & 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 (88)
Sprint 1: Quick Wins
+3Highest ROI — low effort, high impact
- · 1 link(s) with no accessible text
- · 10 button(s) with no accessible text
Sprint 2: Core Fixes
+6Medium effort, high structural impact
- · 4 control(s) without accessible label
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found