Audit overview
All categories sit comfortably above the 70 threshold; this is a clean audit.
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
Your mail setup has problems.
brobets.nl fails 1 mail check: No SPF record found. This is the kind of misconfiguration that sends your mail to spam.
Top Priorities (5)
Content-Security-Policy header is missing
Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.
5 render-blocking <script src> tag(s) without async/defer
Performance issues directly impact user engagement and conversion rates.
6 render-blocking stylesheet(s) -- recommended: <=3
Informational: a Permissions-Policy directive showing feature -> allowed origins.
Cookie 'csrftoken' 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
€531 investment → €8,432/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
7 barrier(s) likely increasing bounce by ~26%.
- Page takes 6.8s to loadUsers abandon at ~3s — you're 4.3s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- HSTS is enabled but max-age is short (3600s)First-visit protection is in place, but browsers forget the policy sooner than recommended→ Raise Strict-Transport-Security max-age to at least 31536000 (1 year)
- 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
- Layout shifts during page loadContent movement causes mis-clicks on CTAs and form fields→ Add width/height to images; reserve space for late-loading embeds
- 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 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
€5.717 /mo
+26.0pp bounce · ~2,598 lost visitors/mo
CPC: EUR 2.20
Bandwidth Waste
€0,34 /mo
4608.2 MB/mo × 0.074 EUR/GB
- Optimize transfer: save ~461 KB per page loadSaves €0,34/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 1 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.
3.62 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
6.78 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.142
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.62 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.
6.78 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
773 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.25 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.339
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
773 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.
1.25 s
Categories
8Performance
5 render-blocking <script src> tag(s) without async/defer
Security
Content-Security-Policy header is missing
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 Font API sites score 94+ on Content; you're at 83 — closing this gap is the highest-leverage improvement.
Technology stack
Django, on Python, with Nginx CDN
Stack Architecture
Umami 
Django 
Google Font API HSTS 
Htmx 1.9.12
Open Graph 
Ubuntu 
Python 
Nginx 1.28.0All Detected Technologies (9)
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Python is an interpreted and general-purpose programming language.
Django is a Python-based free and open-source web application framework.
Google Font API is a web service that supports open-source font files that can be used on your web designs.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Htmx is a JavaScript library for performing AJAX requests, triggering CSS transitions, and invoking WebSocket and server-sent events directly from HTML elements.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Ubuntu is a free and open-source operating system on Linux for the enterprise server, desktop, cloud, and IoT.
Umami is a self-hosted web analytics solution. It's goal is to provide a friendlier, privacy-focused alternative to Google Analytics and a free, open-sourced alternative to paid solutions.
Observations (2)
No build tool detected
A framework (Django) 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
9 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/sites/brobets.nl)<a href="https://beavercheck.com/sites/brobets.nl"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fbrobets.nl" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fbrobets.nlExport & 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 · 6h total → projected A (91)
Sprint 1: Quick Wins
+2Highest ROI — low effort, high impact
- · 6 render-blocking stylesheet(s) -- recommended: <=3
- · Cookie 'csrftoken' is missing the HttpOnly flag
Sprint 2: Core Fixes
+3Medium effort, high structural impact
- · Content-Security-Policy header is missing
- · Cross-Origin-Embedder-Policy header is missing
- · 5 render-blocking <script src> tag(s) without async/defer