Skip to content
https://fernandolaserna.com/prueba6/index.html Export & share
Scanned
2026-06-24 12:17 UTC
Worker
🇺🇸 New York
Duration
1.1m
Vs prev

Global Performance

6/6 locations

High global latency — average 522ms across 6 locations, fastest from Madrid (45ms), slowest from Sao Paulo (949ms). No CDN detected. Cache-Control header is missing. 3 locations above the 500ms target.

United Stated - New York
Full audit
432ms
DNS 164ms · TLS 91ms
Netherlands - Amsterdam
104ms
DNS 22ms · TLS 29ms
United States - Santa Clara
758ms
DNS 309ms · TLS 151ms
Singapore - Singapore
844ms
DNS 373ms · TLS 160ms
Brazil - Sao Paulo
949ms
DNS 298ms · TLS 219ms
Spain - Madrid
45ms
DNS 39ms · TLS 4ms
CDN: No CDN · Avg TTFB: 522ms · Cache: No cache headers

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

HSTS header is missing

Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.

Security › Security Headers
Critical: 3

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

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
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. 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.
2 accessibility issues exclude 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

€380 investment → €8,327/month returns + EUR 20,500,000 risk avoided

Investment
€380
6.9 h · 5 findings
Monthly returns
€8.327
€99.926/yr
Payback
0.0 mo
+26168% Y1
Regulatory risk avoided EUR 20.500.000
Or — fix only the top 3 findings
€3440.0 mo payback · +28969% 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

6 barrier(s) likely increasing bounce by ~20%.

Barriers
6
1 crit 5 warn
Bounce delta
+20pp
added vs baseline
Score
75
B
Speed
1
Trust
2
Usability
0
Content
1
Nav
2
  • 4 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
  • Page loads in 3.8s
    Every additional 100ms above 2.5s costs conversions — you're 1.3s over
    → Target <2.5s LCP: defer non-critical scripts and optimize the hero image
  • No HSTS header
    Returning visitors are briefly exposed to downgrade attacks on first request
    → Set Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
  • Content is hard to read
    Graduate-level reading difficulty — limits the addressable audience for product or blog pages
    → Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

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

Remediation cost

€380 6.9 developer hours at €55/hr
Quick wins
€50 3 fixes in ~55 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

€6.376 / month at risk ~€76.509 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

€20.500.000

RGPDEAA
  • Privacy Policy not detected
    RGPD: EUR 10.000 – EUR 20.000.000
  • No <main> landmark found
    EAA: EUR 1.000 – EUR 500.000
  • Skip navigation link is missing (WCAG 2.4.1)
    EAA: EUR 1.000 – EUR 500.000

Bounce-Rate Cost

€6.376 /mo

+19.7pp bounce · ~1,967 lost visitors/mo

CPC: EUR 3.24

Bandwidth Waste

€0,06 /mo

821.7 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~82 KB per page load
    Saves €0,06/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

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

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

3.77 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.31 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.

3.77 s

Desktop

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

1.20 s

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

1.20 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.20 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.20 s

Categories

8
Avg score 83.8

How you compare

Where this site stands against peers running the same stack.

WordPress · 803 peers
You 83
·
Avg 75
+8 above average
0 50 100
Performance P95Compliance P7Security P90Infrastructure P12Accessibility P86Sustainability P77Content P76SEO P54

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

Better than 94% of WordPress sites See full WordPress benchmark →
Font Awesome · 575 peers
You 83
·
Avg 73
+10 above average
0 50 100
Performance P95Compliance P6Security P92Accessibility P89Content P88Sustainability P82Infrastructure P22SEO P61

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

Better than 96% of Font Awesome sites See full Font Awesome benchmark →

Technology stack

WordPress, with Cloudflare CDN

8 technologies detected 3 stack layers 1 with CPE identifier Complex

Stack Architecture

CMS
WordPress
Framework
Font Awesome 6.5.1 Google Font API Google Search Console HTTP/3 Open Graph
CDN
Cloudflare cdnjs

All Detected Technologies (8)

Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.

Categories CDN Website https://www.cloudflare.com Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

cdnjs is a free distributed JS library delivery service.

Categories CDN Website https://cdnjs.com Detected by BeaverCheck
Categories CMS Detected by BeaverCheck · Medium Evidence robots.txt Disallow pattern: /wp-admin/

Font Awesome is a font and icon toolkit based on CSS and Less.

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

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
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=a8KhwCWtmYoy2pZYVFftJzTFGkfiJ_FehDF5TZKKLW8

HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.

Categories Miscellaneous Website https://httpwg.org/ 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 (3)

WordPress detected — review security configuration

WordPress sites benefit from: protecting wp-login.php, disabling XML-RPC if unused, restricting REST API access, and keeping all plugins and themes up to date. Check the Security tab for specific findings.

→ Security

No build tool detected

A framework (Font Awesome) 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%2Ffernandolaserna.com%2Fprueba6%2Findex.html)](https://beavercheck.com/results/0045fef3-1590-442e-bd62-bffd5bad1dd7)
<a href="https://beavercheck.com/results/0045fef3-1590-442e-bd62-bffd5bad1dd7"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ffernandolaserna.com%2Fprueba6%2Findex.html" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Ffernandolaserna.com%2Fprueba6%2Findex.html

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

+6

Highest ROI — low effort, high impact

3 findings 1h → B (89)
  • · No <main> landmark found
  • · HSTS header is missing
  • · No favicon or icon links detected

Sprint 2: Core Fixes

+3

Medium effort, high structural impact

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

Send Feedback