Skip to content
Scanned
2026-06-17 08:56 UTC
Worker
🇪🇸 Madrid
Duration
1.2m
Vs prev

Global Performance

6/6 locations

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

Spain - Madrid
Full audit
149ms
DNS 72ms · TLS 28ms
Netherlands - Amsterdam
38ms
DNS 12ms · TLS 11ms
United Stated - New York
221ms
DNS 9ms · TLS 73ms
United States - Santa Clara
409ms
DNS 10ms · TLS 136ms
Brazil - Sao Paulo
606ms
DNS 19ms · TLS 199ms
Singapore - Singapore
529ms
DNS 11ms · TLS 175ms
CDN: No CDN · Avg TTFB: 326ms · 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

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

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

Page body has only 74 chars of text -- likely empty / placeholder

Security gaps expose your site and users to attacks, eroding trust.

Security › Empty Page Detection
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

110 HTTP requests — consider bundling or reducing

High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.

Performance › Page Weight Budget
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 10.1s 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.
1 accessibility issue excludes users who rely on assistive technology.
Your LCP is 10.1s — 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

£800 investment → £9,874/month returns + GBP 18,050,000 risk avoided

Investment
£800
10.7 h · 5 findings
Monthly returns
£9,874
£118,490/yr
Payback
0.1 mo
+14711% Y1
Regulatory risk avoided GBP 18,050,000
Or — fix only the top 3 findings
£4880.0 mo payback · +24206% 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 ~27%.

Barriers
7
1 crit 6 warn
Bounce delta
+27pp
added vs baseline
Score
72
B
Speed
2
Trust
1
Usability
0
Content
3
Nav
1
  • Page takes 10.1s to load
    Users abandon at ~3s — you're 7.6s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • High main-thread blocking time
    Page is non-interactive for 374ms after first paint
    → Defer third-party scripts and split large bundles
  • 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

£800 10.7 developer hours at £75/hr
Quick wins
£50 2 fixes in ~40 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,622 / month at risk ~£67,470 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

£18,050,000

UK GDPRPECREquality Act 2010
  • No privacy policy link detected
    UK GDPR: GBP 10,000 – GBP 17,500,000
  • Trackers detected but no cookie policy found
    UK GDPR: GBP 10,000 – GBP 17,500,000
  • Trackers detected but no cookie policy found
    PECR: GBP 1,000 – GBP 500,000

Bounce-Rate Cost

£5,622 /mo

+26.8pp bounce · ~2,677 lost visitors/mo

CPC: GBP 2.10

Bandwidth Waste

£0.37 /mo

5810.9 MB/mo × 0.063 GBP/GB

  • Optimize transfer: save ~581 KB per page load
    Saves £0.37/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

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

5.63 s

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

10.06 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

374 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.068

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

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

10.16 s

Desktop

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

597 ms

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

2.30 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.261

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

1.72 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.32 s

Categories

8
Avg score 80.1

How you compare

Where this site stands against peers running the same stack.

Cloudflare · 2145 peers
You 82
·
Avg 75
+7 above average
0 50 100
Compliance P1Security P92Accessibility P91Infrastructure P17Performance P75SEO P39Content P41Sustainability P59

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

Better than 90% of Cloudflare sites See full Cloudflare benchmark →
Google Search Console · 3866 peers
You 82
·
Avg 73
+9 above average
0 50 100
Compliance P2Security P95Accessibility P94Performance P83Sustainability P76Infrastructure P27SEO P33Content P38

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 94% of Google Search Console sites See full Google Search Console benchmark →

Technology stack

Cloudflare, on LiteSpeed

6 technologies detected 2 stack layers 1 with CPE identifier Complex

Stack Architecture

Framework
Cloudflare Google Search Console HSTS HTTP/3 Microsoft 365
Server
LiteSpeed

All Detected Technologies (6)

LiteSpeed is a high-scalability web server.

Categories Web servers Website https://litespeedtech.com Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →
Categories DNS Detected by BeaverCheck Evidence NS record: sneh.ns.cloudflare.com
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=KnFLEVNyu2ocgNrSCYvTToHaBgdHzAbW3fekQ2nlimc

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
Categories Email Detected by BeaverCheck Evidence MX record: elmwoodlaw-com.mail.protection.outlook.com

Observations (1)

No build tool detected

A framework (Cloudflare) 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%2Felmwoodlaw.com)](https://beavercheck.com/results/73743ead-2048-4983-a680-31a9d25a1701)
<a href="https://beavercheck.com/results/73743ead-2048-4983-a680-31a9d25a1701"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Felmwoodlaw.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Felmwoodlaw.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 · 11h total → projected B (88)

Sprint 1: Quick Wins

+4

Highest ROI — low effort, high impact

2 findings 1h → B (86)
  • · No <main> landmark found
  • · Page body has only 74 chars of text -- likely empty / placeholder

Sprint 2: Core Fixes

+2

Medium effort, high structural impact

3 findings 10h → B (88)
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found
  • · 110 HTTP requests — consider bundling or reducing

Send Feedback