Audit overview
All categories sit comfortably above the 70 threshold; this is a clean audit.
Fix Priority Matrix
5 findingsQuick Wins
3High impact, low effort — start here.
Strategic
1High impact, requires investment.
Easy Improvements
1Small gains, minimal effort.
Deprioritize
0Low impact, high effort — do last.
Nothing in this quadrant — good news.
Screenshots
Your mail setup has problems.
hamsterimkopf.de fails 1 mail check: Subdomain policy (sp=none) is weaker than domain policy (p=reject). This is the kind of misconfiguration that sends your mail to spam.
Top Priorities (5)
1 software version(s) disclosed in HTML: Astro v7.4.5
Each disclosed version enables direct CVE lookup -- attacker reads the version, searches the CVE database, targets the site with a tested exploit.
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.
Subdomain policy (sp=none) is weaker than domain policy (p=reject)
Informational: a labeled value pair from the audit.
Unattributable: 259ms CPU time
Informational: CPU time spent on this resource. Total >1s is a perf budget violation.
base-uri directive is missing
Missing base-uri in CSP leaves a base-tag injection attack path open even on otherwise strict policies.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
€120 investment → €361/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
1 barrier(s) likely increasing bounce by ~2%.
- 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
Warning:Cost of inaction
Compliance Risk
€500.000
- Skip navigation link is missing (WCAG 2.4.1)EAA: EUR 1.000 – EUR 500.000
Bounce-Rate Cost
€361 /mo
+1.6pp bounce · ~164 lost visitors/mo
CPC: EUR 2.20
Bandwidth Waste
€0,09 /mo
1269.1 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~127 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.24 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.33 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
15 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.010
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.24 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.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.
327 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
337 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.035
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
402 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.
338 ms
Categories
8Performance
Unattributable: 259ms CPU time
Security
1 software version(s) disclosed in HTML: Astro v7.4.5
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 86+ on Compliance; you're at 75 — closing this gap is the highest-leverage improvement.
Technology stack
Astro 7.4.5
Stack Architecture
Astro 7.4.5Google Search Console HSTS 
HTTP/3 
Open Graph 
Priority Hints All Detected Technologies (6)
Astro is a new JavaScript-based static site builder.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Priority Hints exposes a mechanism for developers to signal a relative priority for browsers to consider when fetching resources.
Observations (1)
No build tool detected
A framework (Astro) 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/sites/hamsterimkopf.de)<a href="https://beavercheck.com/sites/hamsterimkopf.de"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fhamsterimkopf.de" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fhamsterimkopf.deExport & 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 · 1h total → projected A (94)
Sprint 1: Quick Wins
+3Highest ROI — low effort, high impact
- · Subdomain policy (sp=none) is weaker than domain policy (p=reject)
- · Unattributable: 259ms CPU time
- · base-uri directive is missing
- · 1 software version(s) disclosed in HTML: Astro v7.4.5
Sprint 2: Core Fixes
Medium effort, high structural impact
- · Cross-Origin-Embedder-Policy header is missing