Skip to content
Recent Trends
Performance stable →
43
TTFB stable →
99ms
FCP stable →
3.8s
LCP stable →
13.8s
Scanned
2026-08-20 13:22 UTC
Worker
🇪🇸 Madrid
Duration
43.00s
Vs prev
Improved by +9

Global Performance

6/6 locations

Acceptable global latency — average 201ms across 6 locations, fastest from New York (80ms), slowest from Sao Paulo (434ms). Cloudflare in front. Cache-Control header is missing.

Spain - Madrid
Full audit
99ms
DNS 27ms · TLS 28ms
United Stated - New York
80ms
DNS 6ms · TLS 12ms
United States - Santa Clara
172ms
DNS 8ms · TLS 10ms
Netherlands - Amsterdam
161ms
DNS 7ms · TLS 10ms
Brazil - Sao Paulo
434ms
DNS 5ms · TLS 9ms
Singapore - Singapore
260ms
DNS 3ms · TLS 11ms
CDN: Cloudflare · Avg TTFB: 201ms · Cache: No cache headers

Audit overview

All categories sit comfortably above the 70 threshold; this is a clean audit.

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

'unsafe-eval' found in script source

Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.

Security › Content Security Policy
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

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

78 third-party resources (100% 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. Your LCP of 13.8s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute 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.
Your LCP is 13.8s — fixing the 2 performance criticals 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

$875 investment → $9,008/month returns + USD 150,000 risk avoided

Investment
$875
8.8 h · 4 findings
Monthly returns
$9,008
$108,090/yr
Payback
0.1 mo
+12253% Y1
Regulatory risk avoided USD 150,000
Or — fix only the top 3 findings
$6750.1 mo payback · +15913% 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.
$75 — 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

9 barrier(s) likely increasing bounce by ~31%.

Barriers
9
2 crit 7 warn
Bounce delta
+31pp
added vs baseline
Score
59
C
Speed
2
Trust
2
Usability
0
Content
4
Nav
1
  • Page takes 13.8s to load
    Users abandon at ~3s — you're 11.3s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • Page feels frozen for 884ms
    Clicks on the primary CTA are ignored while JavaScript runs
    → Break up long tasks; defer non-critical JavaScript to post-hydration
  • 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

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

Remediation cost

$875 8.8 developer hours at $100/hr
Quick wins
$75 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

$8,335 / month at risk ~$100,016 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

$150,000

ADA Title III
  • 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

$8,334 /mo

+31.0pp bounce · ~3,098 lost visitors/mo

CPC: USD 2.69

Bandwidth Waste

$0.36 /mo

4489.7 MB/mo × 0.080 USD/GB

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

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

3.77 s

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

13.82 s

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

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

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

13.88 s

Desktop

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

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

3.16 s

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

18 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.45 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.

3.24 s

Categories

8
Avg score 80.6

How you compare

Where this site stands against peers running the same stack.

AngularJS · 468 peers
You 82
·
Avg 74
+8 above average
0 50 100
Security P97Accessibility P94Compliance P7Content P84SEO P83Infrastructure P28Sustainability P44Performance P54

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

Better than 90% of AngularJS sites See full AngularJS benchmark →
Cloudflare Bot Management · 503 peers
You 82
·
Avg 75
+7 above average
0 50 100
Security P96Accessibility P95Compliance P13Infrastructure P25Performance P73SEO P41Sustainability P56Content P47

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

Better than 92% of Cloudflare Bot Management sites See full Cloudflare Bot Management benchmark →

Technology stack

AngularJS, with Cloudflare CDN

7 technologies detected 2 stack layers 2 with CPE identifier Complex

Stack Architecture

Framework
AngularJS Cloudflare Bot Management Cloudflare Turnstile Facebook Google Workspace HTTP/3
CDN
Cloudflare

All Detected Technologies (7)

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 →

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 →

Cloudflare bot management solution identifies and mitigates automated traffic to protect websites from bad bots.

Categories Security Website https://www.cloudflare.com/en-gb/products/bot-management/ Detected by BeaverCheck

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/g/aae2b9a1c261/api.js?onload=mlyM5&render=explicit
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: facebook-domain-verification=dcrdstbacm7lya00lby6c3t8cfhov6
Categories Email Detected by BeaverCheck Evidence MX record: aspmx.l.google.com

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

Observations (1)

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.

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%2Fmediafire.com)](https://beavercheck.com/sites/mediafire.com)
<a href="https://beavercheck.com/sites/mediafire.com"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fmediafire.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fmediafire.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

3 sprints · 9h total → projected B (87)

Sprint 1: Quick Wins

+4

Highest ROI — low effort, high impact

3 findings 1h → B (86)
  • · HSTS header is missing
  • · Scan returned a Cloudflare bot-protection interstitial, not the actual page
  • · 78 third-party resources (100% of weight)

Sprint 2: Core Fixes

+1

Medium effort, high structural impact

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

Sprint 3: Strategic Improvements

Higher effort, long-term payoff

1 findings 6h → B (87)
  • · 'unsafe-eval' found in script source

Send Feedback