Skip to content
Scanned
2026-07-27 18:35 UTC
Worker
🇸🇬 Singapore
Duration
43.00s
Vs prev

Global Performance

6/6 locations

Acceptable global latency — average 294ms across 6 locations, fastest from Singapore (14ms), slowest from New York (614ms). Netlify in front. 1 location above the 500ms target.

Singapore - Singapore
Full audit
14ms
DNS 6ms · TLS 3ms
Netherlands - Amsterdam
298ms
DNS 6ms · TLS 9ms
United Stated - New York
614ms
DNS 6ms · TLS 10ms
Spain - Madrid
382ms
DNS 30ms · TLS 30ms
Brazil - Sao Paulo
292ms
DNS 6ms · TLS 5ms
United States - Santa Clara
165ms
DNS 8ms · TLS 4ms
CDN: Netlify · Avg TTFB: 294ms · Cache: public,max-age=0,must-revalidate

Audit overview

Compliance needs attention; the rest of the categories are in good shape.

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

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

No H1 heading found

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Accessibility › Heading Hierarchy
Warning: 4

9 third-party resources (44% 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: 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 performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 6.9s 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.
3 security gaps detected — browsers may warn visitors about your site.
1 accessibility issue excludes users who rely on assistive technology.
Your LCP is 6.9s — 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

$717 investment → $13,096/month returns + USD 157,500 risk avoided

Investment
$717
7.2 h · 4 findings
Monthly returns
$13,096
$157,152/yr
Payback
0.1 mo
+21828% Y1
Regulatory risk avoided USD 157,500
Or — fix only the top 3 findings
$6170.0 mo payback · +25384% 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.
$17 — 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
0
Content
3
Nav
2
  • Page takes 6.9s to load
    Users abandon at ~3s — you're 4.4s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • 5 broken link(s) on the page
    Clicks land on 404s — trust drops and the session often ends
    → Fix or remove the broken destinations surfaced on the Content tab
  • High main-thread blocking time
    Page is non-interactive for 313ms after first paint
    → Defer third-party scripts and split large bundles
  • 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

$717 7.2 developer hours at $100/hr
Quick wins
$17 1 fixes in ~10 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,933 / 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
  • Skip navigation link is missing (WCAG 2.4.1)
    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.18 /mo

2195.6 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~220 KB per page load
    Saves $0.18/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 3 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

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

5.04 s

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

6.90 s

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

313 ms

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

0.003

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

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

8.14 s

Desktop

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

1.04 s

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

1.05 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.463

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

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

1.05 s

Categories

8
Avg score 82.6

How you compare

Where this site stands against peers running the same stack.

HSTS · 2655 peers
You 84
·
Avg 75
+9 above average
0 50 100
Accessibility P94Compliance P7Security P90Performance P84Sustainability P83Content P30SEO P34Infrastructure P56

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

Better than 91% of HSTS sites See full HSTS benchmark →
Lucide · 89 peers
You 84
·
Avg 78
+6 above average
0 50 100
Better than 79% of Lucide sites See full Lucide benchmark →

Technology stack

HSTS, with Netlify CDN

7 technologies detected 2 stack layers 1 with CPE identifier Complex

Stack Architecture

Framework
HSTS Lucide React React Router 7.18.1 Tailwind CSS
CDN
Netlify Netlify CDN

All Detected Technologies (7)

Netlify providers hosting and server-less backend services for web applications and static websites.

Categories PaaS, CDN Website https://www.netlify.com/ Detected by BeaverCheck Evidence Header: x-nf-request-id, Server: Netlify, Domain: .netlify.app
Categories CDN Website https://www.netlify.com Detected by BeaverCheck Evidence x-nf-request-id: 01KYJDQWPERY45XWP9RHS6FR0A

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

Lucide is an open-source icon library that provides 1000+ vector (svg) files for displaying icons and symbols in digital and non-digital projects.

Categories Font scripts Website https://lucide.dev Detected by BeaverCheck

React is an open-source JavaScript library for building user interfaces or UI components.

Categories JavaScript frameworks Website https://reactjs.org Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

React Router provides declarative routing for React.

Categories JavaScript frameworks Website https://reactrouter.com Detected by BeaverCheck
Categories Framework Website https://tailwindcss.com Detected by BeaverCheck Evidence Found 36 unique Tailwind utility classes in HTML

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

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

Sprint 1: Quick Wins

+3

Highest ROI — low effort, high impact

2 findings 0h → B (87)
  • · No H1 heading found
  • · 9 third-party resources (44% of weight)

Sprint 2: Core Fixes

+4

Medium effort, high structural impact

3 findings 7h → A (91)
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found
  • · Cross-Origin-Embedder-Policy header is missing

Send Feedback