Skip to content
Scanned
2026-05-10 12:46 UTC
Worker
🇺🇸 New York
Duration
1.1m
Vs prev

Global Performance

6/6 locations

High global latency — average 1058ms across 6 locations, fastest from Santa Clara (471ms), slowest from Sao Paulo (1532ms). No CDN detected. Cache-Control header is missing. 5 locations above the 500ms target.

United Stated - New York
Full audit
1455ms
DNS 836ms · TLS 206ms
United States - Santa Clara
471ms
DNS 13ms · TLS 152ms
Brazil - Sao Paulo
1532ms
DNS 541ms · TLS 332ms
Singapore - Singapore
525ms
DNS 205ms · TLS 123ms
Spain - Madrid
986ms
DNS 173ms · TLS 271ms
Netherlands - Amsterdam
1375ms
DNS 608ms · TLS 258ms
CDN: No CDN · Avg TTFB: 1058ms · 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

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

Page body has only 12 chars of text -- likely empty / placeholder

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

Security › Empty Page Detection
Critical: 5

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
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.
4 security gaps detected — browsers may warn visitors about your site.
1 accessibility issue excludes 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

AUD 752 investment → AUD 19,359/month returns + AUD 50,200,000 risk avoided

Investment
AUD 752
6.8 h · 5 findings
Monthly returns
AUD 19,359
AUD 232,313/yr
Payback
0.0 mo
+30806% Y1
Regulatory risk avoided AUD 50,200,000
Or — fix only the top 3 findings
AUD 6880.0 mo payback · +33691% 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.
AUD 92 — 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 ~35%.

Barriers
8
2 crit 6 warn
Bounce delta
+35pp
added vs baseline
Score
62
C
Speed
1
Trust
2
Usability
1
Content
3
Nav
1
  • Page takes 7.1s to load
    Users abandon at ~3s — you're 4.6s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • 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
  • 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

A$752 6.8 developer hours at A$110/hr
Quick wins
A$92 3 fixes in ~50 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.

A$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

Warning:Cost of inaction

AUD 12,402 / month at risk ~AUD 148,826 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

AUD 50,200,000

Privacy Act 1988DDA
  • No privacy policy link detected
    Privacy Act 1988: AUD 66,000 – AUD 50,000,000
  • Privacy Policy not detected
    Privacy Act 1988: AUD 66,000 – AUD 50,000,000
  • No <main> landmark found
    DDA: AUD 5,000 – AUD 200,000

Bounce-Rate Cost

AUD 12,402 /mo

+35.4pp bounce · ~3,543 lost visitors/mo

CPC: AUD 3.50

Bandwidth Waste

AUD 0.30 /mo

2434.8 MB/mo × 0.123 AUD/GB

  • Optimize transfer: save ~243 KB per page load
    Saves AUD 0.30/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

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

3.05 s

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

7.10 s

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

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

9.06 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.49 s

Desktop

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

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

2.48 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.000

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

3.15 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.48 s

Categories

8
Avg score 77.9

How you compare

Where this site stands against peers running the same stack.

HTTP/3 · 1498 peers
You 80
·
Avg 75
At average
0 50 100
Compliance P2Infrastructure P5Security P87Accessibility P85Performance P78SEO P26Content P40Sustainability P51

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

Better than 82% of HTTP/3 sites See full HTTP/3 benchmark →

Technology stack

HTTP/3

1 technologies detected 1 stack layers Minimal

Stack Architecture

Framework
HTTP/3

All Detected Technologies (1)

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 (2)

No build tool detected

A framework (HTTP/3) 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.

Minimal technology footprint

Only 1 technologies detected. This suggests a simple setup with minimal dependencies — excellent for performance and security.

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%2FNeenawcar.com)](https://beavercheck.com/results/6232ee12-4271-47f6-9c0d-40e85d0ff10d)
<a href="https://beavercheck.com/results/6232ee12-4271-47f6-9c0d-40e85d0ff10d"><img src="https://beavercheck.com/badge?url=https%3A%2F%2FNeenawcar.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2FNeenawcar.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 B (86)

Sprint 1: Quick Wins

+6

Highest ROI — low effort, high impact

3 findings 1h → B (86)
  • · Missing <html lang> attribute (WCAG 3.1.1)
  • · HSTS header is missing
  • · Page body has only 12 chars of text -- likely empty / placeholder

Sprint 2: Core Fixes

Medium effort, high structural impact

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

Send Feedback