Skip to content
https://hide-poor-thorough-bluetooth.trycloudflare.com Export & share
Scanned
2026-09-27 15:58 UTC
Worker
🇪🇸 Madrid
Duration
56.00s
Vs prev
—

Global Performance

6/6 locations ✓

High global latency — average 566ms across 6 locations, fastest from Amsterdam (295ms), slowest from Singapore (1335ms). Cloudflare edge cache (DYNAMIC). Cache-Control disables caching (no-store). 2 locations above the 500ms target.

Spain - Madrid
Full audit
355ms
DNS 30ms · TLS 23ms
United Stated - New York
387ms
DNS 8ms · TLS 11ms
United States - Santa Clara
361ms
DNS 5ms · TLS 10ms
Netherlands - Amsterdam
295ms
DNS 11ms · TLS 10ms
Brazil - Sao Paulo
662ms
DNS 7ms · TLS 8ms
Singapore - Singapore
1335ms
DNS 6ms · TLS 10ms
CDN: Cloudflare (DYNAMIC) · Avg TTFB: 566ms · Cache: no-store

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

Your mail setup has problems.

hide-poor-thorough-bluetooth.trycloudflare.com fails 2 mail checks: No DMARC record found, No SPF record found. This is the kind of misconfiguration that sends your mail to spam.

Get a full deliverability audit — €179, 48h →

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

Compressed response missing `Vary` header

Performance issues directly impact user engagement and conversion rates.

Performance › Server Response Intelligence
Warning: 4

Cross-Origin-Embedder-Policy header is missing

COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.

Security › Security Headers
Warning: 5

Cross-Origin-Opener-Policy header is missing

COOP isolates your top-level browsing context from cross-origin windows — without it, popup-based side-channel attacks remain possible.

Security › Security Headers
What fixing these means. Your site is in great shape. The remaining improvements are refinements rather than critical fixes. Your LCP of 2.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.
4 security gaps detected — browsers may warn visitors about your site.
Your LCP is 2.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

$650 investment → $1,405/month returns

Investment
$650
6.5 h · 5 findings
Monthly returns
$1,405
$16,855/yr
Payback
0.5 mo
+2493% Y1
Or — fix only the top 3 findings
$525 → 0.4 mo payback · +3110% 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

5 barrier(s) likely increasing bounce by ~15%.

Barriers
5
5 warn
Bounce delta
+15pp
added vs baseline
Score
85
A
Speed
1
Trust
2
Usability
0
Content
1
Nav
1
  • Page loads in 2.8s
    Every additional 100ms above 2.5s costs conversions — you're 349ms over
    → Target <2.5s LCP: defer non-critical scripts and optimize the hero image
  • 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
  • Content is hard to read
    Graduate-level reading difficulty — limits the addressable audience for product or blog pages
    → Shorten sentences; replace jargon with plain language; target Flesch ease ≥60
  • 1 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

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

Remediation cost

$650 6.5 developer hours at $100/hr
Quick wins
$50 2 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

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

Bounce-Rate Cost

$748 /mo

+15.0pp bounce · ~1,496 lost visitors/mo

CPC: USD 0.50

Bandwidth Waste

$0.08 /mo

1019.9 MB/mo × 0.080 USD/GB

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

93
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.
69
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.26 s

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

2.85 s

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

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

4.28 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.85 s

Desktop

100
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.
69
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.

478 ms

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

558 ms

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

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

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

558 ms

Categories

8
Avg score 90.9

How you compare

Where this site stands against peers running the same stack.

Open Graph · 4211 peers
You 90
·
Avg 76
+14 above average
0 50 100
Accessibility P95Performance P93Sustainability P90Security P89Compliance P81Content P78SEO P70Infrastructure P51

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

Better than 94% of Open Graph sites See full Open Graph benchmark →
Priority Hints · 2150 peers
You 90
·
Avg 77
+13 above average
0 50 100
Accessibility P92Performance P90Sustainability P87Security P86Compliance P80Content P77SEO P68Infrastructure P48

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

Better than 91% of Priority Hints sites See full Priority Hints benchmark →

Technology stack

Open Graph, with Cloudflare CDN

4 technologies detected 2 stack layers 1 with CPE identifier Standard

Stack Architecture

Framework
Open Graph PWA Priority Hints
CDN
Cloudflare

All Detected Technologies (4)

Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.

Categories CDN Website https://www.cloudflare.com Detected by BeaverCheck Evidence Server header in redirect: cloudflare
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Open Graph is a protocol that is used to integrate any web page into the social graph.

Categories Miscellaneous Website https://ogp.me Detected by BeaverCheck

Progressive Web Apps (PWAs) are web apps built and enhanced with modern APIs to deliver enhanced capabilities, reliability, and installability while reaching anyone, anywhere, on any device, all with a single codebase.

Categories Miscellaneous Website https://web.dev/progressive-web-apps/ Detected by BeaverCheck

Priority Hints exposes a mechanism for developers to signal a relative priority for browsers to consider when fetching resources.

Categories Performance Website https://wicg.github.io/priority-hints/ Detected by BeaverCheck

Observations (1)

No build tool detected

A framework (Open Graph) 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%2Fhide-poor-thorough-bluetooth.trycloudflare.com)](https://beavercheck.com/sites/hide-poor-thorough-bluetooth.trycloudflare.com)
<a href="https://beavercheck.com/sites/hide-poor-thorough-bluetooth.trycloudflare.com"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fhide-poor-thorough-bluetooth.trycloudflare.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fhide-poor-thorough-bluetooth.trycloudflare.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 · 6h total → projected A (95)

Sprint 1: Quick Wins

+4

Highest ROI — low effort, high impact

2 findings 0h → A (94)
  • · HSTS header is missing
  • · Cross-Origin-Opener-Policy header is missing

Sprint 2: Core Fixes

+1

Medium effort, high structural impact

3 findings 6h → A (95)
  • · Content-Security-Policy header is missing
  • · Cross-Origin-Embedder-Policy header is missing
  • · Compressed response missing `Vary` header

Send Feedback