Skip to content
DE · EUR (€) · Estimated Applicable regulations: DSGVO · ePrivacy Directive · EAA Dev cost: €90/hr How jurisdiction is detected
Scanned
2026-05-11 04:58 UTC
Worker
🇪🇸 Madrid
Duration
34.00s
Vs prev

Global Performance

6/6 locations

Acceptable global latency — average 432ms across 6 locations, fastest from Amsterdam (49ms), slowest from Singapore (959ms). No CDN detected. Cache-Control header is missing. 3 locations above the 500ms target.

Spain - Madrid
Full audit
139ms
DNS 37ms · TLS 35ms
United Stated - New York
281ms
DNS 3ms · TLS 94ms
Netherlands - Amsterdam
49ms
DNS 3ms · TLS 17ms
United States - Santa Clara
523ms
DNS 45ms · TLS 160ms
Singapore - Singapore
959ms
DNS 429ms · TLS 179ms
Brazil - Sao Paulo
639ms
DNS 3ms · TLS 213ms
CDN: No CDN · Avg TTFB: 432ms · Cache: No cache headers

Audit overview

All categories sit comfortably above the 70 threshold; this is a clean audit.

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Screenshots

DESKTOP + MOBILE
Desktop
Desktop screenshot
Mobile
Mobile screenshot

Top Priorities (5)

Sorted by impact
Critical: 1

Content-Security-Policy header is missing

Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.

Security › Security Headers
Critical: 2

HSTS header is missing

Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.

Security › Security Headers
Critical: 3

No Content-Security-Policy header found

Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.

Security › Content Security Policy
Critical: 4

No <main> landmark found

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Accessibility › Landmark Structure
Warning: 5

1 render-blocking <script src> tag(s) without async/defer

Performance issues directly impact user engagement and conversion rates.

Performance › JavaScript Blocking
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 4.2s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.
3 security gaps detected — browsers may warn visitors about your site.
1 accessibility issue excludes users who rely on assistive technology.
Your LCP is 4.2s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Business case

What fixing the audit's findings is worth -- and what ignoring them keeps costing.

Return on investment

€758 investment → €8,484/month returns + EUR 500,000 risk avoided

Investment
€758
8.4 h · 5 findings
Monthly returns
€8,484
€101,806/yr
Payback
0.1 mo
+13340% Y1
Regulatory risk avoided EUR 500,000
Or — fix only the top 3 findings
€5630.1 mo payback · +17999% Y1
Optimistic scenario assuming the top 3 capture most of the upside. Real-world recovery typically falls between this projection and the full-fix ROI above.
€38 — in quick wins — start here for the fastest payback

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 ~27%.

Barriers
8
1 crit 7 warn
Bounce delta
+27pp
added vs baseline
Score
69
C
Speed
1
Trust
2
Usability
1
Content
3
Nav
1
  • Page takes 4.2s to load
    Users abandon at ~3s — you're 1.7s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • No HSTS header
    Returning visitors are briefly exposed to downgrade attacks on first request
    → Set Strict-Transport-Security: max-age=31536000; includeSubDomains
  • No Content-Security-Policy header
    Higher XSS blast radius — one compromised script can exfiltrate the checkout form
    → Ship a reporting-only CSP first, then enforce once violations are clean
  • Viewport disables user zoom
    Visitors with low vision can't read the page — and some jurisdictions treat this as a legal risk
    → Remove user-scalable=no; drop maximum-scale if it's below 2
  • No Open Graph tags
    Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
    → Add og:title, og:description, og:image, og:url to the page head

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Remediation cost

€758 8.4 developer hours at €90/hr
Quick wins
€38 2 fixes in ~25 minutes

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.

/hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

Cost of inaction

€47,557 / month at risk ~€570,679 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

€500,000

EAA
  • No <main> landmark found
    EAA: EUR 1,000 – EUR 500,000
  • No <nav> landmark found
    EAA: 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,890 /mo

+26.8pp bounce · ~2,677 lost visitors/mo

CPC: EUR 2.20

Bandwidth Waste

€0.09 /mo

1255.1 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~126 KB per page load
    Saves €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.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

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

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Lighthouse

Mobile

75
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
86
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
50
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

3.92 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

4.21 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

12 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.

4.89 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.

4.21 s

Desktop

99
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
86
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
50
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

581 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

791 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.008

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

644 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.

791 ms

Categories

8
Avg score 82.9

How you compare

Where this site stands against peers running the same stack.

Onsen UI · 65 peers
You 84
·
Avg 73
+11 above average
0 50 100
Better than 98% of Onsen UI sites See full Onsen UI benchmark →
Nginx · 956 peers
You 84
·
Avg 74
+10 above average
0 50 100
Security P91Accessibility P91Compliance P11Performance P81Sustainability P78Content P29SEO P67Infrastructure P55

Top 10% of Nginx sites score 86+ on Compliance; you're at 70 — closing this gap is the highest-leverage improvement.

Better than 92% of Nginx sites See full Nginx benchmark →

Technology stack

Onsen UI, with Nginx CDN

2 technologies detected 2 stack layers 1 with CPE identifier Minimal

Stack Architecture

Framework
Onsen UI
CDN
Nginx

All Detected Technologies (2)

Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.

Categories Web servers, Reverse proxies Website https://nginx.org/en Detected by BeaverCheck Evidence Server header: nginx
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Onsen UI is an open-source HTML5 hybrid app framework offering mobile UI components for PhoneGap and Cordova development.

Categories Mobile frameworks Website https://onsen.io Detected by BeaverCheck

Observations (2)

No build tool detected

A framework (Onsen UI) 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.

Minimal technology footprint

Only 2 technologies detected. This suggests a simple setup with minimal dependencies — excellent for performance and security.

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.

BeaverCheck badge

This badge auto-updates with your latest scan result.

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.golem.de)](https://beavercheck.com/results/70f919be-686e-449d-8c12-90c71bf98b10)
<a href="https://beavercheck.com/results/70f919be-686e-449d-8c12-90c71bf98b10"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.golem.de" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.golem.de

Export & share

Download the audit, share with your team, or grab a fix plan ready to copy into your tracker.

Share

Copies markdown to clipboard

Export
Download Markdown Report Download JSON

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 · 8h total → projected A (91)

Sprint 1: Quick Wins

+4

Highest ROI — low effort, high impact

2 findings 0h → B (88)
  • · No <main> landmark found
  • · HSTS header is missing

Sprint 2: Core Fixes

+3

Medium effort, high structural impact

3 findings 8h → A (91)
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found
  • · 1 render-blocking <script src> tag(s) without async/defer

Send Feedback