Skip to content
Recent Trends
Performance stable →
50
TTFB stable →
24ms
FCP stable →
2.1s
LCP stable →
16.8s
Scanned
2026-06-06 18:18 UTC
Worker
🇪🇸 Madrid
Duration
34.00s
Vs prev
Improved by +8

Global Performance

6/6 locations

Excellent global latency — average 15ms across 6 locations, fastest from Sao Paulo (10ms), slowest from Madrid (24ms). No CDN detected.

Spain - Madrid
Full audit
24ms
DNS 19ms · TLS 4ms
United States - Santa Clara
19ms
DNS 5ms · TLS 6ms
United Stated - New York
10ms
DNS 4ms · TLS 4ms
Singapore - Singapore
10ms
DNS 2ms · TLS 5ms
Brazil - Sao Paulo
10ms
DNS 3ms · TLS 5ms
Netherlands - Amsterdam
19ms
DNS 4ms · TLS 10ms
CDN: No CDN · Avg TTFB: 15ms · Cache: max-age=3600

Audit overview

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

Fix Priority Matrix

5 findings

Quick Wins

1

High impact, low effort — start here.

Strategic

4

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 image(s) missing alt attribute

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Accessibility › Alt Text Quality
Critical: 4

2 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
Warning: 5

3 render-blocking <script src> tag(s) without async/defer

Performance issues directly impact user engagement and conversion rates.

Performance › JavaScript Blocking
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 16.8s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. 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 16.8s — 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

$1,000 investment → $8,665/month returns + USD 157,500 risk avoided

Investment
$1,000
10.0 h · 5 findings
Monthly returns
$8,665
$103,982/yr
Payback
0.1 mo
+10298% Y1
Regulatory risk avoided USD 157,500
Or — fix only the top 3 findings
$7500.1 mo payback · +13764% 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.
$50 — 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 ~32%.

Barriers
8
3 crit 5 warn
Bounce delta
+32pp
added vs baseline
Score
55
C
Speed
2
Trust
1
Usability
0
Content
3
Nav
2
  • Page takes 16.8s to load
    Users abandon at ~3s — you're 14.3s 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
  • 8 broken link(s) on the page
    Clicks land on 404s — trust drops and the session often ends
    → Fix or remove the broken destinations surfaced on the Content tab
  • 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

$1,000 10.0 developer hours at $100/hr
Quick wins
$50 1 fixes in ~30 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,665 / month at risk ~$103,982 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • Privacy Policy not detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • 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

Bounce-Rate Cost

$8,664 /mo

+32.2pp bounce · ~3,221 lost visitors/mo

CPC: USD 2.69

Bandwidth Waste

$0.91 /mo

11396.7 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~1.1 MB per page load
    Saves $0.91/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

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

2.11 s

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

16.76 s

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

1.15 s

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.

2.30 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.80 s

Desktop

78
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.
88
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.

462 ms

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

2.48 s

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

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

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

2.49 s

Categories

8
Avg score 76.9

How you compare

Where this site stands against peers running the same stack.

core-js · 1582 peers
You 79
·
Avg 72
+7 above average
0 50 100
Content P2Security P97Accessibility P97Compliance P12SEO P16Infrastructure P82Performance P71Sustainability P56

Top 10% of core-js sites score 95+ on Content; you're at 58 — closing this gap is the highest-leverage improvement.

Better than 93% of core-js sites See full core-js benchmark →
Google Search Console · 3817 peers
You 79
·
Avg 73
+6 above average
0 50 100
Content P1Accessibility P96Security P93Compliance P16Infrastructure P78SEO P33Sustainability P42Performance P56

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

Better than 87% of Google Search Console sites See full Google Search Console benchmark →

Technology stack

Google Search Console

5 technologies detected 2 stack layers Standard

Stack Architecture

Analytics
Apple Sign-in
Framework
Google Search Console HSTS Loadable-Components core-js 3.47.0

All Detected Technologies (5)

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

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

Loadable-Components is a library to solve the React code-splitting client-side and server-side.

Categories JavaScript libraries Website https://github.com/gregberge/loadable-components Detected by BeaverCheck

core-js is a modular standard library for JavaScript, with polyfills for cutting-edge ECMAScript features.

Categories JavaScript libraries Website https://github.com/zloirock/core-js Detected by BeaverCheck

Apple Sign-in is based on OAuth 2.0 and OpenID Connect, and provides a privacy-friendly way for users to sign in to websites and apps.

Categories Authentication Website https://developer.apple.com/sign-in-with-apple/ Detected by BeaverCheck

Observations (1)

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.

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%2Ficloud.com)](https://beavercheck.com/results/190967a6-4bf7-4cb1-9724-4956b8c1966d)
<a href="https://beavercheck.com/results/190967a6-4bf7-4cb1-9724-4956b8c1966d"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ficloud.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Ficloud.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 · 10h total → projected B (88)

Sprint 1: Quick Wins

+1

Highest ROI — low effort, high impact

1 findings 0h → B (80)
  • · 2 button(s) with no accessible text

Sprint 2: Core Fixes

+8

Medium effort, high structural impact

4 findings 10h → B (88)
  • · 1 image(s) missing alt attribute
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found
  • · 3 render-blocking <script src> tag(s) without async/defer

Send Feedback