Skip to content
Recent Trends
Performance stable →
56
TTFB stable →
11ms
FCP stable →
10.2s
LCP stable →
10.3s
Scanned
2026-05-10 11:24 UTC
Worker
🇺🇸 Santa Clara
Duration
2.1m
Vs prev
Declined by -4

Global Performance

6/6 locations

Excellent global latency — average 15ms across 6 locations, fastest from Singapore (10ms), slowest from Madrid (25ms). Varnish in front.

United States - Santa Clara
Full audit
15ms
DNS 4ms · TLS 5ms
Spain - Madrid
25ms
DNS 21ms · TLS 2ms
Netherlands - Amsterdam
15ms
DNS 4ms · TLS 7ms
United Stated - New York
12ms
DNS 3ms · TLS 4ms
Brazil - Sao Paulo
13ms
DNS 3ms · TLS 5ms
Singapore - Singapore
10ms
DNS 3ms · TLS 3ms
CDN: Varnish · Avg TTFB: 15ms · Cache: max-age=3600

Audit overview

Compliance and Sustainability need attention; the other categories are in good shape.

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

Page body has only 144 chars of text -- likely empty / placeholder

Security gaps expose your site and users to attacks, eroding trust.

Security › Empty Page Detection
Critical: 4

Page weighs 11.7 MB (6.9 MB transferred)

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

Performance › Page Weight Budget
Critical: 5

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
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 7.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.
3 security gaps detected — browsers may warn visitors about your site.
Your LCP is 7.8s — fixing the 1 performance critical 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

$800 investment → $16,199/month returns + USD 157,500 risk avoided

Investment
$800
8.0 h · 4 findings
Monthly returns
$16,199
$194,387/yr
Payback
0.0 mo
+24198% Y1
Regulatory risk avoided USD 157,500
Or — fix only the top 3 findings
$6500.0 mo payback · +29806% 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

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

Barriers
9
3 crit 6 warn
Bounce delta
+38pp
added vs baseline
Score
52
D
Speed
2
Trust
1
Usability
2
Content
3
Nav
1
  • Page takes 7.8s to load
    Users abandon at ~3s — you're 5.3s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • Page feels frozen for 3.8s
    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
  • Layout shifts during page load
    Content movement causes mis-clicks on CTAs and form fields
    → Add width/height to images; reserve space for late-loading embeds

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

Remediation cost

$800 8.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

Cost of inaction

$23,474 / month at risk ~$281,687 / 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
  • Privacy Policy not detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • No <main> landmark found
    ADA Title III: USD 25,000 – USD 150,000
  • 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
  • 1 image(s) missing alt attribute
    ADA Title III: USD 25,000 – USD 150,000
  • Missing <html lang> attribute (WCAG 3.1.1)
    ADA Title III: USD 25,000 – USD 150,000

Bounce-Rate Cost

$10,347 /mo

+38.5pp bounce · ~3,847 lost visitors/mo

CPC: USD 2.69

Bandwidth Waste

$1.73 /mo

21677.1 MB/mo × 0.080 USD/GB

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

36
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.
92
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.

2.15 s

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

7.77 s

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

3.77 s

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

0.108

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

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

21.32 s

Desktop

60
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
71
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
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.

569 ms

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

1.74 s

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

779 ms

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

0.002

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

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

4.09 s

Categories

8
Avg score 72.2

How you compare

Where this site stands against peers running the same stack.

Amazon Route 53 · 1000 peers
You 76
·
Avg 72
At average
0 50 100
Compliance P1Security P99Infrastructure P2SEO P7Accessibility P93Content P28Performance P71Sustainability P30

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

Better than 83% of Amazon Route 53 sites See full Amazon Route 53 benchmark →
Apple · 1257 peers
You 76
·
Avg 73
At average
0 50 100
Compliance P1Security P99Infrastructure P3Accessibility P90SEO P12Sustainability P23Performance P70Content P34

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

Better than 77% of Apple sites See full Apple benchmark →

Technology stack

Amazon Route 53

8 technologies detected 1 stack layers 1 with CPE identifier Complex

Stack Architecture

Framework
Amazon Route 53 Apple Google Search Console Google Workspace HSTS Microsoft Tailwind CSS Varnish

All Detected Technologies (8)

Categories DNS Detected by BeaverCheck Evidence NS record: ns-1029.awsdns-00.org
Categories Analytics Detected by BeaverCheck · Low Evidence TXT record: apple-domain-verification=qC3rSSKrh10DoMI7
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=0uv13-wxlHK8FFKaUpgzyrVmL1YdNYW6v3PupLdw3JI
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=ms71041902
Categories Framework Website https://tailwindcss.com Detected by BeaverCheck Evidence Found 13 unique Tailwind utility classes in HTML

Varnish is a reverse caching proxy.

Categories Caching Website https://www.varnish-cache.org Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Observations (2)

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.

Complex technology stack detected

8 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%2Freddit.com)](https://beavercheck.com/results/a026b2ce-fca6-49b5-ac34-b55733b69331)
<a href="https://beavercheck.com/results/a026b2ce-fca6-49b5-ac34-b55733b69331"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Freddit.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Freddit.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 · 8h total → projected B (83)

Sprint 1: Quick Wins

+5

Highest ROI — low effort, high impact

2 findings 0h → B (81)
  • · Page weighs 11.7 MB (6.9 MB transferred)
  • · Page body has only 144 chars of text -- likely empty / placeholder

Sprint 2: Core Fixes

+2

Medium effort, high structural impact

3 findings 8h → B (83)
  • · 1 image(s) missing alt attribute
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found

Send Feedback