Audit overview
All categories sit comfortably above the 70 threshold; this is a clean audit.
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-eval' found in script source
Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.
'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.
6 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.
13 third-party resources (48% of weight)
Informational: third-party resource count and their share of page weight. High share caps perf gains from frontend optimization.
Certificate expires soon (23 days remaining)
Cert expiry within the renewal window — fix now while there's no user impact, instead of after expiry when there's a full outage.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
€1,105 investment → €9,197/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
6 barrier(s) likely increasing bounce by ~24%.
- Page takes 6.7s to loadUsers abandon at ~3s — you're 4.2s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- 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
- 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, …)
- Content is hard to readGraduate-level reading difficulty — limits the addressable audience for product or blog pages→ Shorten sentences; replace jargon with plain language; target Flesch ease ≥60
- 6 link(s) with generic text ("click here", "read more")Screen-reader users navigating by link list see no context — and search engines can't infer relevance→ Rewrite with descriptive phrases that identify the destination
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 detectedGDPR: EUR 10.000 – EUR 20.000.000
- Trackers detected but no cookie policy foundGDPR: EUR 5.000 – EUR 10.000.000
- Trackers detected but no cookie policy foundGDPR: EUR 10.000 – EUR 20.000.000
Bounce-Rate Cost
€5.289 /mo
+24.0pp bounce · ~2,404 lost visitors/mo
CPC: EUR 2.20
Bandwidth Waste
€0,24 /mo
3300.4 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~330 KB per page loadSaves €0,24/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 3 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.
1.98 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
6.68 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
188 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.011
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.98 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.
6.71 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
599 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.12 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.105
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
599 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.12 s
Categories
8Performance
13 third-party resources (48% of weight)
Security
'unsafe-eval' found in script source
Accessibility
6 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 Amazon Route 53 sites score 96+ on Content; you're at 86 — closing this gap is the highest-leverage improvement.
Technology stack
Amazon Route 53, with Fastly CDN
Stack Architecture
Google Optimize 
Google Tag Manager 
Cookie Control 
Cookiebot 1
Cybot Facebook Google Search Console Google Workspace HSTS 
Open Graph 
RSS 
Varnish 
core-js 2.6.12
Fastly 
Nginx All Detected Technologies (16)
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Cookiebot is a cloud-driven solution that automatically controls cookies and trackers, enabling full GDPR/ePrivacy and CCPA compliance for websites.
Cybot is a tool that facilitates compliance with data privacy laws for website operators and marketers.
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.
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.
Varnish is a reverse caching proxy.
core-js is a modular standard library for JavaScript, with polyfills for cutting-edge ECMAScript features.
Google Optimize allows you to test variants of web pages and see how they perform.
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 (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
16 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/ec803e20-c778-4dd2-9f64-6e18d0131395)<a href="https://beavercheck.com/results/ec803e20-c778-4dd2-9f64-6e18d0131395"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Felifesciences.org" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Felifesciences.orgExport & 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 · 13h total → projected A (90)
Sprint 1: Quick Wins
+3Highest ROI — low effort, high impact
- · 6 link(s) with no accessible text
- · 13 third-party resources (48% of weight)
- · Certificate expires soon (23 days remaining)
Sprint 3: Strategic Improvements
+4Higher effort, long-term payoff
- · 'unsafe-eval' found in script source
- · 'unsafe-inline' found in script source