Audit overview
Security and Accessibility need attention; the other 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)
Cookie 'nf_ab' 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.
34 image-only link(s) without alt text
Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.
Cookie 'nf_ab' has no SameSite attribute
Without SameSite, cookies ride along on cross-site requests — enabling CSRF attacks that SameSite=Lax blocks for free.
Cookie 'nf_ab' is missing the HttpOnly flag
Without HttpOnly, JavaScript can read the cookie — an XSS bug becomes a session-stealing attack.
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.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
€191 investment → €9,262/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
5 barrier(s) likely increasing bounce by ~28%.
- Page takes 6.2s to loadUsers abandon at ~3s — you're 3.7s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 1.2sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- 4 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 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 structured dataNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices→ Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
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
- 2 of 3 <nav> elements are unlabeledEAA: EUR 1.000 – EUR 500.000
- Multiple H1 headings (7 found)EAA: EUR 1.000 – EUR 500.000
- 34 image-only link(s) without alt textEAA: EUR 1.000 – EUR 500.000
Bounce-Rate Cost
€6.219 /mo
+28.3pp bounce · ~2,827 lost visitors/mo
CPC: EUR 2.20
Bandwidth Waste
€0,25 /mo
3419.7 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~342 KB per page loadSaves €0,25/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.
2.38 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
6.17 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.18 s
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.
2.92 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.
9.56 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
906 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.14 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
6 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.005
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.18 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.
2.14 s
Categories
8Performance
All checks pass
Security
Cookie 'nf_ab' is missing the Secure flag
Accessibility
34 image-only link(s) without alt text
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.
Technology stack
Storyblok, hosted on Amazon Web Services, with AWS CloudFront CDN
Stack Architecture
Google Analytics 
Google Tag Manager 
PostHog 
Storyblok 
Astro HSTS 
Open Graph 
Priority Hints 
Rudderstack 
Sentry 
AWS CloudFront Amazon CloudFront 
Netlify 
Amazon Web Services All Detected Technologies (14)
Amazon CloudFront is a fast content delivery network (CDN) service that securely delivers data, videos, applications, and APIs to customers globally with low latency, high transfer speeds.
Netlify providers hosting and server-less backend services for web applications and static websites.
Amazon Web Services (AWS) is a comprehensive cloud services platform offering compute power, database storage, content delivery and other functionality.
Storyblok is a headless CMS with a visual editor for developers, marketers and content editors. Storyblok helps your team to manage content and digital experiences for every use-case from corporate websites, ecommerce, helpdesks, mobile apps, screen displays, and more.
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.
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.
Rudderstack is a customer data platform (CDP) that helps you collect, clean, and control your customer data.
Sentry is an open-source platform for workflow productivity, aggregating errors from across the stack in real time.
Google Analytics is a free web analytics service that tracks and reports website traffic.
Google Tag Manager is a tag management system (TMS) that allows you to quickly and easily update measurement codes and related code fragments collectively known as tags on your website or mobile app.
PostHog is the open-source, all-in-one product analytics platform.
Observations (2)
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.
Complex technology stack detected
14 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/9df146d9-4478-2dbd-75a0-36aca0c093b0)<a href="https://beavercheck.com/results/9df146d9-4478-2dbd-75a0-36aca0c093b0"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.storyblok.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.storyblok.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 · 2h total → projected B (84)
Sprint 1: Quick Wins
+5Highest ROI — low effort, high impact
- · Cookie 'nf_ab' is missing the Secure flag
- · 34 image-only link(s) without alt text
- · Cookie 'nf_ab' has no SameSite attribute
- · Cookie 'nf_ab' is missing the HttpOnly flag
Sprint 2: Core Fixes
+1Medium effort, high structural impact
- · Cross-Origin-Embedder-Policy header is missing