Audit overview
Accessibility and Sustainability need attention; the other categories are in good shape.
Fix Priority Matrix
5 findingsQuick Wins
3High impact, low effort — start here.
Strategic
2High 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.
Page weighs 12.8 MB (8.1 MB transferred)
Informational: total page weight (uncompressed) and bytes actually transferred over the wire.
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 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.
47 third-party resources (97% of weight)
Informational: third-party resource count and their share of page weight. High share caps perf gains from frontend optimization.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
€680 investment → €6,274/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
7 barrier(s) likely increasing bounce by ~29%.
- Page takes 34.2s to loadUsers abandon at ~3s — you're 31.7s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- High main-thread blocking timePage is non-interactive for 416ms after first paint→ Defer third-party scripts and split large bundles
- 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
- Layout shifts during page loadContent movement causes mis-clicks on CTAs and form fields→ Add width/height to images; reserve space for late-loading embeds
- No structured dataNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices→ Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
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
- 1 of 3 <nav> elements are unlabeledEAA: EUR 1.000 – EUR 500.000
- 1 image(s) missing alt attributeEAA: EUR 1.000 – EUR 500.000
Bounce-Rate Cost
€6.272 /mo
+28.5pp bounce · ~2,851 lost visitors/mo
CPC: EUR 2.20
Bandwidth Waste
€1,89 /mo
25566.8 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~2.6 MB per page loadSaves €1,89/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.13 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
34.19 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
416 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.211
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.46 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.
34.19 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
605 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.99 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.004
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
877 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.
2.99 s
Categories
8Performance
Page weighs 12.8 MB (8.1 MB transferred)
Security
'unsafe-inline' found in script source
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.
Technology stack
Wagtail, on Python, hosted on Google Cloud
Stack Architecture
Google Analytics 
Google Tag Manager 
Wagtail 
Django 
GSAP 
Google Cloud Load Balancing 
Google Cloud Trace Google Domains 
Google Font API Google Search Console Google Workspace HSTS 
HTTP/3 
Open Graph 
YouTube 
Python Google Cloud All Detected Technologies (17)
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.
GSAP is an animation library that allows you to create animations with JavaScript.
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.
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.
Open Graph is a protocol that is used to integrate any web page into the social graph.
YouTube is a video sharing service where users can create their own profile, upload videos, watch, like and comment on other videos.
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
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/068c28c3-40ca-462e-a70f-2b287952ee8b)<a href="https://beavercheck.com/results/068c28c3-40ca-462e-a70f-2b287952ee8b"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fresearch.google" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fresearch.googleExport & 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 · 8h total → projected B (87)
Sprint 1: Quick Wins
+5Highest ROI — low effort, high impact
- · Page weighs 12.8 MB (8.1 MB transferred)
- · 2 button(s) with no accessible text
- · 47 third-party resources (97% of weight)
Sprint 2: Core Fixes
+1Medium effort, high structural impact
- · 1 image(s) missing alt attribute
Sprint 3: Strategic Improvements
+3Higher effort, long-term payoff
- · 'unsafe-inline' found in script source