Skip to content
Scanned
2026-04-22 01:07 UTC
Worker
🇺🇸 New York
Duration
3.9m
Vs prev

Audit overview

3 categories need attention: Performance, and 2 others.

Fix Priority Matrix

5 findings

Quick Wins

1

High impact, low effort — start here.

Strategic

4

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

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

574 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
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 has several issues that may be affecting user experience and business outcomes. Your LCP of 3.9s 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 3.9s — 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

€880 investment → €9,283/month returns + EUR 120,000,000 risk avoided

Investment
€880
11.0 h · 4 findings
Monthly returns
€9.283
€111.393/yr
Payback
0.1 mo
+12558% Y1
Regulatory risk avoided EUR 120.000.000
Or — fix only the top 3 findings
€8000.1 mo payback · +13824% 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.

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

6 barrier(s) likely increasing bounce by ~33%.

Barriers
6
3 crit 3 warn
Bounce delta
+33pp
added vs baseline
Score
61
C
Speed
2
Trust
2
Usability
2
Content
0
Nav
0
  • Page feels frozen for 4.7s
    Clicks on the primary CTA are ignored while JavaScript runs
    → Break up long tasks; defer non-critical JavaScript to post-hydration
  • Severe layout shift during page load
    Users mis-click when content jumps — converting intent into frustration
    → Reserve space for images, ads, and embeds with explicit width/height
  • No viewport meta tag
    Mobile browsers render at desktop width and shrink — text unreadable, tap targets miniature
    → Add <meta name="viewport" content="width=device-width, initial-scale=1">
  • Page loads in 3.9s
    Every additional 100ms above 2.5s costs conversions — you're 1.4s over
    → Target <2.5s LCP: defer non-critical scripts and optimize the hero image
  • No HSTS header
    Returning visitors are briefly exposed to downgrade attacks on first request
    → Set Strict-Transport-Security: max-age=31536000; includeSubDomains

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

Remediation cost

€880 11.0 developer hours at €80/hr

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.339 / month at risk ~€88.070 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

€120.000.000

ePrivacy DirectiveRGPD
  • No privacy policy link detected
    RGPD: EUR 10.000 – EUR 20.000.000
  • Trackers detected but no cookie policy found
    RGPD: EUR 5.000 – EUR 10.000.000
  • Trackers detected but no cookie policy found
    RGPD: EUR 10.000 – EUR 20.000.000

Bounce-Rate Cost

€7.338 /mo

+33.4pp bounce · ~3,336 lost visitors/mo

CPC: EUR 2.20

Bandwidth Waste

€0,75 /mo

10105.8 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~1.0 MB per page load
    Saves €0,75/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 2 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

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

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

3.94 s

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

4.68 s

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

0.295

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

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

34.46 s

Desktop

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

919 ms

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

970 ms

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

390 ms

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

0.008

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

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

6.45 s

Categories

6
Avg score 67.3

How you compare

Where this site stands against peers running the same stack.

Cloudflare · 2298 peers
You 63
·
Avg 75
-12 below average
0 50 100
Performance P1Accessibility P1Sustainability P34Compliance P45Infrastructure P55Security P47

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

Google Search Console · 3990 peers
You 63
·
Avg 74
-11 below average
0 50 100
Performance P1Accessibility P1Infrastructure P69Security P55Sustainability P55Compliance P49

Top 10% of Google Search Console sites score 89+ on Performance; you're at 64 — closing this gap is the highest-leverage improvement.

Technology stack

Cloudflare, with Nginx CDN

4 technologies detected 2 stack layers 1 with CPE identifier Standard

Stack Architecture

Framework
Cloudflare Google Search Console HSTS
CDN
Nginx 1.22.1

All Detected Technologies (4)

Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.

Categories Web servers, Reverse proxies Website https://nginx.org/en Detected by BeaverCheck Evidence Server header: nginx/1.22.1
This technology has a CPE identifier — check for known vulnerabilities Search NVD →
Categories DNS Detected by BeaverCheck Evidence NS record: duke.ns.cloudflare.com
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=QUmIpmPK89ccL7TjiiUvrVBAMM_QTZnjGU6mhtd57Iw

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

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

Sprint 1: Quick Wins

+1

Highest ROI — low effort, high impact

1 findings 0h → D (64)
  • · 573 third-party resources (100% of weight)

Sprint 2: Core Fixes

+7

Medium effort, high structural impact

4 findings 11h → C (71)
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found
  • · Cross-Origin-Embedder-Policy header is missing
  • · 574 HTTP requests — consider bundling or reducing

Send Feedback