Skip to content
Scanned
2026-04-22 23:59 UTC
Worker
🇳🇱 Amsterdam
Duration
44.00s
Vs prev

Audit overview

5 categories need attention: Performance, and 4 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
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

Page weighs 11.0 MB (6.8 MB transferred)

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

Performance › Page Weight Budget
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
Warning: 5

83 third-party resources (79% 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 29.6s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute 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.
Your LCP is 29.6s — fixing the 2 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

$617 investment → $10,023/month returns + USD 157,500 risk avoided

Investment
$617
6.2 h · 3 findings
Monthly returns
$10,023
$120,271/yr
Payback
0.1 mo
+19403% Y1
Regulatory risk avoided USD 157,500
Or — fix only the top 3 findings
$6170.1 mo payback · +19403% 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 ~37%.

Barriers
8
3 crit 5 warn
Bounce delta
+37pp
added vs baseline
Score
55
C
Speed
2
Trust
1
Usability
1
Content
3
Nav
1
  • Page takes 29.6s to load
    Users abandon at ~3s — you're 27.1s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • Page feels frozen for 2.5s
    Clicks on the primary CTA are ignored while JavaScript runs
    → Break up long tasks; defer non-critical JavaScript to post-hydration
  • 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 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

$617 6.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

$10,023 / month at risk ~$120,271 / 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

$10,021 /mo

+37.3pp bounce · ~3,725 lost visitors/mo

CPC: USD 2.69

Bandwidth Waste

$1.72 /mo

21537.5 MB/mo × 0.080 USD/GB

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

Categories

8
Avg score 69.4

How you compare

Where this site stands against peers running the same stack.

Amazon Route 53 · 1011 peers
You 71
·
Avg 72
At average
0 50 100
Compliance P3SEO P5Content P9Infrastructure P10Security P87Accessibility P85Sustainability P21Performance P32

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

Better than 23% of Amazon Route 53 sites See full Amazon Route 53 benchmark →
Facebook · 1418 peers
You 71
·
Avg 73
At average
0 50 100
Compliance P2Content P7SEO P9Infrastructure P10Security P85Sustainability P16Accessibility P81Performance P31

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

Better than 22% of Facebook sites See full Facebook benchmark →

Technology stack

Amazon Route 53

7 technologies detected 1 stack layers Complex

Stack Architecture

Framework
Amazon Route 53 Facebook Google Search Console Google Workspace HSTS Microsoft Next.js

All Detected Technologies (7)

Categories DNS Detected by BeaverCheck Evidence NS record: ns-1496.awsdns-59.org
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: facebook-domain-verification=2olb7r30vjw80adllzwfvlvh6owjtv
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=c-hsNjXZFadvLgN6RawQBiDbjsKbJJO1WEheFvMlljo
Categories Email Detected by BeaverCheck Evidence MX record: aspmx.l.google.com

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
Categories Analytics Detected by BeaverCheck · Low Evidence TXT record: MS=ms97368111
Categories Framework Detected by BeaverCheck Evidence X-Powered-By: Next.js in redirect

Observations (2)

Next.js application detected

Next.js provides server-side rendering (SSR) and static generation (SSG) for React. The Performance tab shows how effectively the application leverages these features.

No build tool detected

A framework (Amazon Route 53) 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%2Fmubi.com)](https://beavercheck.com/results/a250d9fe-d519-4f62-a981-4f3bbb35ec62)
<a href="https://beavercheck.com/results/a250d9fe-d519-4f62-a981-4f3bbb35ec62"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fmubi.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fmubi.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 B (81)

Sprint 1: Quick Wins

+5

Highest ROI — low effort, high impact

3 findings 0h → C (76)
  • · Page weighs 11.0 MB (6.8 MB transferred)
  • · No <main> landmark found
  • · 83 third-party resources (79% of weight)

Sprint 2: Core Fixes

+5

Medium effort, high structural impact

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

Send Feedback