Global Performance
5/5 locations ✓High global latency — average 781ms across 5 locations, fastest from Amsterdam (208ms), slowest from Sao Paulo (1274ms). No CDN detected. 4 locations above the 500ms target.
Audit overview
All categories sit comfortably above the 70 threshold; this is a clean audit.
Fix Priority Matrix
3 findingsQuick Wins
2High impact, low effort — start here.
Strategic
1High 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 (3)
Unattributable: 286ms CPU time
Informational: CPU time spent on this resource. Total >1s is a perf budget violation.
https://beavercheck.com/: 663ms CPU time
Informational: CPU time spent on this resource. Total >1s is a perf budget violation.
DNS resolution is slow (423 ms)
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
€160 investment → €903/month returns
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
1 barrier(s) likely increasing bounce by ~3%.
- 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
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
Remediation cost
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
Bounce-Rate Cost
€903 /mo
+3.2pp bounce · ~322 lost visitors/mo
CPC: EUR 2.80
Bandwidth Waste
€0,04 /mo
567.6 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~57 KB per page loadSaves €0,04/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
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.21 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.21 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
167 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.003
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.86 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.18 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
429 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
429 ms
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.008
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
938 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.
429 ms
Categories
8Performance
Unattributable: 286ms CPU time
Security
All checks pass
Accessibility
All checks pass
SEO
All checks pass
Infrastructure
DNS resolution is slow (423 ms)
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 Google Search Console sites score 95+ on Infrastructure; you're at 90 — closing this gap is the highest-leverage improvement.
Technology stack
Alpine.js 3.15.9, hosted on OVH, with Nginx CDN
Stack Architecture
Alpine.js 3.15.9Google Search Console HSTS 
Htmx 2.0.8
Open Graph 
Tailwind CSS 
Nginx 
OVH All Detected Technologies (8)
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Alpine.js is a minimal framework for composing behavior directly in your markup.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Htmx is a JavaScript library for performing AJAX requests, triggering CSS transitions, and invoking WebSocket and server-sent events directly from HTML elements.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Observations (2)
No build tool detected
A framework (Alpine.js) 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
8 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/sites/beavercheck.com)<a href="https://beavercheck.com/sites/beavercheck.com"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fbeavercheck.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fbeavercheck.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 · 2h total → projected A (94)
Sprint 1: Quick Wins
+2Highest ROI — low effort, high impact
- · Unattributable: 286ms CPU time
- · https://beavercheck.com/: 663ms CPU time
Sprint 2: Core Fixes
Medium effort, high structural impact
- · DNS resolution is slow (423 ms)