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.
HSTS header is missing
Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.
No Content-Security-Policy header found
Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.
2 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
$775 investment → $13,509/month returns + USD 150,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 ~31%.
- Page takes 6.9s to loadUsers abandon at ~3s — you're 4.4s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 804msClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- 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
- 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
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
$150,000
- Skip navigation link is missing (WCAG 2.4.1)ADA Title III: USD 25,000 – USD 150,000
- Heading level skipped: H1 → H3 (missing H2)ADA Title III: USD 25,000 – USD 150,000
- 1 image(s) with generic alt textADA Title III: USD 25,000 – USD 150,000
Bounce-Rate Cost
$8,277 /mo
+30.8pp bounce · ~3,077 lost visitors/mo
CPC: USD 2.69
Bandwidth Waste
$0.32 /mo
3969.7 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~397 KB per page loadSaves $0.32/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.10 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
6.95 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
804 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.017
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
4.51 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.
8.55 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.11 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.
30 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.001
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.74 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.15 s
Categories
8Performance
All checks pass
Security
Content-Security-Policy header is missing
Accessibility
2 button(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 Apple sites score 76+ on Security; you're at 62 — closing this gap is the highest-leverage improvement.
Technology stack
Sitecore, on IIS, hosted on GoDaddy
Stack Architecture
Google Tag Manager 
Sitecore 
Cookie Control 
Cookiebot 1
Cybot Facebook Google Search Console Microsoft 365 
Microsoft ASP.NET 
Open Graph 
Swiper 
Windows Server 
core-js 3.17.2
IIS 10.0
GoDaddy Microsoft IIS 10.0All Detected Technologies (17)
Internet Information Services (IIS) is an extensible web server software created by Microsoft for use with the Windows NT family.
Sitecore provides web content management, and multichannel marketing automation software.
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.
ASP.NET is an open-source, server-side web-application framework designed for web development to produce dynamic web pages.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Swiper is a JavaScript library that creates modern touch sliders with hardware-accelerated transitions.
Windows Server is a brand name for a group of server operating systems.
core-js is a modular standard library for JavaScript, with polyfills for cutting-edge ECMAScript features.
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.
Observations (3)
Server version exposed in headers
The Server header reveals 'IIS 10.0'. Exposing exact server versions helps attackers target known vulnerabilities. Consider configuring your server to hide version information.
No build tool detected
A framework (Apple) 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
17 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/7f04de2f-1060-4900-990f-fd7ea4b15576)<a href="https://beavercheck.com/results/7f04de2f-1060-4900-990f-fd7ea4b15576"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Featright.org" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Featright.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
+4Highest ROI — low effort, high impact
- · HSTS header is missing
- · 2 button(s) with no accessible text
Sprint 2: Core Fixes
+5Medium effort, high structural impact
- · 4 control(s) without accessible label
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found