Skip to content
Scanned
2026-08-03 05:41 UTC
Worker
🇪🇸 Madrid
Duration
47.00s
Vs prev

Global Performance

6/6 locations

Acceptable global latency — average 204ms across 6 locations, fastest from New York (143ms), slowest from Amsterdam (260ms). No CDN detected. Cache-Control header is missing.

Spain - Madrid
Full audit
228ms
DNS 52ms · TLS 19ms
United Stated - New York
143ms
DNS 3ms · TLS 5ms
United States - Santa Clara
177ms
DNS 5ms · TLS 4ms
Brazil - Sao Paulo
192ms
DNS 3ms · TLS 5ms
Singapore - Singapore
224ms
DNS 5ms · TLS 5ms
Netherlands - Amsterdam
260ms
DNS 2ms · TLS 4ms
CDN: No CDN · Avg TTFB: 204ms · 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

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

1 button(s) with no accessible text

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Accessibility › Link & Button Quality
Critical: 4

1 control(s) without accessible label

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Accessibility › Form Accessibility
Critical: 5

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
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.
2 security gaps detected — browsers may warn visitors about your site.
3 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

$800 investment → $16,456/month returns + USD 150,000 risk avoided

Investment
$800
8.0 h · 5 findings
Monthly returns
$16,456
$197,477/yr
Payback
0.0 mo
+24585% Y1
Regulatory risk avoided USD 150,000
Or — fix only the top 3 findings
$6500.0 mo payback · +30281% 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.
$100 — 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

9 barrier(s) likely increasing bounce by ~36%.

Barriers
9
2 crit 7 warn
Bounce delta
+36pp
added vs baseline
Score
59
C
Speed
1
Trust
2
Usability
2
Content
3
Nav
1
  • Page takes 9.0s to load
    Users abandon at ~3s — you're 6.5s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • 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 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
  • 1 form field(s) without a label
    Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes
    → Associate every input with a visible <label for="…">; add autocomplete attributes

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

Remediation cost

$800 8.0 developer hours at $100/hr
Quick wins
$100 2 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

$9,785 / month at risk ~$117,416 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

$150,000

ADA Title III
  • No <nav> landmark found
    ADA Title III: USD 25,000 – USD 150,000
  • Skip navigation link is missing (WCAG 2.4.1)
    ADA Title III: USD 25,000 – USD 150,000
  • No headings found
    ADA Title III: USD 25,000 – USD 150,000

Bounce-Rate Cost

$9,784 /mo

+36.4pp bounce · ~3,637 lost visitors/mo

CPC: USD 2.69

Bandwidth Waste

$0.23 /mo

2848.2 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~285 KB per page load
    Saves $0.23/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

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

6.53 s

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

8.98 s

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

122 ms

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

0.022

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

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

10.17 s

Desktop

81
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.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
61
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.

1.14 s

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

2.91 s

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

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

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

2.91 s

Categories

8
Avg score 80.6

How you compare

Where this site stands against peers running the same stack.

HSTS · 2715 peers
You 81
·
Avg 75
+6 above average
0 50 100
Accessibility P84Security P79Compliance P23Performance P77SEO P24Content P35Sustainability P64Infrastructure P57

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

Better than 83% of HSTS sites See full HSTS benchmark →
HTTP/3 · 1676 peers
You 81
·
Avg 76
At average
0 50 100
Accessibility P81Security P78Compliance P23Performance P70SEO P32Content P39Infrastructure P48Sustainability P49

Top 10% of HTTP/3 sites score 85+ on Compliance; you're at 72 — closing this gap is the highest-leverage improvement.

Better than 80% of HTTP/3 sites See full HTTP/3 benchmark →

Technology stack

HSTS

2 technologies detected 1 stack layers Minimal

Stack Architecture

Framework
HSTS HTTP/3

All Detected Technologies (2)

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

HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.

Categories Miscellaneous Website https://httpwg.org/ Detected by BeaverCheck

Observations (2)

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.

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

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

Sprint 1: Quick Wins

+3

Highest ROI — low effort, high impact

2 findings 1h → B (84)
  • · 1 button(s) with no accessible text
  • · Soft 404: server returns HTTP 200 for non-existent pages

Sprint 2: Core Fixes

+6

Medium effort, high structural impact

3 findings 7h → A (90)
  • · 1 control(s) without accessible label
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found

Send Feedback