Skip to content
Recent Trends
Performance stable →
64
TTFB stable →
754ms
FCP stable →
3.8s
LCP stable →
4.0s
Scanned
2026-06-30 07:27 UTC
Worker
🇪🇸 Madrid
Duration
39.00s
Vs prev
no change

Global Performance

6/6 locations

High global latency — average 529ms across 6 locations, fastest from Santa Clara (175ms), slowest from Sao Paulo (793ms). Cloudflare edge cache (DYNAMIC). 4 locations above the 500ms target.

Spain - Madrid
Full audit
754ms
DNS 34ms · TLS 24ms
United States - Santa Clara
175ms
DNS 72ms · TLS 11ms
United Stated - New York
320ms
DNS 31ms · TLS 9ms
Netherlands - Amsterdam
543ms
DNS 32ms · TLS 10ms
Singapore - Singapore
589ms
DNS 16ms · TLS 14ms
Brazil - Sao Paulo
793ms
DNS 113ms · TLS 9ms
CDN: Cloudflare (DYNAMIC) · Avg TTFB: 529ms · Cache: public,max-age=0,must-revalidate

Audit overview

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

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

'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

'unsafe-inline' 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: 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
Critical: 4

Soft 404: server returns HTTP 200 for non-existent pages

Soft 404s (HTTP 200 for missing pages) confuse Google — it indexes the 'not found' page as real content and ranks it.

Accessibility › 404 Error Page
Warning: 5

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

Performance issues directly impact user engagement and conversion rates.

Performance › JavaScript Blocking
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 4.0s 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 4.0s — 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

$1,500 investment → $10,115/month returns + USD 150,000 risk avoided

Investment
$1,500
15.0 h · 5 findings
Monthly returns
$10,115
$121,376/yr
Payback
0.1 mo
+7992% Y1
Regulatory risk avoided USD 150,000
Or — fix only the top 3 findings
$1,2500.1 mo payback · +9610% 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.
$100 — 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 4.0s to load
    Users abandon at ~3s — you're 1.5s 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 499ms 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

$1,500 15.0 developer hours at $100/hr
Quick wins
$100 2 fixes in ~60 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

$7,202 / month at risk ~$86,422 / 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

$7,202 /mo

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

CPC: USD 2.69

Bandwidth Waste

$0.17 /mo

2106.4 MB/mo × 0.080 USD/GB

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

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

3.85 s

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

4.05 s

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

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

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

7.48 s

Desktop

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

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

1.40 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.132

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

1.27 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.40 s

Categories

8
Avg score 83.1

How you compare

Where this site stands against peers running the same stack.

AngularJS · 453 peers
You 84
·
Avg 74
+10 above average
0 50 100
Compliance P7Security P91SEO P91Accessibility P90Performance P88Content P86Sustainability P68Infrastructure P59

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

Better than 93% of AngularJS sites See full AngularJS benchmark →
Cloudflare Turnstile · 471 peers
You 84
·
Avg 74
+10 above average
0 50 100
Compliance P7Security P91Accessibility P90Performance P88SEO P87Content P83Sustainability P69Infrastructure P57

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

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

Technology stack

AngularJS, with Cloudflare CDN

7 technologies detected 2 stack layers 2 with CPE identifier Complex

Stack Architecture

Framework
AngularJS Cloudflare Turnstile Google Search Console HSTS HTTP/3
CDN
Cloudflare Netlify

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 →

Netlify providers hosting and server-less backend services for web applications and static websites.

Categories PaaS, CDN Website https://www.netlify.com/ Detected by BeaverCheck Evidence Header: x-nf-request-id

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/25e6c66701a0/api.js?onload=ePmH8&render=explicit
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=7HB1XU6np9P3KQ7JyHth2jR2ceQbUNGlE5quVFRXP4Q

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

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%2Fnotehand.app)](https://beavercheck.com/results/2dea0a77-1782-4c56-971d-27c0f991c631)
<a href="https://beavercheck.com/results/2dea0a77-1782-4c56-971d-27c0f991c631"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fnotehand.app" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fnotehand.app

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 · 15h total → projected A (91)

Sprint 1: Quick Wins

+4

Highest ROI — low effort, high impact

2 findings 1h → B (88)
  • · Scan returned a Cloudflare bot-protection interstitial, not the actual page
  • · Soft 404: server returns HTTP 200 for non-existent pages

Sprint 2: Core Fixes

+1

Medium effort, high structural impact

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

Sprint 3: Strategic Improvements

+2

Higher effort, long-term payoff

2 findings 12h → A (91)
  • · 'unsafe-eval' found in script source
  • · 'unsafe-inline' found in script source

Send Feedback