Audit overview
3 categories need attention: Security, and 2 others.
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.
No Content-Security-Policy header found
Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.
Page weighs 18.6 MB (17.0 MB transferred)
Informational: total page weight (uncompressed) and bytes actually transferred over the wire.
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.
3 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
€413 investment → €11,702/month returns + EUR 120,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
11 barrier(s) likely increasing bounce by ~35%.
- Page takes 10.5s to loadUsers abandon at ~3s — you're 8.0s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 1.1sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- 3 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
€120.500.000
- No privacy policy link detectedRGPD: EUR 10.000 – EUR 20.000.000
- Trackers detected but no cookie policy foundRGPD: EUR 5.000 – EUR 10.000.000
- Trackers detected but no cookie policy foundRGPD: EUR 10.000 – EUR 20.000.000
Bounce-Rate Cost
€7.650 /mo
+34.8pp bounce · ~3,477 lost visitors/mo
CPC: EUR 2.20
Bandwidth Waste
€3,97 /mo
53608.6 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~5.4 MB per page loadSaves €3,97/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.63 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
10.50 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.14 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.149
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
8.64 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.
15.02 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.53 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.47 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
92 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.071
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.01 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.48 s
Categories
8Performance
Page weighs 18.6 MB (17.0 MB transferred)
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 Amazon Route 53 sites score 82+ on Sustainability; you're at 54 — closing this gap is the highest-leverage improvement.
Top 10% of core-js sites score 84+ on Sustainability; you're at 54 — closing this gap is the highest-leverage improvement.
Technology stack
Amazon Route 53, on styled-components, hosted on Next.js, with Nginx CDN
Stack Architecture
Adjust 
Datadog 
Google Tag Manager 
VWO 
Open Graph 
Osano 
React 
Webpack 
YouTube 
core-js 3.33.1
lit-html 2.8.0
styled-components 5.3.11
Nginx 
Next.js 15.5.9All Detected Technologies (18)
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Next.js is a React framework for developing single page Javascript applications.
Styled components is a CSS-in-JS styling framework that uses tagged template literals in JavaScript.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Osano is a data privacy platform that helps your website become compliant with laws such as GDPR and CCPA.
React is an open-source JavaScript library for building user interfaces or UI components.
Webpack is an open-source JavaScript module bundler.
YouTube is a video sharing service where users can create their own profile, upload videos, watch, like and comment on other videos.
core-js is a modular standard library for JavaScript, with polyfills for cutting-edge ECMAScript features.
lit-html is a simple, modern, safe, small and fast HTML templating library for JavaScript.
Adjust is the mobile marketing analytics platform.
Datadog is a SaaS-based monitoring and analytics platform for large-scale applications and infrastructure.
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.
VWO is a website testing and conversion optimisation platform.
Observations (3)
Runtime exposed via X-Powered-By header
The X-Powered-By header reveals 'styled-components 5.3.11'. Remove this header in production to reduce information leakage.
No build tool detected
A framework (Amazon Route 53) 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
18 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/e5fc2880-613d-4cc8-b200-5725f48dd040)<a href="https://beavercheck.com/results/e5fc2880-613d-4cc8-b200-5725f48dd040"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fleagueoflegends.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fleagueoflegends.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 · 8h total → projected C (79)
Sprint 1: Quick Wins
+4Highest ROI — low effort, high impact
- · Page weighs 18.6 MB (17.0 MB transferred)
- · 2 button(s) with no accessible text
Sprint 2: Core Fixes
+6Medium effort, high structural impact
- · 3 control(s) without accessible label
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found