Audit overview
Accessibility and Sustainability 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)
2 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.
4 control(s) without accessible label
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
104 third-party resources (100% of weight)
Informational: third-party resource count and their share of page weight. High share caps perf gains from frontend optimization.
105 HTTP requests — consider bundling or reducing
High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.
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.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
$650 investment → $14,632/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
7 barrier(s) likely increasing bounce by ~33%.
- Page takes 5.2s to loadUsers abandon at ~3s — you're 2.7s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 695msClicks 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
- 5 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
$11,477 /mo
+32.8pp bounce · ~3,279 lost visitors/mo
CPC: USD 3.50
Bandwidth Waste
$0.51 /mo
6396.6 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~640 KB per page loadSaves $0.51/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.46 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
5.23 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
695 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.034
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
5.59 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.
14.60 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.26 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.88 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
9 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.018
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.08 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.94 s
Categories
8Performance
104 third-party resources (100% of weight)
Security
Cross-Origin-Embedder-Policy header is missing
Accessibility
2 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 WordPress sites score 73+ on Accessibility; you're at 53 — closing this gap is the highest-leverage improvement.
Technology stack
WordPress, on PHP, hosted on Amazon Web Services, with Amazon S3 CDN
Stack Architecture
Facebook Pixel 2.9.303
Google Analytics 
Google Tag Manager 
Max Mega Menu 
SHE Media 
WordPress 
Admiral 
Adobe Fonts 1.21.0Amazon Route 53 Facebook Facebook SDK Flickity 
Google Font API Google Search Console HSTS 
Lodash 1.13.7Microsoft Microsoft 365 
MySQL 
OneTrust 
Open Graph 
Priority Hints 
RSS 
Reddit 
Typekit 1.21.0
core-js 3.40.0
jQuery 3.7.1
PHP 
Python 
Amazon S3 
Nginx 
Amazon Web Services 
Snowplow Analytics 
WordPress VIP All Detected Technologies (34)
Amazon S3 or Amazon Simple Storage Service is a service offered by Amazon Web Services (AWS) that provides object storage through a web service interface.
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Amazon Web Services (AWS) is a comprehensive cloud services platform offering compute power, database storage, content delivery and other functionality.
Snowplow is an open-source behavioral data management platform for businesses.
WordPress VIP is a managed hosting platform for WordPress.
PHP is a general-purpose scripting language used for web development.
Python is an interpreted and general-purpose programming language.
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.
Admiral is a Visitor Relationship Management (VRM) platform.
Adobe Fonts is a web-based service providing access to a vast library of high-quality fonts for web and print design.
Flickity is a JavaScript slider library, built by David DeSandro of Metafizzy fame.
Google Font API is a web service that supports open-source font files that can be used on your web designs.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Lodash is a JavaScript library which provides utility functions for common programming tasks using the functional programming paradigm.
MySQL is an open-source relational database management system.
OneTrust is a cloud-based data privacy management compliance platform.
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.
Typekit is an online service which offers a subscription library of fonts.
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.
Max Mega Menu is a popular WordPress plugin that enhances the menu functionality on WordPress websites.
SHE Media is an ad network, which means that they basically serve as a coordinator between advertisers and publishers (bloggers).
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 (Admiral) 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
34 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/2f58d7db-14f6-4ad0-9b34-3eac7d30d521)<a href="https://beavercheck.com/results/2f58d7db-14f6-4ad0-9b34-3eac7d30d521"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fsheknows.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fsheknows.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 · 6h total → projected B (81)
Sprint 1: Quick Wins
+2Highest ROI — low effort, high impact
- · 2 link(s) with no accessible text
- · 104 third-party resources (100% of weight)
Sprint 2: Core Fixes
+4Medium effort, high structural impact
- · 4 control(s) without accessible label
- · Cross-Origin-Embedder-Policy header is missing
- · 105 HTTP requests — consider bundling or reducing