Skip to content
Scanned
2026-09-09 20:23 UTC
Worker
🇪🇸 Madrid
Duration
1.1m
Vs prev

Global Performance

6/6 locations

Excellent global latency — average 63ms across 6 locations, fastest from Singapore (26ms), slowest from Madrid (100ms). Cloudflare in front. Cache-Control header is missing.

Spain - Madrid
Full audit
100ms
DNS 39ms · TLS 23ms
United Stated - New York
58ms
DNS 33ms · TLS 14ms
Netherlands - Amsterdam
51ms
DNS 24ms · TLS 14ms
United States - Santa Clara
62ms
DNS 39ms · TLS 13ms
Singapore - Singapore
26ms
DNS 11ms · TLS 9ms
Brazil - Sao Paulo
84ms
DNS 69ms · TLS 9ms
CDN: Cloudflare · Avg TTFB: 63ms · Cache: No cache headers

Audit overview

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

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

Page weighs 12.2 MB (5.4 MB transferred)

Informational: total page weight (uncompressed) and bytes actually transferred over the wire.

Performance › Page Weight Budget
Critical: 3

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

is missing width/height — may cause layout shift

Performance issues directly impact user engagement and conversion rates.

Performance › Image Optimization
Warning: 5

189 third-party resources (100% of weight)

Informational: third-party resource count and their share of page weight. High share caps perf gains from frontend optimization.

Performance › Page Weight Inventory
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 22.2s exceeds Google's 2.5s 'Good' threshold and the 3 performance issues below directly contribute to it. Addressing the critical issues below would have the most immediate impact on your user trust.
1 security gap detected — browsers may warn visitors about your site.
Your LCP is 22.2s — fixing the 3 performance criticals could bring it under Google's 2.5s 'Good' threshold.
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

$517 investment → $7,798/month returns + USD 157,500 risk avoided

Investment
$517
5.2 h · 3 findings
Monthly returns
$7,798
$93,572/yr
Payback
0.1 mo
+18011% Y1
Regulatory risk avoided USD 157,500
Or — fix only the top 3 findings
$5170.1 mo payback · +18011% 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.
$17 — 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 ~29%.

Barriers
8
2 crit 6 warn
Bounce delta
+29pp
added vs baseline
Score
62
C
Speed
2
Trust
2
Usability
0
Content
3
Nav
1
  • Page takes 22.2s to load
    Users abandon at ~3s — you're 19.7s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • Page feels frozen for 2.4s
    Clicks on the primary CTA are ignored while JavaScript runs
    → Break up long tasks; defer non-critical JavaScript to post-hydration
  • HSTS is enabled but max-age is short (15552000s)
    First-visit protection is in place, but browsers forget the policy sooner than recommended
    → Raise Strict-Transport-Security max-age to at least 31536000 (1 year)
  • 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

$517 5.2 developer hours at $100/hr
Quick wins
$17 1 fixes in ~10 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,798 / month at risk ~$93,572 / 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 found (page links and common paths checked)
    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,796 /mo

+29.0pp bounce · ~2,898 lost visitors/mo

CPC: USD 2.69

Bandwidth Waste

$1.37 /mo

17108.8 MB/mo × 0.080 USD/GB

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

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

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

22.16 s

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

2.42 s

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

0.084

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

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

32.98 s

Desktop

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

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

2.08 s

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

184 ms

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

0.005

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

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

5.82 s

Categories

8
Avg score 77.9

How you compare

Where this site stands against peers running the same stack.

Apple · 1301 peers
You 79
·
Avg 73
+6 above average
0 50 100
Compliance P1Security P98Accessibility P93SEO P29Performance P65Sustainability P64Content P38Infrastructure P41

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

Better than 90% of Apple sites See full Apple benchmark →
Google Domains · 233 peers
You 79
·
Avg 75
At average
0 50 100
Better than 91% of Google Domains sites See full Google Domains benchmark →

Technology stack

Apple, with Cloudflare CDN

11 technologies detected 2 stack layers 1 with CPE identifier Enterprise

Stack Architecture

Framework
Apple Google Domains Google Search Console Google Workspace HSTS HTTP/3 Microsoft Microsoft 365 Mimecast Tailwind CSS
CDN
Cloudflare

All Detected Technologies (11)

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 →
Categories Analytics Detected by BeaverCheck · Low Evidence TXT record: apple-domain-verification=rFaAtDAi55cu32FO
Categories DNS Detected by BeaverCheck Evidence NS record: ns-cloud-c4.googledomains.com
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=d5r-J1fpGodeeNyQ74KKEZx8fqHFOP_JH8dy8nUDyEk
Categories Email Detected by BeaverCheck Evidence TXT SPF record includes _spf.google.com: v=spf1 include:_spf.google.com include:spf.protection.outlook.com ip4:90.216.131.60 ip4:90.216.131.61 ip4:90.216.131.62 ip4:80.238.1.152 ip4:80.238.1.153 ip4:80.238.1.155 mx include:mail.zendesk.com include:eu._netblocks.mimecast.com -all

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
Categories Analytics Detected by BeaverCheck · Low Evidence TXT record: MS=ms76096908
Categories Email Detected by BeaverCheck Evidence TXT SPF record includes spf.protection.outlook.com: v=spf1 include:_spf.google.com include:spf.protection.outlook.com ip4:90.216.131.60 ip4:90.216.131.61 ip4:90.216.131.62 ip4:80.238.1.152 ip4:80.238.1.153 ip4:80.238.1.155 mx include:mail.zendesk.com include:eu._netblocks.mimecast.com -all
Categories Email Detected by BeaverCheck Evidence MX record: eu-smtp-inbound-2.mimecast.com
Categories Framework Website https://tailwindcss.com Detected by BeaverCheck Evidence Found 16 unique Tailwind utility classes in HTML

Observations (2)

No build tool detected

A framework (Apple) 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.

Complex technology stack detected

11 technologies identified. A complex stack increases maintenance burden and attack surface. Consider whether all components are actively needed.

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%2FOddschecker.com)](https://beavercheck.com/sites/oddschecker.com)
<a href="https://beavercheck.com/sites/oddschecker.com"><img src="https://beavercheck.com/badge?url=https%3A%2F%2FOddschecker.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2FOddschecker.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 · 5h total → projected B (87)

Sprint 1: Quick Wins

+5

Highest ROI — low effort, high impact

3 findings 0h → B (84)
  • · Page weighs 12.2 MB (5.4 MB transferred)
  • · No <main> landmark found
  • · 189 third-party resources (100% of weight)

Sprint 2: Core Fixes

+3

Medium effort, high structural impact

2 findings 5h → B (87)
  • · Content-Security-Policy header is missing
  • · is missing width/height — may cause layout shift

Send Feedback