Skip to content
PT · EUR (€) · Estimated Applicable regulations: RGPD · ePrivacy Directive · EAA Dev cost: €45/hr How jurisdiction is detected
Scanned
2026-05-17 20:20 UTC
Worker
🇪🇸 Madrid
Duration
34.00s
Vs prev

Global Performance

6/6 locations

Acceptable global latency — average 398ms across 6 locations, fastest from Amsterdam (54ms), slowest from Sao Paulo (775ms). No CDN detected. Cache-Control header is missing. 2 locations above the 500ms target.

Spain - Madrid
Full audit
138ms
DNS 42ms · TLS 34ms
United Stated - New York
408ms
DNS 130ms · TLS 95ms
Netherlands - Amsterdam
54ms
DNS 8ms · TLS 20ms
Singapore - Singapore
492ms
DNS 9ms · TLS 163ms
Brazil - Sao Paulo
775ms
DNS 155ms · TLS 209ms
United States - Santa Clara
523ms
DNS 36ms · TLS 163ms
CDN: No CDN · Avg TTFB: 398ms · 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

2 link(s) with no accessible text

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Accessibility › Link & Button Quality
Warning: 2

/composer.json is publicly accessible

Sensitive resource publicly accessible — restrict access or remove.

Security › Information Leakage
Warning: 3

7 third-party resources (98% 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
Warning: 4

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

Cross-Origin-Opener-Policy header is missing

COOP isolates your top-level browsing context from cross-origin windows — without it, popup-based side-channel attacks remain possible.

Security › Security Headers
What fixing these means. Your site is in great shape. The remaining improvements are refinements rather than critical fixes. Your LCP of 2.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 audience reach.
1 accessibility issue excludes users who rely on assistive technology.
3 security gaps detected — browsers may warn visitors about your site.
Your LCP is 2.7s — 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

€124 investment → €3,205/month returns + EUR 120,500,000 risk avoided

Investment
€124
2.8 h · 4 findings
Monthly returns
€3.205
€38.463/yr
Payback
0.0 mo
+30981% Y1
Regulatory risk avoided EUR 120.500.000
Or — fix only the top 3 findings
€1130.0 mo payback · +34089% 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.
€34 — 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.7s
    Every additional 100ms above 2.5s costs conversions — you're 230ms 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

€124 2.8 developer hours at €45/hr
Quick wins
€34 2 fixes in ~45 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

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

Compliance Risk

€120.500.000

ePrivacy DirectiveRGPDEAA
  • No privacy policy link detected
    RGPD: EUR 10.000 – EUR 20.000.000
  • Trackers detected but no cookie policy found
    RGPD: EUR 5.000 – EUR 10.000.000
  • Trackers detected but no cookie policy found
    RGPD: EUR 10.000 – EUR 20.000.000

Bounce-Rate Cost

€2.851 /mo

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

CPC: EUR 2.20

Bandwidth Waste

€0,06 /mo

746.9 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~75 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 1 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

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

1.83 s

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

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

2.55 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.73 s

Desktop

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

439 ms

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

639 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.002

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

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

639 ms

Categories

8
Avg score 86.2

How you compare

Where this site stands against peers running the same stack.

Google Search Console · 3802 peers
You 87
·
Avg 73
+14 above average
0 50 100
Compliance P1Performance P97Accessibility P97Security P96Sustainability P93Infrastructure P89SEO P59Content P57

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

Better than 98% of Google Search Console sites See full Google Search Console benchmark →
HSTS · 2488 peers
You 87
·
Avg 75
+12 above average
0 50 100
Compliance P3Accessibility P94Performance P93Security P93Sustainability P93Infrastructure P87Content P57SEO P56

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 →

Technology stack

Google Search Console, on Caddy/Go

7 technologies detected 3 stack layers 2 with CPE identifier Complex

Stack Architecture

Framework
Google Search Console HSTS HTTP/3 Open Graph RSS
Runtime
Go
Server
Caddy

All Detected Technologies (7)

Caddy is a Go-based web server known for its simplicity and automatic HTTPS features.

Categories Web servers Website https://caddyserver.com Detected by BeaverCheck Evidence Server header: Caddy
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Go is an open source high-level programming language.

Categories Programming languages Website https://go.dev Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=GCx8159EYV3deOS8OeJ0s8GGq8Q6flR3Nv8VlVY1RDI

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

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

RSS is a family of web feed formats used to publish frequently updated works—such as blog entries, news headlines, audio, and video—in a standardized format.

Categories Miscellaneous Website https://www.rssboard.org/rss-specification Detected by BeaverCheck

Observations (1)

No build tool detected

A framework (Google Search Console) 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%2Femanuelpina.pt)](https://beavercheck.com/results/3404e947-4b09-4214-906c-85d63ac16ab2)
<a href="https://beavercheck.com/results/3404e947-4b09-4214-906c-85d63ac16ab2"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Femanuelpina.pt" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Femanuelpina.pt

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

Sprint 1: Quick Wins

+3

Highest ROI — low effort, high impact

3 findings 1h → A (90)
  • · 2 link(s) with no accessible text
  • · 7 third-party resources (98% of weight)
  • · Cross-Origin-Opener-Policy header is missing

Sprint 2: Core Fixes

+2

Medium effort, high structural impact

2 findings 2h → A (92)
  • · /composer.json is publicly accessible
  • · Cross-Origin-Embedder-Policy header is missing

Send Feedback