Skip to content
Scanned
2026-04-22 23:04 UTC
Worker
🇪🇸 Madrid
Duration
38.00s
Vs prev

Audit overview

3 categories need attention: Security, and 2 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

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

No favicon or icon links detected

Without a favicon, your tab shows a blank icon and bookmarks look unbranded — amateur signal in every browser surface.

Accessibility › Favicon & Branding
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.
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

$692 investment → $11,122/month returns + USD 157,500 risk avoided

Investment
$692
6.9 h · 5 findings
Monthly returns
$11,122
$133,458/yr
Payback
0.1 mo
+19195% Y1
Regulatory risk avoided USD 157,500
Or — fix only the top 3 findings
$6250.1 mo payback · +21253% 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.
$92 — 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 11.6s to load
    Users abandon at ~3s — you're 9.1s 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 507ms 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

$692 6.9 developer hours at $100/hr
Quick wins
$92 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

$7,407 / month at risk ~$88,883 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • No privacy policy link detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no privacy policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

Bounce-Rate Cost

$7,407 /mo

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

CPC: USD 2.69

Bandwidth Waste

$0.38 /mo

4784.3 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~478 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

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

4.07 s

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

11.59 s

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

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

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

11.61 s

Desktop

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

982 ms

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

1.50 s

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

30 ms

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

0.020

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

1.42 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.50 s

Categories

8
Avg score 70.4

How you compare

Where this site stands against peers running the same stack.

Amazon ELB · 174 peers
You 70
·
Avg 71
At average
0 50 100
Better than 31% of Amazon ELB sites See full Amazon ELB benchmark →
Amazon Route 53 · 1012 peers
You 70
·
Avg 72
At average
0 50 100
SEO P8Content P9Accessibility P14Compliance P17Infrastructure P21Performance P74Sustainability P63Security P46

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

Better than 14% of Amazon Route 53 sites See full Amazon Route 53 benchmark →

Technology stack

Amazon ELB, hosted on Amazon Web Services, with Cloudflare CDN

7 technologies detected 3 stack layers Complex

Stack Architecture

Framework
Amazon ELB Amazon Route 53 Facebook Microsoft Proofpoint
CDN
Cloudflare
Hosting
Amazon Web Services

All Detected Technologies (7)

Categories CDN Detected by BeaverCheck Evidence Server header in redirect: cloudflare

Amazon Web Services (AWS) is a comprehensive cloud services platform offering compute power, database storage, content delivery and other functionality.

Categories PaaS Website https://aws.amazon.com/ Detected by BeaverCheck

AWS ELB is a network load balancer service provided by Amazon Web Services for distributing traffic across multiple targets, such as Amazon EC2 instances, containers, IP addresses, and Lambda functions.

Categories Load balancers Website https://aws.amazon.com/elasticloadbalancing/ Detected by BeaverCheck
Categories DNS Detected by BeaverCheck Evidence NS record: ns-483.awsdns-60.com
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: facebook-domain-verification=127ugsc6ryh3k2fnfbey7pe4s3la7h
Categories Analytics Detected by BeaverCheck · Low Evidence TXT record: MS=ms87452117
Categories Email Detected by BeaverCheck Evidence MX record: mxa-00363202.gslb.pphosted.com

Observations (1)

No build tool detected

A framework (Amazon ELB) 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%2Fsncf.com)](https://beavercheck.com/results/07dade66-b1a7-4253-81f4-1a609b4b16ca)
<a href="https://beavercheck.com/results/07dade66-b1a7-4253-81f4-1a609b4b16ca"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fsncf.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fsncf.com

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

Sprint 1: Quick Wins

+5

Highest ROI — low effort, high impact

3 findings 1h → C (75)
  • · No <main> landmark found
  • · HSTS header is missing
  • · No favicon or icon links detected

Sprint 2: Core Fixes

+4

Medium effort, high structural impact

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

Send Feedback