Skip to content
Recent Trends
Performance degrading ↓
44
TTFB stable →
127ms
FCP degrading ↓
3.1s
LCP degrading ↓
9.4s
Scanned
2026-05-25 04:47 UTC
Worker
🇧🇷 Sao Paulo
Duration
45.00s
Vs prev
Declined by -2

Global Performance

6/6 locations

Excellent global latency — average 72ms across 6 locations, fastest from Singapore (22ms), slowest from Madrid (166ms). No CDN detected.

Brazil - Sao Paulo
Full audit
127ms
DNS 3ms · TLS 53ms
Netherlands - Amsterdam
27ms
DNS 2ms · TLS 8ms
United Stated - New York
34ms
DNS 2ms · TLS 10ms
Spain - Madrid
166ms
DNS 21ms · TLS 50ms
United States - Santa Clara
55ms
DNS 4ms · TLS 23ms
Singapore - Singapore
22ms
DNS 3ms · TLS 4ms
CDN: No CDN · Avg TTFB: 72ms · Cache: max-age=2592000

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

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

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

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

1 control(s) without accessible label

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Accessibility › Form Accessibility
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

BRL 1,335 investment → BRL 15,351/month returns

Investment
BRL 1.335
7.4 h · 5 findings
Monthly returns
BRL 15.351
BRL 184.209/yr
Payback
0.1 mo
+13698% Y1
Or — fix only the top 3 findings
BRL 1.1250.1 mo payback · +16274% 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.
BRL 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

10 barrier(s) likely increasing bounce by ~38%.

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

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

Remediation cost

R$1,335 7.4 developer hours at R$180/hr
Quick wins
R$75 2 fixes in ~25 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.

R$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

Warning:Cost of inaction

BRL 9.617 / month at risk ~BRL 115.409 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Bounce-Rate Cost

BRL 9.616 /mo

+38.5pp bounce · ~3,847 lost visitors/mo

CPC: BRL 2.50

Bandwidth Waste

BRL 1,04 /mo

2547.1 MB/mo × 0.410 BRL/GB

  • Optimize transfer: save ~255 KB per page load
    Saves BRL 1,04/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

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

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

9.42 s

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

1.28 s

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

0.025

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

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

9.42 s

Desktop

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

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

1.43 s

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

112 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.11 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.

2.11 s

Categories

8
Avg score 81.2

How you compare

Where this site stands against peers running the same stack.

Apple · 1266 peers
You 82
·
Avg 73
+9 above average
0 50 100
Security P97Accessibility P97Performance P92Sustainability P89Compliance P14SEO P31Content P33Infrastructure P62

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

Better than 98% of Apple sites See full Apple benchmark →
Facebook · 1405 peers
You 82
·
Avg 72
+10 above average
0 50 100
Security P98Accessibility P98Performance P92Sustainability P88Compliance P14Content P32SEO P33Infrastructure P58

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

Better than 98% of Facebook sites See full Facebook benchmark →

Technology stack

Apple, hosted on Google Web Server

9 technologies detected 2 stack layers 1 with CPE identifier Enterprise

Stack Architecture

Framework
Apple Facebook Google Domains Google Search Console Google Workspace HTTP/3 Microsoft Priority Hints
Hosting
Google Web Server

All Detected Technologies (9)

Categories Web servers Website https://en.wikipedia.org/wiki/Google_Web_Server Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →
Categories Analytics Detected by BeaverCheck · Low Evidence TXT record: apple-domain-verification=30afIBcvSuDV2PLX
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: facebook-domain-verification=22rm551cu4k0ab0bxsw536tlds4h95
Categories DNS Detected by BeaverCheck Evidence NS record: ns3.google.com
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=wD8N7i1JTNTkezJ49swvWW48f8_9xveREV4oB-0Hf5o
Categories Email Detected by BeaverCheck Evidence MX record: smtp.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
Categories Analytics Detected by BeaverCheck · Low Evidence TXT record: MS=E4A68B9AB2BB9670BCE15412F62916164C0B20BB

Priority Hints exposes a mechanism for developers to signal a relative priority for browsers to consider when fetching resources.

Categories Performance Website https://wicg.github.io/priority-hints/ Detected by BeaverCheck

Observations (2)

No build tool detected

A framework (Apple) 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

9 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%2Fgoogle.com)](https://beavercheck.com/results/d7aeb9f5-b8ae-440e-b1d6-c8fb8099781d)
<a href="https://beavercheck.com/results/d7aeb9f5-b8ae-440e-b1d6-c8fb8099781d"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fgoogle.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fgoogle.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 · 7h total → projected A (90)

Sprint 1: Quick Wins

+4

Highest ROI — low effort, high impact

2 findings 0h → B (86)
  • · No <main> landmark found
  • · HSTS header is missing

Sprint 2: Core Fixes

+4

Medium effort, high structural impact

3 findings 7h → A (90)
  • · 1 control(s) without accessible label
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found

Send Feedback