Skip to content
Scanned
2026-10-04 17:55 UTC
Worker
🇧🇷 Sao Paulo
Duration
4.3m
Vs prev
—

Global Performance

6/6 locations ✓

High global latency — average 1171ms across 6 locations, fastest from Amsterdam (415ms), slowest from Sao Paulo (2046ms). No CDN (document or assets). Cache-Control header is missing. 4 locations above the 500ms target.

Brazil - Sao Paulo
Full audit
2046ms
DNS 1085ms · TLS 284ms
Spain - Madrid
424ms
DNS 67ms · TLS 105ms
United Stated - New York
1028ms
DNS 412ms · TLS 166ms
Netherlands - Amsterdam
415ms
DNS 91ms · TLS 92ms
United States - Santa Clara
1503ms
DNS 691ms · TLS 227ms
Singapore - Singapore
1611ms
DNS 619ms · TLS 309ms
CDN: No CDN (document or assets) · Avg TTFB: 1171ms · Cache: No cache headers

Audit overview

Accessibility and Sustainability need attention; the other 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

Your mail setup has problems.

shahoclimb.com fails 2 mail checks: No DMARC record found, No SPF record found. This is the kind of misconfiguration that sends your mail to spam.

Get a full deliverability audit — €179, 48h →

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

Page weighs 4.4 MB (4.5 MB transferred)

Informational: total page weight (uncompressed) and bytes actually transferred over the wire.

Performance › Page Weight Budget
Warning: 3

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

Cross-Origin-Opener-Policy header is missing

COOP isolates your top-level browsing context from cross-origin windows — without it, popup-based side-channel attacks remain possible.

Security › Security Headers
Warning: 5

HSTS is enabled but max-age is short (2592000s, should be >= 31536000s)

HSTS is on, but a short max-age means browsers forget the policy sooner than recommended — set >= 1 year.

Security › Security Headers
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 14.8s 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.
4 security gaps detected — browsers may warn visitors about your site.
Your LCP is 14.8s — 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

IRR 6,500,000 investment → IRR 383,226,145/month returns

Investment
IRR 6,500,000
4.3 h · 4 findings
Monthly returns
IRR 383,226,145
IRR 4,598,713,738/yr
Payback
0.0 mo
+70649% Y1
Or — fix only the top 3 findings
IRR 6,375,000 → 0.0 mo payback · +72037% 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.
IRR 500,000 — 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

5 barrier(s) likely increasing bounce by ~34%.

Barriers
5
3 crit 2 warn
Bounce delta
+34pp
added vs baseline
Score
64
C
Speed
1
Trust
2
Usability
2
Content
0
Nav
0
  • Page takes 14.8s to load
    Users abandon at ~3s — you're 12.3s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • 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">
  • HSTS is enabled but max-age is short (2592000s)
    First-visit protection is in place, but browsers forget the policy sooner than recommended
    → Raise Strict-Transport-Security max-age to at least 31536000 (1 year)
  • 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

﷼6,500,000 4.3 developer hours at ﷼1500000/hr
Quick wins
﷼500,000 2 fixes in ~20 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

IRR 383,226,145 / month at risk ~IRR 4,598,713,738 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Bounce-Rate Cost

IRR 383,179,044 /mo

+33.9pp bounce · ~3,390 lost visitors/mo

CPC: IRR 113025.21

Bandwidth Waste

IRR 47,101 /mo

14012.5 MB/mo × 3361.345 IRR/GB

  • Optimize transfer: save ~1.4 MB per page load
    Saves IRR 47,101/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

31
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
74
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
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.

10.11 s

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

14.76 s

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

60 ms

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

1.491

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

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

18.10 s

Desktop

38
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
74
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
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.

2.08 s

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

4.96 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.763

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

3.23 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.99 s

Categories

6
Avg score 72.2

How you compare

Where this site stands against peers running the same stack.

HSTS · 3210 peers
You 73
·
Avg 77
At average
0 50 100
Infrastructure P4Sustainability P24Accessibility P34Compliance P38Performance P41Security P58

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

Better than 23% of HSTS sites See full HSTS benchmark →
Microsoft ASP.NET · 139 peers
You 73
·
Avg 73
At average
0 50 100
Better than 51% of Microsoft ASP.NET sites See full Microsoft ASP.NET benchmark →

Technology stack

HSTS, on IIS/ASP.NET, hosted on Microsoft IIS

6 technologies detected 4 stack layers 2 with CPE identifier Complex

Stack Architecture

Framework
HSTS Microsoft ASP.NET Windows Server
Runtime
ASP.NET
Server
IIS 10.0
Hosting
Microsoft IIS 10.0

All Detected Technologies (6)

Internet Information Services (IIS) is an extensible web server software created by Microsoft for use with the Windows NT family.

Categories Web servers Website https://www.iis.net Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →
Categories Server Website https://www.iis.net Detected by BeaverCheck Evidence Server header: Microsoft-IIS/10.0
Categories Runtime Website https://dotnet.microsoft.com Detected by BeaverCheck Evidence x-powered-by: ASP.NET

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

ASP.NET is an open-source, server-side web-application framework designed for web development to produce dynamic web pages.

Categories Web frameworks Website https://www.asp.net Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Windows Server is a brand name for a group of server operating systems.

Categories Operating systems Website https://microsoft.com/windowsserver Detected by BeaverCheck

Observations (2)

Server version exposed in headers

The Server header reveals 'IIS 10.0'. Exposing exact server versions helps attackers target known vulnerabilities. Consider configuring your server to hide version information.

→ Security

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%2Fshahoclimb.com)](https://beavercheck.com/sites/shahoclimb.com)
<a href="https://beavercheck.com/sites/shahoclimb.com"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fshahoclimb.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fshahoclimb.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 · 4h total → projected B (81)

Sprint 1: Quick Wins

+5

Highest ROI — low effort, high impact

3 findings 0h → C (78)
  • · Page weighs 4.4 MB (4.5 MB transferred)
  • · HSTS is enabled but max-age is short (2592000s, should be >= 31536000s)
  • · Cross-Origin-Opener-Policy header is missing

Sprint 2: Core Fixes

+3

Medium effort, high structural impact

2 findings 4h → B (81)
  • · Content-Security-Policy header is missing
  • · Cross-Origin-Embedder-Policy header is missing

Send Feedback