Skip to content
Scanned
2026-05-22 16:25 UTC
Worker
🇪🇸 Madrid
Duration
30.00s
Vs prev

Global Performance

6/6 locations

High global latency — average 557ms across 6 locations, fastest from Amsterdam (101ms), slowest from Sao Paulo (999ms). Cloudflare edge cache (DYNAMIC). Cache-Control disables caching (no-store). 3 locations above the 500ms target.

Spain - Madrid
Full audit
192ms
DNS 59ms · TLS 24ms
United Stated - New York
402ms
DNS 14ms · TLS 9ms
Netherlands - Amsterdam
101ms
DNS 23ms · TLS 11ms
United States - Santa Clara
697ms
DNS 35ms · TLS 10ms
Brazil - Sao Paulo
999ms
DNS 226ms · TLS 8ms
Singapore - Singapore
948ms
DNS 218ms · TLS 9ms
CDN: Cloudflare (DYNAMIC) · Avg TTFB: 557ms · Cache: no-store

Audit overview

Compliance needs attention; the rest of the categories are in good shape.

Fix Priority Matrix

5 findings

Quick Wins

4

High impact, low effort — start here.

Strategic

1

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

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

Scan returned a Cloudflare bot-protection interstitial, not the actual page

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

Security › Bot Challenge Detection
Critical: 3

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

1 render-blocking <script src> tag(s) without async/defer

Performance issues directly impact user engagement and conversion rates.

Performance › JavaScript Blocking
Warning: 5

10 third-party resources (93% 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
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. The 2 performance issues below shape how fast users perceive your page. Addressing the critical issues below would have the most immediate impact on your user trust.
2 security gaps detected — browsers may warn visitors about your site.
1 accessibility issue excludes users who rely on assistive technology.
2 performance issues — Akamai's research found 53% of mobile users abandon pages over 3s.

Business case

What fixing the audit's findings is worth -- and what ignoring them keeps costing.

Return on investment

$325 investment → $4,434/month returns + USD 157,500 risk avoided

Investment
$325
3.3 h · 4 findings
Monthly returns
$4,434
$53,212/yr
Payback
0.1 mo
+16273% Y1
Regulatory risk avoided USD 157,500
Or — fix only the top 3 findings
$1250.0 mo payback · +42470% 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.
$125 — 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 ~16%.

Barriers
7
7 warn
Bounce delta
+16pp
added vs baseline
Score
79
B
Speed
0
Trust
2
Usability
0
Content
4
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
  • 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, …)
  • Thin content
    Under 300 words — visitors bounce looking for substance, search engines rank competitors first
    → Add a substantive FAQ, product detail, or case-study section

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

Remediation cost

$325 3.3 developer hours at $100/hr
Quick wins
$125 3 fixes in ~75 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

$4,434 / month at risk ~$53,212 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • 1 non-essential cookie(s) set without consent banner
    CCPA/CPRA: USD 2,500 – USD 7,500
  • 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,434 /mo

+16.5pp bounce · ~1,648 lost visitors/mo

CPC: USD 2.69

Bandwidth Waste

$0.13 /mo

1610.7 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~161 KB per page load
    Saves $0.13/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 3 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.
86
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
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.91 s

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

1.91 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.027

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

1.91 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.91 s

Desktop

94
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
93
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
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.10 s

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

1.33 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.014

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

1.10 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.34 s

Categories

8
Avg score 83.6

How you compare

Where this site stands against peers running the same stack.

AngularJS · 437 peers
You 84
·
Avg 74
+10 above average
0 50 100
Compliance P2Accessibility P96Performance P95SEO P93Content P89Sustainability P84Security P82Infrastructure P54

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

Better than 95% of AngularJS sites See full AngularJS benchmark →
Cloudflare Turnstile · 452 peers
You 84
·
Avg 74
+10 above average
0 50 100
Compliance P3Accessibility P96Performance P95SEO P89Content P85Sustainability P85Security P81Infrastructure P51

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

Better than 95% of Cloudflare Turnstile sites See full Cloudflare Turnstile benchmark →

Technology stack

AngularJS, on LiteSpeed/PHP, with Cloudflare CDN

8 technologies detected 5 stack layers 5 with CPE identifier Complex

Stack Architecture

Analytics
Hostinger
Framework
AngularJS Cloudflare Turnstile Google Search Console HTTP/3
Runtime
PHP 8.2.30
Server
LiteSpeed
CDN
Cloudflare

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 Evidence Server header in redirect: cloudflare
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

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 →

PHP is a general-purpose scripting language used for web development.

Categories Programming languages Website https://php.net Detected by BeaverCheck Evidence x-powered-by: PHP/8.2.30
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

AngularJS is a JavaScript-based open-source web application framework led by the Angular Team at Google.

Categories JavaScript frameworks Website https://angularjs.org Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Turnstile is Cloudflare's smart CAPTCHA alternative.

Categories Security Website https://www.cloudflare.com/products/turnstile Detected by BeaverCheck Evidence Script URL contains challenges.cloudflare.com: https://challenges.cloudflare.com/turnstile/v0/b/1eec422858ff/api.js?onload=fvJqb8&render=explicit
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=Gqg2qpWrd-A3hA2l5CudxHsLi39D4Uc1qxS3aNrEZfA

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

Hostinger is an employee-owned Web hosting provider and internet domain registrar.

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

Observations (3)

Runtime exposed via X-Powered-By header

The X-Powered-By header reveals 'PHP 8.2.30'. Remove this header in production to reduce information leakage.

→ Security

No build tool detected

A framework (AngularJS) 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%2Fdalilakmoh.top)](https://beavercheck.com/results/0d601232-8f03-4de5-a50d-9bec51b003d6)
<a href="https://beavercheck.com/results/0d601232-8f03-4de5-a50d-9bec51b003d6"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fdalilakmoh.top" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fdalilakmoh.top

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

+7

Highest ROI — low effort, high impact

4 findings 1h → A (91)
  • · HSTS header is missing
  • · Scan returned a Cloudflare bot-protection interstitial, not the actual page
  • · No favicon or icon links detected
  • · 10 third-party resources (93% of weight)

Sprint 2: Core Fixes

+1

Medium effort, high structural impact

1 findings 2h → A (92)
  • · 1 render-blocking <script src> tag(s) without async/defer

Send Feedback