Audit overview
Security and Accessibility need attention; the other categories are in good shape.
Fix Priority Matrix
5 findingsQuick Wins
1High impact, low effort — start here.
Strategic
4High 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 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.
2 control(s) without accessible label
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
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.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
$867 investment → $3,782/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
7 barrier(s) likely increasing bounce by ~22%.
- Page loads in 3.2sEvery additional 100ms above 2.5s costs conversions — you're 657ms over→ Target <2.5s LCP: defer non-critical scripts and optimize the hero image
- 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
- 2 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
- Viewport disables user zoomVisitors with low vision can't read the page — and some jurisdictions treat this as a legal risk→ Remove user-scalable=no; drop maximum-scale if it's below 2
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
- No <main> landmark foundADA Title III: USD 25,000 – USD 150,000
- 2 of 2 <nav> elements are unlabeledADA Title III: USD 25,000 – USD 150,000
- Skip navigation link is missing (WCAG 2.4.1)ADA Title III: USD 25,000 – USD 150,000
Bounce-Rate Cost
$2,545 /mo
+21.9pp bounce · ~2,194 lost visitors/mo
CPC: USD 1.16
Bandwidth Waste
$0.07 /mo
856.3 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~86 KB per page loadSaves $0.07/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.71 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.16 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
42 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.004
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.71 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.92 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
814 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
952 ms
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.003
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
814 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.
961 ms
Categories
8Performance
All checks pass
Security
Content-Security-Policy header is missing
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 77+ on Security; you're at 61 — closing this gap is the highest-leverage improvement.
Technology stack
WordPress, on PHP, with Nginx CDN
Stack Architecture
Jetpack 
Yoast SEO 
WooCommerce 
WordPress 
HTTP/3 
MySQL 
Open Graph 
RSS 
core-js 3.39.0
jQuery 3.5.1
PHP 
Nginx cdnjs All Detected Technologies (14)
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
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.
WooCommerce is an open-source ecommerce plugin for WordPress.
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.
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.
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.
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.
Jetpack is a popular WordPress plugin created by Automattic, the people behind WordPress.com.
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 (HSTS) 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
14 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/34787017-79e5-47c5-9314-5e9c1ccc8bbb)<a href="https://beavercheck.com/results/34787017-79e5-47c5-9314-5e9c1ccc8bbb"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fschneier.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fschneier.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 · 9h total → projected B (86)
Sprint 1: Quick Wins
+2Highest ROI — low effort, high impact
- · No <main> landmark found
Sprint 2: Core Fixes
+7Medium effort, high structural impact
- · 2 control(s) without accessible label
- · 1 image(s) missing alt attribute
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found