Skip to content
Scanned
2026-04-22 00:10 UTC
Worker
🇪🇸 Madrid
Duration
1.2m
Vs prev

Audit overview

4 categories need attention: Security, and 3 others.

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

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

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

Cookie 'c2sd-an-auth' is missing the HttpOnly flag

Without HttpOnly, JavaScript can read the cookie — an XSS bug becomes a session-stealing attack.

Security › Cookie Security
Warning: 5

Cookie 'c2sd-an-cookie-verification' is missing the HttpOnly flag

Without HttpOnly, JavaScript can read the cookie — an XSS bug becomes a session-stealing attack.

Security › Cookie Security
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. 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.
4 security gaps detected — browsers may warn visitors about your site.
1 accessibility issue excludes 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

€560 investment → €6,058/month returns + EUR 120,500,000 risk avoided

Investment
€560
7.0 h · 5 findings
Monthly returns
€6.058
€72.697/yr
Payback
0.1 mo
+12882% Y1
Regulatory risk avoided EUR 120.500.000
Or — fix only the top 3 findings
€5200.1 mo payback · +13880% 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.
€80 — 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 ~28%.

Barriers
8
1 crit 7 warn
Bounce delta
+28pp
added vs baseline
Score
69
C
Speed
2
Trust
2
Usability
0
Content
3
Nav
1
  • Page takes 16.1s to load
    Users abandon at ~3s — you're 13.6s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • High main-thread blocking time
    Page is non-interactive for 282ms after first paint
    → Defer third-party scripts and split large bundles
  • 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

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

Remediation cost

€560 7.0 developer hours at €80/hr
Quick wins
€80 3 fixes in ~60 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

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

Compliance Risk

€120.500.000

ePrivacy DirectiveRGPDEAA
  • No privacy policy link detected
    RGPD: EUR 10.000 – EUR 20.000.000
  • Trackers detected but no cookie policy found
    RGPD: EUR 5.000 – EUR 10.000.000
  • Trackers detected but no cookie policy found
    RGPD: EUR 10.000 – EUR 20.000.000

Bounce-Rate Cost

€6.057 /mo

+27.5pp bounce · ~2,753 lost visitors/mo

CPC: EUR 2.20

Bandwidth Waste

€0,73 /mo

9811.0 MB/mo × 0.074 EUR/GB

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

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

11.83 s

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

16.14 s

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

282 ms

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

0.060

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

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

16.14 s

Desktop

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

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

3.06 s

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

44 ms

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

0.015

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

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

3.06 s

Categories

8
Avg score 69.9

How you compare

Where this site stands against peers running the same stack.

Google Search Console · 3818 peers
You 70
·
Avg 73
At average
0 50 100
Content P10SEO P18Infrastructure P18Compliance P18Sustainability P19Accessibility P25Security P57Performance P56

Top 10% of Google Search Console sites score 96+ on Content; you're at 68 — closing this gap is the highest-leverage improvement.

Better than 13% of Google Search Console sites See full Google Search Console benchmark →
HSTS · 2557 peers
You 70
·
Avg 75
At average
0 50 100
Content P10SEO P14Infrastructure P14Sustainability P14Accessibility P20Compliance P23Security P40Performance P46

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

Better than 7% of HSTS sites See full HSTS benchmark →

Technology stack

Google Search Console

2 technologies detected 1 stack layers Minimal

Stack Architecture

Framework
Google Search Console HSTS

All Detected Technologies (2)

Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=Dot44n8XqpQEdQfm-PJLq5ViDbXzK0TkQD44Ii-ar2k

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 (2)

No build tool detected

A framework (Google Search Console) 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%2Fhal.science)](https://beavercheck.com/results/7d005841-0b3a-44a0-b2a7-c99f3dce5c0a)
<a href="https://beavercheck.com/results/7d005841-0b3a-44a0-b2a7-c99f3dce5c0a"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fhal.science" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fhal.science

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 C (77)

Sprint 1: Quick Wins

+4

Highest ROI — low effort, high impact

3 findings 1h → C (74)
  • · Soft 404: server returns HTTP 200 for non-existent pages
  • · Cookie 'c2sd-an-auth' is missing the HttpOnly flag
  • · Cookie 'c2sd-an-cookie-verification' is missing the HttpOnly flag

Sprint 2: Core Fixes

+3

Medium effort, high structural impact

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

Send Feedback