Global Performance
6/6 locations ✓Acceptable global latency — average 270ms across 6 locations, fastest from Santa Clara (82ms), slowest from Singapore (466ms). Cloudflare edge cache (DYNAMIC).
Audit overview
Compliance needs attention; the rest of the categories are in good shape.
Fix Priority Matrix
5 findingsQuick Wins
4High 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 (5)
Cross-Origin-Embedder-Policy header is missing
COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.
Cross-Origin-Opener-Policy header is missing
COOP isolates your top-level browsing context from cross-origin windows — without it, popup-based side-channel attacks remain possible.
HSTS max-age is too short (0s, should be ≥ 31536000s)
Short HSTS max-age leaves a downgrade-attack window every time the cache expires — set ≥ 1 year.
No Permissions-Policy header
Permissions-Policy locks down browser APIs you don't use, shrinking the attack surface.
Permissions-Policy header is missing
Permissions-Policy locks down browser APIs you don't use — without it, every page can request camera/mic/geolocation if XSS lands.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
€156 investment → €6,690/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
5 barrier(s) likely increasing bounce by ~24%.
- Page takes 4.3s to loadUsers abandon at ~3s — you're 1.8s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- 25 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
- No skip-to-content linkKeyboard and screen-reader users must tab through the entire header on every page→ Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
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
Cost of inaction
Compliance Risk
€120,500,000
- 1 non-essential cookie(s) set without consent bannerGDPR: EUR 5,000 – EUR 10,000,000
- 1 non-essential cookie(s) set without consent bannerGDPR: EUR 10,000 – EUR 20,000,000
- 1 non-essential cookie(s) set without consent bannerePrivacy Directive: EUR 5,000 – EUR 100,000,000
- Skip navigation link is missing (WCAG 2.4.1)EAA: EUR 1,000 – EUR 500,000
- 7 image(s) with generic alt textEAA: EUR 1,000 – EUR 500,000
Bounce-Rate Cost
€5,352 /mo
+24.3pp bounce · ~2,433 lost visitors/mo
CPC: EUR 2.20
Bandwidth Waste
€0.09 /mo
1212.0 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~121 KB per page loadSaves €0.09/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.62 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
4.34 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
5 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.
1.62 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.
4.34 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
470 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.47 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.009
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
516 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.47 s
Categories
8Performance
All checks pass
Security
Cross-Origin-Embedder-Policy header is missing
Accessibility
All checks pass
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 Google Search Console sites score 85+ on Compliance; you're at 67 — closing this gap is the highest-leverage improvement.
Top 10% of Google Workspace sites score 86+ on Compliance; you're at 67 — closing this gap is the highest-leverage improvement.
Technology stack
Google Search Console, on Ruby, with Cloudflare CDN
Stack Architecture
Open Graph 
RSS 
Ruby on Rails 
Stimulus 
jQuery 3.7.1
Ruby 
Cloudflare All Detected Technologies (10)
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Ruby is an open-source object-oriented programming language.
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.
Ruby on Rails is a server-side web application framework written in Ruby under the MIT License.
A modest JavaScript framework for the HTML you already have.
jQuery is a JavaScript library which is a free, open-source software designed to simplify HTML DOM tree traversal and manipulation, as well as event handling, CSS animation, and Ajax.
Observations (2)
No build tool detected
A framework (Google Search Console) 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
10 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/51b3d314-67ed-483b-9cd0-0dd19cabd0ac)<a href="https://beavercheck.com/results/51b3d314-67ed-483b-9cd0-0dd19cabd0ac"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fe621.net" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fe621.netExport & 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 (90)
Sprint 1: Quick Wins
+3Highest ROI — low effort, high impact
- · HSTS max-age is too short (0s, should be ≥ 31536000s)
- · Cross-Origin-Opener-Policy header is missing
- · No Permissions-Policy header
- · Permissions-Policy header is missing
Sprint 2: Core Fixes
Medium effort, high structural impact
- · Cross-Origin-Embedder-Policy header is missing