Skip to content
Scanned
2026-05-10 14:23 UTC
Worker
🇪🇸 Madrid
Duration
38.00s
Vs prev

Global Performance

6/6 locations

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

Spain - Madrid
Full audit
396ms
DNS 41ms · TLS 121ms
United Stated - New York
78ms
DNS 14ms · TLS 25ms
Netherlands - Amsterdam
425ms
DNS 137ms · TLS 100ms
United States - Santa Clara
158ms
DNS 14ms · TLS 51ms
Brazil - Sao Paulo
659ms
DNS 244ms · TLS 142ms
Singapore - Singapore
1609ms
DNS 12ms · TLS 875ms
CDN: No CDN · Avg TTFB: 554ms · Cache: No cache headers

Audit overview

Compliance and Content need attention; the other categories are in good shape.

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

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
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. Addressing the critical issues below would have the most immediate impact on your user trust.
4 security gaps detected — browsers may warn visitors about your site.
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

$742 investment → $4,730/month returns + USD 157,500 risk avoided

Investment
$742
7.4 h · 5 findings
Monthly returns
$4,730
$56,765/yr
Payback
0.2 mo
+7554% Y1
Regulatory risk avoided USD 157,500
Or — fix only the top 3 findings
$6250.1 mo payback · +8982% 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.
$42 — 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 ~18%.

Barriers
7
7 warn
Bounce delta
+18pp
added vs baseline
Score
79
B
Speed
0
Trust
2
Usability
1
Content
3
Nav
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
  • Layout shifts during page load
    Content movement causes mis-clicks on CTAs and form fields
    → Add width/height to images; reserve space for late-loading embeds
  • 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

$742 7.4 developer hours at $100/hr
Quick wins
$42 2 fixes in ~25 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

$17,855 / month at risk ~$214,265 / 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

$4,730 /mo

+17.6pp bounce · ~1,758 lost visitors/mo

CPC: USD 2.69

Bandwidth Waste

$0.64 /mo

7956.7 MB/mo × 0.080 USD/GB

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

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

775 ms

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

1.35 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.233

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

1.02 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.35 s

Desktop

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

210 ms

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

367 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.062

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

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

367 ms

Categories

8
Avg score 78.8

How you compare

Where this site stands against peers running the same stack.

Ubuntu · 65 peers
You 82
·
Avg 73
+9 above average
0 50 100
Better than 95% of Ubuntu sites See full Ubuntu benchmark →
Apache · 445 peers
You 82
·
Avg 73
+9 above average
0 50 100
Accessibility P99Security P97Compliance P4Performance P86Content P25SEO P28Sustainability P63Infrastructure P42

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

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

Technology stack

Ubuntu, on Apache, hosted on Apache HTTP Server

3 technologies detected 3 stack layers 2 with CPE identifier Standard

Stack Architecture

Framework
Ubuntu
Server
Apache 2.4.58
Hosting
Apache HTTP Server 2.4.58

All Detected Technologies (3)

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

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 →

Ubuntu is a free and open-source operating system on Linux for the enterprise server, desktop, cloud, and IoT.

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

Observations (2)

Server version exposed in headers

The Server header reveals 'Apache 2.4.58'. Exposing exact server versions helps attackers target known vulnerabilities. Consider configuring your server to hide version information.

→ Security

No build tool detected

A framework (Ubuntu) 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%2Fhalftoberfest.com)](https://beavercheck.com/results/0596ecaa-47d6-40a6-a025-6362bc46b6ef)
<a href="https://beavercheck.com/results/0596ecaa-47d6-40a6-a025-6362bc46b6ef"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fhalftoberfest.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fhalftoberfest.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 · 7h total → projected B (88)

Sprint 1: Quick Wins

+4

Highest ROI — low effort, high impact

2 findings 0h → B (86)
  • · No <main> landmark found
  • · HSTS header is missing

Sprint 2: Core Fixes

+2

Medium effort, high structural impact

3 findings 7h → B (88)
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found
  • · Cross-Origin-Embedder-Policy header is missing

Send Feedback