Audit overview
3 categories need attention: Security, and 2 others.
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.
Cookie 'ID' is missing the Secure flag
A cookie without the Secure flag can leak over HTTP — in HSTS-protected sites, this is still a defense-in-depth gap.
HSTS header is missing
Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.
No Content-Security-Policy header found
Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.
2 control(s) without accessible label
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
€638 investment → €6,816/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
8 barrier(s) likely increasing bounce by ~31%.
- 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 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
- 2 form field(s) without a labelScreen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes→ Associate every input with a visible <label for="…">; add autocomplete attributes
- No Open Graph tagsLinks shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop→ Add og:title, og:description, og:image, og:url to the page head
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
- 1 tracking cookie(s) set before consent interactionGDPR: EUR 5.000 – EUR 10.000.000
- 1 tracking cookie(s) set before consent interactionGDPR: EUR 10.000 – EUR 20.000.000
- 1 tracking cookie(s) set before consent interactionePrivacy Directive: EUR 5.000 – EUR 100.000.000
Bounce-Rate Cost
€6.816 /mo
+31.0pp bounce · ~3,098 lost visitors/mo
CPC: EUR 2.20
Bandwidth Waste
€0,05 /mo
614.8 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~61 KB per page loadSaves €0,05/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 5 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.68 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.75 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.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.68 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.76 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
634 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
714 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.
634 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.
714 ms
Categories
8Performance
All checks pass
Security
Content-Security-Policy header is missing
Accessibility
2 control(s) without accessible label
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 68+ on Accessibility; you're at 47 — closing this gap is the highest-leverage improvement.
Technology stack
Amazon Route 53, on Apache/Perl, hosted on Amazon EC2
Stack Architecture
mod_perl 2.0.7
Perl 5.16.3
Apache 2.4.37
Amazon EC2 
Amazon Web Services Apache HTTP Server 2.4.37All Detected Technologies (7)
Amazon Elastic Compute Cloud is a part of Amazon.com's cloud-computing platform, Amazon Web Services, that allows users to rent virtual computers on which to run their own computer applications.
Amazon Web Services (AWS) is a comprehensive cloud services platform offering compute power, database storage, content delivery and other functionality.
Apache is a free and open-source cross-platform web server software.
Perl is a family of two high-level, general-purpose, interpreted, dynamic programming languages.
Mod_perl is an optional module for the Apache HTTP server. It embeds a Perl interpreter into the Apache server. In addition to allowing Apache modules to be written in the Perl programming language, it allows the Apache web server to be dynamically configured by Perl programs.
Observations (3)
Server version exposed in headers
The Server header reveals 'Apache 2.4.37'. Exposing exact server versions helps attackers target known vulnerabilities. Consider configuring your server to hide version information.
Runtime exposed via X-Powered-By header
The X-Powered-By header reveals 'Perl 5.16.3'. Remove this header in production to reduce information leakage.
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/ede4100c-9adb-484e-85d9-ba1f3d211c90)<a href="https://beavercheck.com/results/ede4100c-9adb-484e-85d9-ba1f3d211c90"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fpbase.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fpbase.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 · 8h total → projected B (82)
Sprint 1: Quick Wins
+5Highest ROI — low effort, high impact
- · Cookie 'ID' is missing the Secure flag
- · HSTS header is missing
Sprint 2: Core Fixes
+4Medium effort, high structural impact
- · 2 control(s) without accessible label
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found