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)
'unsafe-inline' found in script source
Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.
HSTS header is missing
Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.
1 control(s) without accessible label
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
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.
is missing width/height — may cause layout shift
Performance issues directly impact user engagement and conversion rates.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
$975 investment → $12,771/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
5 barrier(s) likely increasing bounce by ~25%.
- Page takes 9.6s to loadUsers abandon at ~3s — you're 7.1s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- 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
- 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
- 1 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
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
- Trackers detected but no cookie policy foundCCPA/CPRA: USD 2,500 – USD 7,500
- Trackers detected but no privacy policy foundCCPA/CPRA: USD 2,500 – USD 7,500
Bounce-Rate Cost
$6,771 /mo
+25.2pp bounce · ~2,517 lost visitors/mo
CPC: USD 2.69
Bandwidth Waste
$0.32 /mo
3964.7 MB/mo × 0.080 USD/GB
- Optimize transfer: save ~396 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 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.
2.85 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
9.57 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
174 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.
4.54 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.
9.64 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
564 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.28 s
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.001
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
940 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.28 s
Categories
8Performance
is missing width/height — may cause layout shift
Security
'unsafe-inline' found in script source
Accessibility
1 control(s) without accessible label
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.
Technology stack
Wagtail, on Python, hosted on Google Cloud
Stack Architecture
Google Analytics 
Google Tag Manager 
Wagtail 
Django 
Google Cloud Load Balancing 
Google Cloud Trace 
Google Font API Google Search Console Google Workspace Masonry 
Open Graph 
Tailwind CSS 
Python Google Cloud All Detected Technologies (14)
Google Cloud is a suite of cloud computing services.
Python is an interpreted and general-purpose programming language.
Wagtail is a Django content management system (CMS) focused on flexibility and user experience.
Django is a Python-based free and open-source web application framework.
Google Cloud Load Balancing is a scalable, fully managed global load balancing service using Google Frontend.
Google Cloud Trace is a distributed tracing system that collects latency data from applications and displays it in the Google Cloud Console.
Google Font API is a web service that supports open-source font files that can be used on your web designs.
Masonry is a JavaScript library that enables a cascading grid layout, positioning elements based on available vertical space for an optimized, gap-free arrangement.
Open Graph is a protocol that is used to integrate any web page into the social graph.
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.
Observations (2)
No build tool detected
A framework (Django) 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/9c03650f-6ab1-4eb0-a416-1bfbc95d6750)<a href="https://beavercheck.com/results/9c03650f-6ab1-4eb0-a416-1bfbc95d6750"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fblog.youtube" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fblog.youtubeExport & 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
3 sprints · 10h total → projected B (88)
Sprint 1: Quick Wins
+4Highest ROI — low effort, high impact
- · HSTS header is missing
- · 1 link(s) with no accessible text
Sprint 2: Core Fixes
+2Medium effort, high structural impact
- · 1 control(s) without accessible label
- · is missing width/height — may cause layout shift
Sprint 3: Strategic Improvements
+3Higher effort, long-term payoff
- · 'unsafe-inline' found in script source