Skip to content
DE · EUR (€) · Estimated Applicable regulations: DSGVO · ePrivacy Directive · EAA Dev cost: €90/hr How jurisdiction is detected
Scanned
2026-08-25 18:26 UTC
Worker
🇪🇸 Madrid
Duration
1.1m
Vs prev

Global Performance

6/6 locations

High global latency — average 1231ms across 6 locations, fastest from New York (713ms), slowest from Singapore (1719ms). No CDN detected. 6 locations above the 500ms target.

Spain - Madrid
Full audit
865ms
DNS 69ms · TLS 70ms
Netherlands - Amsterdam
734ms
DNS 51ms · TLS 35ms
United Stated - New York
713ms
DNS 230ms · TLS 184ms
United States - Santa Clara
1710ms
DNS 353ms · TLS 981ms
Singapore - Singapore
1719ms
DNS 335ms · TLS 946ms
Brazil - Sao Paulo
1647ms
DNS 356ms · TLS 729ms
CDN: No CDN · Avg TTFB: 1231ms · Cache: max-age=600

Audit overview

Content needs attention; the rest of the categories are in good shape.

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

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

Your mail setup has problems.

ladysilvia.eu fails 2 mail checks: No DMARC record found, SPF ends in ?all — provides no enforcement. This is the kind of misconfiguration that sends your mail to spam.

Get a full deliverability audit — €179, 48h →

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

5 link(s) with no accessible text

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Accessibility › Link & Button Quality
Critical: 5

No H1 heading found

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Accessibility › Heading Hierarchy
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. 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.
2 accessibility issues exclude users who rely on assistive technology.

Business case

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

Return on investment

€623 investment → €3,544/month returns + EUR 500,000 risk avoided

Investment
€623
6.9 h · 5 findings
Monthly returns
€3.544
€42.534/yr
Payback
0.2 mo
+6733% Y1
Regulatory risk avoided EUR 500.000
Or — fix only the top 3 findings
€5630.2 mo payback · +7462% 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.
€83 — 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 ~16%.

Barriers
8
8 warn
Bounce delta
+16pp
added vs baseline
Score
76
B
Speed
0
Trust
2
Usability
0
Content
3
Nav
3
  • 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
  • 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
  • No structured data
    No 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, …)
  • Content is hard to read
    Graduate-level reading difficulty — limits the addressable audience for product or blog pages
    → Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

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

Remediation cost

€623 6.9 developer hours at €90/hr
Quick wins
€83 3 fixes in ~55 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

Warning:Cost of inaction

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

Compliance Risk

€500.000

EAA
  • Skip navigation link is missing (WCAG 2.4.1)
    EAA: EUR 1.000 – EUR 500.000
  • No H1 heading found
    EAA: EUR 1.000 – EUR 500.000
  • 1 heading(s) are over 120 characters -- likely a misformatted paragraph
    EAA: EUR 1.000 – EUR 500.000

Bounce-Rate Cost

€3.544 /mo

+16.1pp bounce · ~1,611 lost visitors/mo

CPC: EUR 2.20

Bandwidth Waste

€0,38 /mo

5153.8 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~515 KB per page load
    Saves €0,38/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 5 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

0
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
96
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
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.

7.66 s

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

0 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.000

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

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

0 ms

Desktop

98
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
96
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
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.

578 ms

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

1.09 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.001

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

933 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.10 s

Categories

8
Avg score 81.2

How you compare

Where this site stands against peers running the same stack.

CentOS · 13 peers
You 83
·
Avg 72
+11 above average
0 50 100
Better than 92% of CentOS sites See full CentOS benchmark →
OpenSSL · 48 peers
You 83
·
Avg 72
+11 above average
0 50 100
Better than 97% of OpenSSL sites See full OpenSSL benchmark →

Technology stack

CentOS, on Apache/PHP, hosted on Apache HTTP Server

5 technologies detected 4 stack layers 4 with CPE identifier Standard

Stack Architecture

Framework
CentOS OpenSSL 1.0.2k
Runtime
PHP 8.3.2
Server
Apache 2.4.6
Hosting
Apache HTTP Server 2.4.6

All Detected Technologies (5)

Categories Server Website https://httpd.apache.org Detected by BeaverCheck Evidence Server header: Apache/2.4.6 (CentOS) PHP/8.3.2 OpenSSL/1.0.2k-fips

Apache is a free and open-source cross-platform web server software.

Categories Web servers Website https://httpd.apache.org/ Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

PHP is a general-purpose scripting language used for web development.

Categories Programming languages Website https://php.net Detected by BeaverCheck Evidence x-powered-by: PHP/8.3.2
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

CentOS is a Linux distribution that provides a free, community-supported computing platform functionally compatible with its upstream source, Red Hat Enterprise Linux (RHEL).

Categories Operating systems Website https://centos.org Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

OpenSSL is a software library for applications that secure communications over computer networks against eavesdropping or need to identify the party at the other end.

Categories Web server extensions Website https://openssl.org Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Observations (3)

Server version exposed in headers

The Server header reveals 'Apache 2.4.6'. Exposing exact server versions helps attackers target known vulnerabilities. Consider configuring your server to hide version information.

→ Security

Runtime exposed via X-Powered-By header

The X-Powered-By header reveals 'PHP 8.3.2'. Remove this header in production to reduce information leakage.

→ Security

No build tool detected

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

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%2Fladysilvia.eu)](https://beavercheck.com/sites/ladysilvia.eu)
<a href="https://beavercheck.com/sites/ladysilvia.eu"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fladysilvia.eu" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fladysilvia.eu

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

Sprint 1: Quick Wins

+6

Highest ROI — low effort, high impact

3 findings 1h → B (89)
  • · No H1 heading found
  • · HSTS header is missing
  • · 5 link(s) with no accessible text

Sprint 2: Core Fixes

+1

Medium effort, high structural impact

2 findings 6h → A (90)
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found

Send Feedback