Skip to content
Recent Trends
Performance improving ↑
100
TTFB degrading ↓
3.1s
FCP improving ↑
1.1s
LCP improving ↑
1.1s
Scanned
2026-05-11 07:16 UTC
Worker
🇪🇸 Madrid
Duration
34.00s
Vs prev
Improved by +2

Global Performance

6/6 locations

Acceptable global latency — average 295ms across 6 locations, fastest from Santa Clara (14ms), slowest from Madrid (628ms). Netlify in front. 1 location above the 500ms target.

Spain - Madrid
Full audit
628ms
DNS 1ms · TLS 28ms
United Stated - New York
79ms
DNS 4ms · TLS 8ms
Netherlands - Amsterdam
281ms
DNS 2ms · TLS 9ms
United States - Santa Clara
14ms
DNS 5ms · TLS 3ms
Singapore - Singapore
461ms
DNS 4ms · TLS 3ms
Brazil - Sao Paulo
306ms
DNS 6ms · TLS 3ms
CDN: Netlify · Avg TTFB: 295ms · 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

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

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

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: 5

3 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 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.
2 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.
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

$667 investment → $4,062/month returns + USD 157,500 risk avoided

Investment
$667
6.7 h · 4 findings
Monthly returns
$4,062
$48,748/yr
Payback
0.2 mo
+7212% Y1
Regulatory risk avoided USD 157,500
Or — fix only the top 3 findings
$6170.2 mo payback · +7805% 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.
$67 — 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

4 barrier(s) likely increasing bounce by ~13%.

Barriers
4
4 warn
Bounce delta
+13pp
added vs baseline
Score
88
A
Speed
1
Trust
1
Usability
0
Content
1
Nav
1
  • Page loads in 2.8s
    Every additional 100ms above 2.5s costs conversions — you're 306ms over
    → Target <2.5s LCP: defer non-critical scripts and optimize the hero image
  • 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, …)
  • No skip-to-content link
    Keyboard and screen-reader users must tab through the entire header on every page
    → Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

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

Remediation cost

$667 6.7 developer hours at $100/hr
Quick wins
$67 2 fixes in ~40 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

$16,611 / month at risk ~$199,332 / 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 <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

Bounce-Rate Cost

$3,486 /mo

+13.0pp bounce · ~1,296 lost visitors/mo

CPC: USD 2.69

Bandwidth Waste

$0.02 /mo

212.2 MB/mo × 0.080 USD/GB

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

Mobile

90
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
93
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.

2.81 s

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

2.81 s

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.

3.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.81 s

Desktop

98
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
93
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.

689 ms

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

689 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.084

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

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

689 ms

Categories

8
Avg score 84.0

How you compare

Where this site stands against peers running the same stack.

Google Font API · 992 peers
You 83
·
Avg 73
+10 above average
0 50 100
Compliance P2Sustainability P98Performance P97Accessibility P95Security P93SEO P27Infrastructure P57Content P48

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

Better than 98% of Google Font API sites See full Google Font API benchmark →
HSTS · 2418 peers
You 83
·
Avg 75
+8 above average
0 50 100
Compliance P3Sustainability P97Performance P92Accessibility P92Security P83SEO P43Content P57Infrastructure P56

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

Better than 94% of HSTS sites See full HSTS benchmark →

Technology stack

Google Font API, with Netlify CDN

5 technologies detected 2 stack layers Standard

Stack Architecture

Framework
Google Font API HSTS Open Graph
CDN
Netlify Netlify CDN

All Detected Technologies (5)

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: 01KRAY8695WD40JN5ZYGJKEJBK

Google Font API is a web service that supports open-source font files that can be used on your web designs.

Categories Font scripts Website https://fonts.google.com/ Detected by BeaverCheck

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 (Google Font API) 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/a5c1493a-e439-4c7f-bb69-327cd02987fd)
<a href="https://beavercheck.com/results/a5c1493a-e439-4c7f-bb69-327cd02987fd"><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 · 7h total → projected A (92)

Sprint 1: Quick Wins

+4

Highest ROI — low effort, high impact

3 findings 1h → B (87)
  • · No <main> landmark found
  • · No favicon or icon links detected
  • · 3 third-party resources (79% of weight)

Sprint 2: Core Fixes

+5

Medium effort, high structural impact

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

Send Feedback