Skip to content
Scanned
2026-09-09 16:21 UTC
Worker
🇪🇸 Madrid
Duration
50.00s
Vs prev

Global Performance

6/6 locations

Acceptable global latency — average 457ms across 6 locations, fastest from New York (130ms), slowest from Singapore (819ms). Netlify edge cache ("Netlify Edge"; hit; ttl=31521399). 3 locations above the 500ms target.

Spain - Madrid
Full audit
505ms
DNS 289ms · TLS 189ms
United Stated - New York
130ms
DNS 39ms · TLS 46ms
United States - Santa Clara
359ms
DNS 187ms · TLS 162ms
Netherlands - Amsterdam
515ms
DNS 296ms · TLS 170ms
Brazil - Sao Paulo
411ms
DNS 48ms · TLS 224ms
Singapore - Singapore
819ms
DNS 23ms · TLS 221ms
CDN: Netlify ("Netlify Edge"; hit; ttl=31521399) · Avg TTFB: 457ms · Cache: public,max-age=0,must-revalidate

Audit overview

Compliance and Sustainability need attention; the other 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

Your mail setup has problems.

emmanuelalade.com fails 1 mail check: DMARC policy is none — monitoring only. This is the kind of misconfiguration that sends your mail to spam.

Get a full deliverability audit — €179, 48h →

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 15.0 MB (14.7 MB transferred)

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

Performance › Page Weight Budget
Critical: 3

Soft 404: server returns HTTP 200 for non-existent pages

Soft 404s (HTTP 200 for missing pages) confuse Google — it indexes the 'not found' page as real content and ranks it.

Accessibility › 404 Error Page
Warning: 4

1 publicly-accessible JavaScript source map(s)

Source maps reveal original source code (variable names, comments, file structure) and are shipped to production by mistake almost universally. The standard fix is a one-line build-tool config change.

Security › Source Map Exposure
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 performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 15.7s 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 15.7s — 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

$500 investment → $5,906/month returns + USD 150,000 risk avoided

Investment
$500
5.0 h · 4 findings
Monthly returns
$5,906
$70,876/yr
Payback
0.1 mo
+14075% Y1
Regulatory risk avoided USD 150,000
Or — fix only the top 3 findings
$4000.1 mo payback · +17619% 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.
$100 — 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 ~22%.

Barriers
4
1 crit 3 warn
Bounce delta
+22pp
added vs baseline
Score
81
B
Speed
1
Trust
1
Usability
0
Content
0
Nav
2
  • Page takes 15.7s to load
    Users abandon at ~3s — you're 13.2s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • 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 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
  • 2 broken link(s) on the page
    Clicks land on 404s — trust drops and the session often ends
    → Fix or remove the broken destinations surfaced on the Content tab

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

Remediation cost

$500 5.0 developer hours at $100/hr
Quick wins
$100 2 fixes in ~60 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

$5,906 / month at risk ~$70,876 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

$150,000

ADA Title III
  • Skip navigation link is missing (WCAG 2.4.1)
    ADA Title III: USD 25,000 – USD 150,000

Bounce-Rate Cost

$5,903 /mo

+21.9pp bounce · ~2,194 lost visitors/mo

CPC: USD 2.69

Bandwidth Waste

$3.70 /mo

46309.0 MB/mo × 0.080 USD/GB

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

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

3.45 s

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

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

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

15.68 s

Desktop

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

720 ms

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

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

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

1.76 s

Categories

8
Avg score 80.5

How you compare

Where this site stands against peers running the same stack.

Google Font API · 1216 peers
You 82
·
Avg 75
+7 above average
0 50 100
Compliance P12Security P87Accessibility P87Performance P81Sustainability P22SEO P76Content P69Infrastructure P45

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

Better than 90% of Google Font API sites See full Google Font API benchmark →
HSTS · 3016 peers
You 82
·
Avg 77
At average
0 50 100
Compliance P14Sustainability P16Accessibility P78SEO P75Security P72Performance P70Content P68Infrastructure P36

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

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

Technology stack

Google Font API, with Netlify CDN

8 technologies detected 2 stack layers Complex

Stack Architecture

Framework
Google Font API HSTS Lucide Open Graph Tailwind CSS Zoho Mail
CDN
Netlify Netlify CDN

All Detected Technologies (8)

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
Categories CDN Website https://www.netlify.com Detected by BeaverCheck Evidence x-nf-request-id: 01M23FHMANG7R377FBSY9T6QC3

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

Lucide is an open-source icon library that provides 1000+ vector (svg) files for displaying icons and symbols in digital and non-digital projects.

Categories Font scripts Website https://lucide.dev 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
Categories Framework Website https://tailwindcss.com Detected by BeaverCheck Evidence Found 199 unique Tailwind utility classes in HTML
Categories Email Detected by BeaverCheck Evidence MX record: mx.zoho.com

Observations (2)

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.

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%2Femmanuelalade.com)](https://beavercheck.com/sites/emmanuelalade.com)
<a href="https://beavercheck.com/sites/emmanuelalade.com"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Femmanuelalade.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Femmanuelalade.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 A (90)

Sprint 1: Quick Wins

+5

Highest ROI — low effort, high impact

3 findings 1h → B (87)
  • · Page weighs 15.0 MB (14.7 MB transferred)
  • · Soft 404: server returns HTTP 200 for non-existent pages
  • · 1 publicly-accessible JavaScript source map(s)

Sprint 2: Core Fixes

+3

Medium effort, high structural impact

2 findings 4h → A (90)
  • · Content-Security-Policy header is missing
  • · Cross-Origin-Embedder-Policy header is missing

Send Feedback