Skip to content
FR · EUR (€) · Estimated Applicable regulations: RGPD · ePrivacy Directive · EAA Dev cost: €80/hr How jurisdiction is detected
Scanned
2026-04-07 20:42 UTC
Worker
🇪🇸 Madrid
Duration
1.1m
Vs prev

Audit overview

4 categories need attention: Accessibility, and 3 others.

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

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: 3

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
Critical: 4

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.

Accessibility › 404 Error Page
Warning: 5

is missing width/height — may cause layout shift

Performance issues directly impact user engagement and conversion rates.

Performance › Image Optimization
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 15.1s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.
2 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.
Your LCP is 15.1s — 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

€693 investment → €8,196/month returns + EUR 20,500,000 risk avoided

Investment
€693
8.7 h · 5 findings
Monthly returns
€8.196
€98.354/yr
Payback
0.1 mo
+14086% Y1
Regulatory risk avoided EUR 20.500.000
Or — fix only the top 3 findings
€4930.1 mo payback · +19837% 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.
€53 — 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 ~37%.

Barriers
8
3 crit 5 warn
Bounce delta
+37pp
added vs baseline
Score
55
C
Speed
2
Trust
1
Usability
1
Content
3
Nav
1
  • Page takes 15.1s to load
    Users abandon at ~3s — you're 12.6s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • Page feels frozen for 1.2s
    Clicks on the primary CTA are ignored while JavaScript runs
    → Break up long tasks; defer non-critical JavaScript to post-hydration
  • No viewport meta tag
    Mobile browsers render at desktop width and shrink — text unreadable, tap targets miniature
    → Add <meta name="viewport" content="width=device-width, initial-scale=1">
  • 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

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

Remediation cost

€693 8.7 developer hours at €80/hr
Quick wins
€53 2 fixes in ~40 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

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

Compliance Risk

€20.500.000

RGPDEAA
  • No privacy policy link detected
    RGPD: EUR 10.000 – EUR 20.000.000
  • Privacy Policy not detected
    RGPD: EUR 10.000 – EUR 20.000.000
  • No <main> landmark found
    EAA: EUR 1.000 – EUR 500.000

Bounce-Rate Cost

€8.195 /mo

+37.3pp bounce · ~3,725 lost visitors/mo

CPC: EUR 2.20

Bandwidth Waste

€0,68 /mo

9240.7 MB/mo × 0.074 EUR/GB

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

31
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
71
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.
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.

12.72 s

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

15.06 s

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

1.24 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.011

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

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

20.00 s

Desktop

61
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
76
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.
83
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.

2.46 s

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

4.35 s

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

132 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.032

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

2.60 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.35 s

Categories

8
Avg score 68.4

How you compare

Where this site stands against peers running the same stack.

HSTS · 2603 peers
You 70
·
Avg 75
At average
0 50 100
Infrastructure P6SEO P8Content P10Sustainability P10Compliance P12Accessibility P15Performance P36Security P63

Top 10% of HSTS sites score 95+ on Infrastructure; you're at 80 — closing this gap is the highest-leverage improvement.

Better than 7% of HSTS sites See full HSTS benchmark →
Apache · 460 peers
You 70
·
Avg 73
At average
0 50 100
SEO P5Compliance P15Infrastructure P16Security P83Sustainability P19Accessibility P20Content P24Performance P35

Top 10% of Apache sites score 95+ on SEO; you're at 74 — closing this gap is the highest-leverage improvement.

Better than 13% of Apache sites See full Apache benchmark →

Technology stack

HSTS, on Apache, hosted on Apache HTTP Server

3 technologies detected 3 stack layers 1 with CPE identifier Standard

Stack Architecture

Framework
HSTS
Server
Apache
Hosting
Apache HTTP Server

All Detected Technologies (3)

Categories Server Website https://httpd.apache.org Detected by BeaverCheck Evidence Server header: Apache

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 →

HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.

Categories Security Website https://www.rfc-editor.org/rfc/rfc6797#section-6.1 Detected by BeaverCheck

Observations (1)

No build tool detected

A framework (HSTS) 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%2Fwww.colissimo.fr)](https://beavercheck.com/results/bd0fa783-4f02-156f-2aed-bb4684b3141b)
<a href="https://beavercheck.com/results/bd0fa783-4f02-156f-2aed-bb4684b3141b"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.colissimo.fr" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.colissimo.fr

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 · 9h total → projected C (79)

Sprint 1: Quick Wins

+3

Highest ROI — low effort, high impact

2 findings 1h → C (73)
  • · No <main> landmark found
  • · Soft 404: server returns HTTP 200 for non-existent pages

Sprint 2: Core Fixes

+6

Medium effort, high structural impact

3 findings 8h → C (79)
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found
  • · is missing width/height — may cause layout shift

Send Feedback