Skip to content
Recent Trends
Performance improving ↑
100
TTFB degrading ↓
3.1s
FCP improving ↑
1.1s
LCP improving ↑
1.1s
Scanned
2026-05-11 08:20 UTC
Worker
🇺🇸 Santa Clara
Duration
33.00s
Vs prev
no change

Global Performance

6/6 locations

Acceptable global latency — average 311ms across 6 locations, fastest from New York (89ms), slowest from Singapore (627ms). Netlify in front. 1 location above the 500ms target.

United States - Santa Clara
Full audit
175ms
DNS 8ms · TLS 5ms
Spain - Madrid
339ms
DNS 30ms · TLS 29ms
United Stated - New York
89ms
DNS 5ms · TLS 8ms
Netherlands - Amsterdam
285ms
DNS 12ms · TLS 11ms
Singapore - Singapore
627ms
DNS 7ms · TLS 3ms
Brazil - Sao Paulo
354ms
DNS 5ms · TLS 4ms
CDN: Netlify · Avg TTFB: 311ms · Cache: public,max-age=0,must-revalidate

Audit overview

Compliance 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

No favicon or icon links detected

Without a favicon, your tab shows a blank icon and bookmarks look unbranded — amateur signal in every browser surface.

Accessibility › Favicon & Branding
Warning: 4

88 inline style attribute(s) detected

Inline style attributes force `style-src 'unsafe-inline'` in any CSP -- effectively negating CSP's XSS-mitigation value for stylesheets.

Security › CSP Inline-Style Readiness
Warning: 5

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
What fixing these means. Your site is in great shape. The remaining improvements are refinements rather than critical fixes. 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.
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

$1,150 investment → $1,280/month returns + USD 157,500 risk avoided

Investment
$1,150
11.5 h · 5 findings
Monthly returns
$1,280
$15,359/yr
Payback
0.9 mo
+1236% Y1
Regulatory risk avoided USD 157,500
Or — fix only the top 3 findings
$6500.5 mo payback · +2263% 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

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

Barriers
2
2 warn
Bounce delta
+5pp
added vs baseline
Score
94
A
Speed
0
Trust
1
Usability
0
Content
1
Nav
0
  • 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 structured data
    No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
    → Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

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

Remediation cost

$1,150 11.5 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

$14,405 / month at risk ~$172,859 / 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
  • 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

Bounce-Rate Cost

$1,280 /mo

+4.8pp bounce · ~476 lost visitors/mo

CPC: USD 2.69

Bandwidth Waste

$0.00 /mo

44.2 MB/mo × 0.080 USD/GB

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

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

857 ms

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

893 ms

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

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

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

941 ms

Desktop

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

214 ms

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

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

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

241 ms

Categories

8
Avg score 82.8

How you compare

Where this site stands against peers running the same stack.

HSTS · 2418 peers
You 85
·
Avg 75
+10 above average
0 50 100
Compliance P3Performance P97Accessibility P95Security P92Infrastructure P15Sustainability P70SEO P43Content P57

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

Better than 96% of HSTS sites See full HSTS benchmark →
Open Graph · 3295 peers
You 85
·
Avg 74
+11 above average
0 50 100
Compliance P1Performance P98Security P96Accessibility P96Infrastructure P17Sustainability P75SEO P29Content P38

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

Better than 97% of Open Graph sites See full Open Graph benchmark →

Technology stack

HSTS, with Netlify CDN

4 technologies detected 2 stack layers Standard

Stack Architecture

Framework
HSTS Open Graph
CDN
Netlify Netlify CDN

All Detected Technologies (4)

Netlify providers hosting and server-less backend services for web applications and static websites.

Categories PaaS, CDN Website https://www.netlify.com/ Detected by BeaverCheck Evidence Header: x-nf-request-id, Server: Netlify, Domain: .netlify.app
Categories CDN Website https://www.netlify.com Detected by BeaverCheck Evidence x-nf-request-id: 01KRB1Y84MRJVA0B3MH363DCK0

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

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

Observations (1)

No build tool detected

A framework (HSTS) 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%2Fbenefit-estimator.netlify.app)](https://beavercheck.com/results/05c611fa-ae02-44de-a55e-4a1c81afdfc0)
<a href="https://beavercheck.com/results/05c611fa-ae02-44de-a55e-4a1c81afdfc0"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fbenefit-estimator.netlify.app" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fbenefit-estimator.netlify.app

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 · 12h total → projected A (91)

Sprint 1: Quick Wins

+1

Highest ROI — low effort, high impact

1 findings 0h → B (86)
  • · No favicon or icon links detected

Sprint 2: Core Fixes

+5

Medium effort, high structural impact

4 findings 11h → A (91)
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found
  • · Cross-Origin-Embedder-Policy header is missing
  • · 88 inline style attribute(s) detected

Send Feedback