Audit overview
Security and Accessibility need attention; the other 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)
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.
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.
DMARC policy is none — monitoring only
DMARC p=none collects reports but doesn't actually block spoofed mail — phishing emails still reach inboxes.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
CHF 1,008 investment → CHF 6,614/month returns + CHF 250,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 ~21%.
- No viewport meta tagMobile browsers render at desktop width and shrink — text unreadable, tap targets miniature→ Add <meta name="viewport" content="width=device-width, initial-scale=1">
- 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
CHF 250’000
- No privacy policy link detectednDSG/FADP: CHF 1’000 – CHF 250’000
Bounce-Rate Cost
CHF 6’614 /mo
+20.7pp bounce · ~2,067 lost visitors/mo
CPC: CHF 3.20
Bandwidth Waste
CHF 0.00 /mo
67.8 MB/mo × 0.071 CHF/GB
- Optimize transfer: save ~7 KB per page loadSaves CHF 0.00/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.
0 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
0 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.
0 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.
0 ms
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
0 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
0 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.
0 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.
0 ms
Categories
6How you compare
Where this site stands against peers running the same stack.
Top 10% of Amazon Route 53 sites score 68+ on Accessibility; you're at 28 — closing this gap is the highest-leverage improvement.
Top 10% of Google Workspace sites score 70+ on Accessibility; you're at 28 — closing this gap is the highest-leverage improvement.
Technology stack
Amazon Route 53, on Apache, hosted on Apache HTTP Server
Stack Architecture
OpenSSL 3.2.2
Apache 2.4.64 Apache HTTP Server 2.4.64All Detected Technologies (6)
Apache is a free and open-source cross-platform web server software.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
OpenSSL is a software library for applications that secure communications over computer networks against eavesdropping or need to identify the party at the other end.
Observations (2)
Server version exposed in headers
The Server header reveals 'Apache 2.4.64'. Exposing exact server versions helps attackers target known vulnerabilities. Consider configuring your server to hide version information.
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.
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/a50c0d4d-2f31-4ae5-9f8f-5fee37379842)<a href="https://beavercheck.com/results/a50c0d4d-2f31-4ae5-9f8f-5fee37379842"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ffourmilab.ch" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Ffourmilab.chExport & 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 B (81)
Sprint 1: Quick Wins
+2Highest ROI — low effort, high impact
- · Cross-Origin-Opener-Policy header is missing
- · DMARC policy is none — monitoring only
Sprint 2: Core Fixes
+5Medium effort, high structural impact
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found
- · Cross-Origin-Embedder-Policy header is missing