Global Performance
6/6 locations ✓High global latency — average 584ms across 6 locations, fastest from Amsterdam (98ms), slowest from Sao Paulo (1030ms). No CDN (document or assets). Cache-Control header is missing. 3 locations above the 500ms target.
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
Top Priorities (5)
Content-Security-Policy header is missing
Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.
HSTS header is missing
Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.
4 control(s) without accessible label
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
Soft 404: server returns HTTP 200 for non-existent pages
Soft 404s (HTTP 200 for missing pages) confuse Google — it indexes the 'not found' page as real content and ranks it.
1 render-blocking <script src> tag(s) without async/defer
Performance issues directly impact user engagement and conversion rates.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
DKK 4,388 investment → DKK 86,276/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
9 barrier(s) likely increasing bounce by ~31%.
- Page takes 8.3s to loadUsers abandon at ~3s — you're 5.8s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- 4 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
- High main-thread blocking timePage is non-interactive for 224ms after first paint→ Defer third-party scripts and split large bundles
- 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
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
- Multiple H1 headings (2 found)EAA: EUR 1.000 – EUR 500.000
- 1 image(s) with generic alt textEAA: EUR 1.000 – EUR 500.000
Bounce-Rate Cost
DKK 49.232 /mo
+30.8pp bounce · ~3,077 lost visitors/mo
CPC: DKK 16.00
Bandwidth Waste
DKK 1,43 /mo
2586.4 MB/mo × 0.552 DKK/GB
- Optimize transfer: save ~259 KB per page loadSaves DKK 1,43/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 4 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.06 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
8.27 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
224 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.
3.90 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.
8.30 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.01 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.11 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1 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.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.
1.81 s
Categories
8Performance
1 render-blocking <script src> tag(s) without async/defer
Security
Content-Security-Policy header is missing
Accessibility
4 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 Apple sites score 94+ on Infrastructure; you're at 76 — closing this gap is the highest-leverage improvement.
Technology stack
Apple, on Caddy/Go
Stack Architecture
BrightEdge 1.5.36
Google Analytics 
Google Tag Manager 
Cookie Control 
Cookiebot 1
Cybot Flickity 
GSAP 
HTTP/3 
LazySizes Microsoft Microsoft 365 
Open Graph 
PubSubJS 
Tailwind CSS 
Go 
Caddy All Detected Technologies (18)
Caddy is a Go-based web server known for its simplicity and automatic HTTPS features.
Go is an open source high-level programming language.
Cookiebot is a cloud-driven solution that automatically controls cookies and trackers, enabling full GDPR/ePrivacy and CCPA compliance for websites.
Cybot is a tool that facilitates compliance with data privacy laws for website operators and marketers.
Flickity is a JavaScript slider library, built by David DeSandro of Metafizzy fame.
GSAP is an animation library that allows you to create animations with JavaScript.
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
LazySizes is a JavaScript library used to delay the loading of images (iframes, scripts, etc) until they come into view.
Open Graph is a protocol that is used to integrate any web page into the social graph.
PubSubJS is a topic-based publish/subscribe library written in JavaScript.
BrightEdge is an SEO solution and content performance marketing platform.
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.
Observations (2)
No build tool detected
A framework (Apple) 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
18 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/evidi.dk)<a href="https://beavercheck.com/sites/evidi.dk"><img src="https://beavercheck.com/badge?url=https%3A%2F%2FEvidi.dk" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2FEvidi.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
2 sprints · 7h total → projected A (90)
Sprint 1: Quick Wins
+4Highest ROI — low effort, high impact
- · HSTS header is missing
- · Soft 404: server returns HTTP 200 for non-existent pages
Sprint 2: Core Fixes
+5Medium effort, high structural impact
- · 4 control(s) without accessible label
- · Content-Security-Policy header is missing
- · 1 render-blocking <script src> tag(s) without async/defer