Global Performance
6/6 locations ✓High global latency — average 942ms across 6 locations, fastest from Santa Clara (684ms), slowest from Madrid (1896ms). No CDN detected. Cache-Control header is missing. 6 locations above the 500ms target.
Audit overview
Compliance needs attention; the rest of the categories are in good shape.
Fix Priority Matrix
5 findingsQuick Wins
1High impact, low effort — start here.
Strategic
4High 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)
'unsafe-inline' found in script source
Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.
No H1 heading found
No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.
1 render-blocking <script src> tag(s) without async/defer
Performance issues directly impact user engagement and conversion rates.
115 HTTP requests — consider bundling or reducing
High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.
13 inline style attribute(s) detected
Inline style attributes force `style-src 'unsafe-inline'` in any CSP -- effectively negating CSP's XSS-mitigation value for stylesheets.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
DKK 10,508 investment → DKK 57,604/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 ~28%.
- Page feels frozen for 2.2sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- 7 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
- Page loads in 3.8sEvery additional 100ms above 2.5s costs conversions — you're 1.3s over→ Target <2.5s LCP: defer non-critical scripts and optimize the hero image
- 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
€120.500.000
- No privacy policy link detectedGDPR: EUR 10.000 – EUR 20.000.000
- 2 non-essential cookie(s) set without consent bannerGDPR: EUR 5.000 – EUR 10.000.000
- 2 non-essential cookie(s) set without consent bannerGDPR: EUR 10.000 – EUR 20.000.000
Bounce-Rate Cost
DKK 44.054 /mo
+27.5pp bounce · ~2,753 lost visitors/mo
CPC: DKK 16.00
Bandwidth Waste
DKK 2,59 /mo
4690.8 MB/mo × 0.552 DKK/GB
- Optimize transfer: save ~469 KB per page loadSaves DKK 2,59/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.98 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.78 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
2.19 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.
4.34 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.
10.03 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
778 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.13 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
286 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.703
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.41 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.26 s
Categories
8Performance
1 render-blocking <script src> tag(s) without async/defer
Security
'unsafe-inline' found in script source
Accessibility
No H1 heading found
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 HSTS sites score 86+ on Compliance; you're at 54 — closing this gap is the highest-leverage improvement.
Technology stack
Elasticsearch
Stack Architecture
Elastic APM 
Elasticsearch HSTS 
Nuxt UI Nuxt.js 
Open Graph 
Tailwind CSS 
Vue.js All Detected Technologies (8)
Elasticsearch is a search engine based on the Lucene library. It provides a distributed, multitenant-capable full-text search engine with an HTTP web interface and schema-free JSON documents.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Nuxt UI is a customizable UI library designed for Nuxt.
Nuxt is a Vue framework for developing modern web applications.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Vue.js is an open-source model–view–viewmodel JavaScript framework for building user interfaces and single-page applications.
Elastic APM offers free and open application performance monitoring.
Observations (2)
No build tool detected
A framework (Elasticsearch) 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
8 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/4aefde1d-d8d5-4d0c-9c1d-fc803a464e29)<a href="https://beavercheck.com/results/4aefde1d-d8d5-4d0c-9c1d-fc803a464e29"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fdanbritdirect.dk" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fdanbritdirect.dkExport & 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
3 sprints · 16h total → projected B (89)
Sprint 1: Quick Wins
+2Highest ROI — low effort, high impact
- · No H1 heading found
Sprint 2: Core Fixes
+3Medium effort, high structural impact
- · 1 render-blocking <script src> tag(s) without async/defer
- · 115 HTTP requests — consider bundling or reducing
- · 13 inline style attribute(s) detected
Sprint 3: Strategic Improvements
+1Higher effort, long-term payoff
- · 'unsafe-inline' found in script source