Skip to content
Scanned
2026-05-10 12:31 UTC
Worker
🇪🇸 Madrid
Duration
37.00s
Vs prev

Global Performance

6/6 locations

High global latency — average 579ms across 6 locations, fastest from New York (147ms), slowest from Singapore (1212ms). No CDN detected. Cache-Control header is missing. 3 locations above the 500ms target.

Spain - Madrid
Full audit
478ms
DNS 128ms · TLS 118ms
United Stated - New York
147ms
DNS 62ms · TLS 30ms
United States - Santa Clara
336ms
DNS 126ms · TLS 71ms
Netherlands - Amsterdam
566ms
DNS 234ms · TLS 113ms
Brazil - Sao Paulo
737ms
DNS 323ms · TLS 139ms
Singapore - Singapore
1212ms
DNS 485ms · TLS 244ms
CDN: No CDN · Avg TTFB: 579ms · 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

Missing <html lang> attribute (WCAG 3.1.1)

Missing <html lang> attribute -- screen readers default to the user's system language and pronounce content with the wrong phonetics.

Accessibility › Document Language
Critical: 5

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

$650 investment → $7,605/month returns + USD 157,500 risk avoided

Investment
$650
6.5 h · 5 findings
Monthly returns
$7,605
$91,256/yr
Payback
0.1 mo
+13939% Y1
Regulatory risk avoided USD 157,500
Or — fix only the top 3 findings
$6250.1 mo payback · +14501% 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

7 barrier(s) likely increasing bounce by ~28%.

Barriers
7
1 crit 6 warn
Bounce delta
+28pp
added vs baseline
Score
72
B
Speed
0
Trust
2
Usability
1
Content
3
Nav
1
  • No viewport meta tag
    Mobile browsers render at desktop width and shrink — text unreadable, tap targets miniature
    → Add <meta name="viewport" content="width=device-width, initial-scale=1">
  • 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
  • No Open Graph tags
    Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
    → Add og:title, og:description, og:image, og:url to the page head
  • 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

$650 6.5 developer hours at $100/hr
Quick wins
$50 3 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

$20,730 / month at risk ~$248,756 / 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
  • No headings found
    ADA Title III: USD 25,000 – USD 150,000
  • Missing <html lang> attribute (WCAG 3.1.1)
    ADA Title III: USD 25,000 – USD 150,000

Bounce-Rate Cost

$7,605 /mo

+28.3pp bounce · ~2,827 lost visitors/mo

CPC: USD 2.69

Bandwidth Waste

$0.00 /mo

12.3 MB/mo × 0.080 USD/GB

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

98
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
59
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
73
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
90
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.84 s

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

1.84 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.84 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.84 s

Desktop

100
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
59
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
73
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
90
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.

529 ms

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

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

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

529 ms

Categories

8
Avg score 78.6

How you compare

Where this site stands against peers running the same stack.

Apache · 447 peers
You 81
·
Avg 73
+8 above average
0 50 100
Compliance P2Security P97Accessibility P94Performance P91Infrastructure P16Sustainability P80SEO P23Content P49

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

Better than 96% of Apache sites See full Apache benchmark →

Technology stack

Apache, hosted on Apache HTTP Server

2 technologies detected 2 stack layers 1 with CPE identifier Minimal

Stack Architecture

Server
Apache
Hosting
Apache HTTP Server

All Detected Technologies (2)

Categories Server Website https://httpd.apache.org Detected by BeaverCheck Evidence Server header: Apache

Apache is a free and open-source cross-platform web server software.

Categories Web servers Website https://httpd.apache.org/ Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Observations (1)

Minimal technology footprint

Only 2 technologies detected. This suggests a simple setup with minimal dependencies — excellent for performance and security.

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%2FIwindirect.com)](https://beavercheck.com/results/d2adf99b-2f4e-42f2-b096-6961888bb833)
<a href="https://beavercheck.com/results/d2adf99b-2f4e-42f2-b096-6961888bb833"><img src="https://beavercheck.com/badge?url=https%3A%2F%2FIwindirect.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2FIwindirect.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 · 6h total → projected B (89)

Sprint 1: Quick Wins

+6

Highest ROI — low effort, high impact

3 findings 0h → B (87)
  • · Missing <html lang> attribute (WCAG 3.1.1)
  • · No <main> landmark found
  • · HSTS header is missing

Sprint 2: Core Fixes

+2

Medium effort, high structural impact

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

Send Feedback