Global Performance
6/6 locations ✓High global latency — average 608ms across 6 locations, fastest from Amsterdam (125ms), slowest from Singapore (1111ms). No CDN detected. Cache-Control disables caching (no-store). 3 locations above the 500ms target.
Audit overview
Accessibility needs attention; the rest of the categories are in good shape.
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)
'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.
No <main> landmark found
Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.
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.
Page weight 610 KB over 1MB target
Performance issues directly impact user engagement and conversion rates.
Unattributable: 347ms CPU time
Informational: CPU time spent on this resource. Total >1s is a perf budget violation.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
€733 investment → €710/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
2 barrier(s) likely increasing bounce by ~3%.
- 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
€500,000
- No <main> landmark foundEAA: EUR 1,000 – EUR 500,000
- 2 of 2 <nav> elements are unlabeledEAA: EUR 1,000 – EUR 500,000
- Skip navigation link is missing (WCAG 2.4.1)EAA: EUR 1,000 – EUR 500,000
Bounce-Rate Cost
€709 /mo
+3.2pp bounce · ~322 lost visitors/mo
CPC: EUR 2.20
Bandwidth Waste
€0.37 /mo
5020.9 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~502 KB per page loadSaves €0.37/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 2 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.01 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.09 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
102 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.87 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.
1.32 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
275 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
296 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.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
915 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.
298 ms
Categories
8Performance
Page weight 610 KB over 1MB target
Security
'unsafe-inline' found in script source
Accessibility
No <main> landmark found
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 95+ on Infrastructure; you're at 85 — closing this gap is the highest-leverage improvement.
Top 10% of HSTS sites score 95+ on Infrastructure; you're at 85 — closing this gap is the highest-leverage improvement.
Technology stack
Google Search Console
Stack Architecture
Open Graph All Detected Technologies (3)
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.
Observations (1)
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.
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/1454d1e4-18a1-40e8-8c68-480f45b2ffe5)<a href="https://beavercheck.com/results/1454d1e4-18a1-40e8-8c68-480f45b2ffe5"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fmymoonova.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fmymoonova.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
3 sprints · 9h total → projected A (92)
Sprint 1: Quick Wins
+2Highest ROI — low effort, high impact
- · No <main> landmark found
- · Unattributable: 347ms CPU time
Sprint 2: Core Fixes
+2Medium effort, high structural impact
- · Cross-Origin-Embedder-Policy header is missing
- · Page weight 610 KB over 1MB target
Sprint 3: Strategic Improvements
+2Higher effort, long-term payoff
- · 'unsafe-inline' found in script source