Skip to content
Recent Trends
Performance stable →
34
TTFB stable →
329ms
FCP stable →
8.9s
LCP stable →
17.5s
Scanned
2026-05-18 13:44 UTC
Worker
🇧🇷 Sao Paulo
Duration
1.2m
Vs prev
no change

Global Performance

6/6 locations

Acceptable global latency — average 346ms across 6 locations, fastest from Amsterdam (95ms), slowest from Sao Paulo (605ms). Cloudflare edge cache (DYNAMIC). Cache-Control header is missing. 1 location above the 500ms target.

Brazil - Sao Paulo
Full audit
605ms
DNS 7ms · TLS 9ms
Spain - Madrid
117ms
DNS 31ms · TLS 22ms
Netherlands - Amsterdam
95ms
DNS 8ms · TLS 13ms
United Stated - New York
279ms
DNS 9ms · TLS 8ms
United States - Santa Clara
483ms
DNS 9ms · TLS 8ms
Singapore - Singapore
498ms
DNS 9ms · TLS 8ms
CDN: Cloudflare (DYNAMIC) · Avg TTFB: 346ms · 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

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

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 10 chars of text -- likely empty / placeholder

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

Security › Empty Page Detection
Critical: 4

Missing <html lang> attribute (WCAG 3.1.1)

Missing <html lang> attribute -- screen readers default to the user's system language and pronounce content with the wrong phonetics.

Accessibility › Document Language
Critical: 5

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
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. 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.
2 accessibility issues exclude users who rely on assistive technology.

Business case

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

Return on investment

$675 investment → $8,161/month returns + USD 157,500 risk avoided

Investment
$675
6.8 h · 5 findings
Monthly returns
$8,161
$97,936/yr
Payback
0.1 mo
+14409% Y1
Regulatory risk avoided USD 157,500
Or — fix only the top 3 findings
$6500.1 mo payback · +14967% 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

8 barrier(s) likely increasing bounce by ~30%.

Barriers
8
2 crit 6 warn
Bounce delta
+30pp
added vs baseline
Score
62
C
Speed
2
Trust
1
Usability
1
Content
3
Nav
1
  • Page takes 22.5s to load
    Users abandon at ~3s — you're 20.0s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • Page feels frozen for 691ms
    Clicks on the primary CTA are ignored while JavaScript runs
    → Break up long tasks; defer non-critical JavaScript to post-hydration
  • 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
  • Viewport disables user zoom
    Visitors with low vision can't read the page — and some jurisdictions treat this as a legal risk
    → Remove user-scalable=no; drop maximum-scale if it's below 2
  • 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

$675 6.8 developer hours at $100/hr
Quick wins
$75 3 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,161 / month at risk ~$97,936 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • No privacy policy link detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Privacy Policy not detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • No <main> landmark found
    ADA Title III: USD 25,000 – USD 150,000

Bounce-Rate Cost

$8,161 /mo

+30.3pp bounce · ~3,034 lost visitors/mo

CPC: USD 2.69

Bandwidth Waste

$0.40 /mo

5024.4 MB/mo × 0.080 USD/GB

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

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

12.18 s

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

22.52 s

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

691 ms

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

0.054

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

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

22.52 s

Desktop

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

2.88 s

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

4.30 s

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

61 ms

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

0.016

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

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

4.30 s

Categories

8
Avg score 79.2

How you compare

Where this site stands against peers running the same stack.

core-js · 1570 peers
You 80
·
Avg 72
+8 above average
0 50 100
Compliance P1Security P98Sustainability P96Accessibility P95Performance P94SEO P8Infrastructure P17Content P22

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

Better than 95% of core-js sites See full core-js benchmark →
HSTS · 2487 peers
You 80
·
Avg 75
At average
0 50 100
Compliance P1Security P90Infrastructure P11Accessibility P89Sustainability P85SEO P24Performance P76Content P35

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

Better than 83% of HSTS sites See full HSTS benchmark →

Technology stack

HSTS, with Cloudflare CDN

7 technologies detected 2 stack layers 2 with CPE identifier Complex

Stack Architecture

Framework
HSTS HTTP/3 Sentry core-js 3.46.0 lit-element 4.2.0 lit-html 3.3.0
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 →

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

Sentry is an open-source platform for workflow productivity, aggregating errors from across the stack in real time.

Categories Issue trackers Website https://sentry.io/ Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

core-js is a modular standard library for JavaScript, with polyfills for cutting-edge ECMAScript features.

Categories JavaScript libraries Website https://github.com/zloirock/core-js Detected by BeaverCheck

lit-element is a simple base class for creating web components that work in any web page with any framework. lit-element uses lit-html to render into shadow DOM, and adds API to manage properties and attributes.

Categories JavaScript libraries Website https://lit.dev Detected by BeaverCheck

lit-html is a simple, modern, safe, small and fast HTML templating library for JavaScript.

Categories JavaScript libraries Website https://lit.dev Detected by BeaverCheck

Observations (1)

No build tool detected

A framework (HSTS) 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%2Fmindmx.org)](https://beavercheck.com/results/62603bb9-0bac-4876-a3d3-1db5373a58ba)
<a href="https://beavercheck.com/results/62603bb9-0bac-4876-a3d3-1db5373a58ba"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fmindmx.org" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fmindmx.org

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 · 7h total → projected B (88)

Sprint 1: Quick Wins

+6

Highest ROI — low effort, high impact

3 findings 1h → B (86)
  • · Missing <html lang> attribute (WCAG 3.1.1)
  • · No <main> landmark found
  • · Page body has only 10 chars of text -- likely empty / placeholder

Sprint 2: Core Fixes

+2

Medium effort, high structural impact

2 findings 6h → B (88)
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found

Send Feedback