Skip to content
Recent Trends
Performance stable →
89
TTFB stable →
75ms
FCP stable →
2.3s
LCP stable →
3.3s
Scanned
2026-04-06 15:08 UTC
Worker
🇺🇸 New York
Duration
38.00s
Vs prev
Improved by +3

Audit overview

3 categories need attention: Security, and 2 others.

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

Page weighs 5.4 MB (4.0 MB transferred)

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

Performance › Page Weight Budget
Critical: 4

Soft 404: server returns HTTP 200 for non-existent pages

Soft 404s (HTTP 200 for missing pages) confuse Google — it indexes the 'not found' page as real content and ranks it.

Accessibility › 404 Error Page
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 3.3s 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.
Your LCP is 3.3s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
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

$750 investment → $7,666/month returns + USD 157,500 risk avoided

Investment
$750
7.5 h · 4 findings
Monthly returns
$7,666
$91,996/yr
Payback
0.1 mo
+12166% Y1
Regulatory risk avoided USD 157,500
Or — fix only the top 3 findings
$6500.1 mo payback · +14053% 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.
$50 — 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

7 barrier(s) likely increasing bounce by ~23%.

Barriers
7
1 crit 6 warn
Bounce delta
+23pp
added vs baseline
Score
72
B
Speed
1
Trust
2
Usability
0
Content
3
Nav
1
  • 3 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
  • Page loads in 3.3s
    Every additional 100ms above 2.5s costs conversions — you're 848ms over
    → Target <2.5s LCP: defer non-critical scripts and optimize the hero image
  • 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

$750 7.5 developer hours at $100/hr
Quick wins
$50 1 fixes in ~30 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

$6,069 / month at risk ~$72,834 / 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
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no privacy policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

Bounce-Rate Cost

$6,068 /mo

+22.6pp bounce · ~2,256 lost visitors/mo

CPC: USD 2.69

Bandwidth Waste

$1.00 /mo

12524.8 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~1.3 MB per page load
    Saves $1.00/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 4 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

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

2.30 s

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

3.35 s

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

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

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

3.36 s

Desktop

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

609 ms

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

810 ms

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.

609 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

814 ms

Categories

8
Avg score 74.1

How you compare

Where this site stands against peers running the same stack.

HSTS · 2601 peers
You 73
·
Avg 75
At average
0 50 100
Security P4Content P5Infrastructure P9Performance P68Compliance P33SEO P35Sustainability P59Accessibility P50

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

Better than 28% of HSTS sites See full HSTS benchmark →
Priority Hints · 1604 peers
You 73
·
Avg 74
At average
0 50 100
Content P2Security P8Infrastructure P9Compliance P17SEO P20Performance P78Sustainability P68Accessibility P49

Top 10% of Priority Hints sites score 96+ on Content; you're at 65 — closing this gap is the highest-leverage improvement.

Better than 31% of Priority Hints sites See full Priority Hints benchmark →

Technology stack

HSTS, hosted on Vercel, with Vercel Edge CDN

9 technologies detected 4 stack layers 2 with CPE identifier Enterprise

Stack Architecture

Analytics
Vercel Analytics Vercel Speed Insights
Framework
HSTS Priority Hints Svelte SvelteKit Vite
CDN
Vercel Edge
Hosting
Vercel

All Detected Technologies (9)

Categories CDN Website https://vercel.com Detected by BeaverCheck Evidence x-vercel-id: iad1::p6zlg-1775488082671-2395c1e64dc6

Vercel is a cloud platform for static frontends and serverless functions.

Categories PaaS Website https://vercel.com Detected by BeaverCheck Evidence Header: x-vercel-id, Server: Vercel

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

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

Svelte is a free and open-source front end compiler created by Rich Harris and maintained by the Svelte core team members.

Categories JavaScript frameworks Website https://svelte.dev Detected by BeaverCheck Evidence Script URL: https://kit.svelte.dev/_vercel/speed-insights/script.js
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

SvelteKit is the official Svelte framework for building web applications with a flexible filesystem-based routing.

Categories UI frameworks Website https://kit.svelte.dev Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Vite is a rapid development tool for modern web projects.

Categories Miscellaneous Website https://vitejs.dev Detected by BeaverCheck
Categories Analytics Website https://vercel.com/analytics Detected by BeaverCheck

Vercel Speed Insights provides you with a detailed view of your website's performance metrics, based on Core Web Vitals.

Categories Analytics Website https://vercel.com/docs/speed-insights Detected by BeaverCheck

Observations (2)

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.

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%2Fkit.svelte.dev)](https://beavercheck.com/results/3164ed15-5981-44d2-8183-2a0bb7a406a5)
<a href="https://beavercheck.com/results/3164ed15-5981-44d2-8183-2a0bb7a406a5"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fkit.svelte.dev" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fkit.svelte.dev

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

Sprint 1: Quick Wins

+4

Highest ROI — low effort, high impact

2 findings 0h → C (77)
  • · Page weighs 5.4 MB (4.0 MB transferred)
  • · Soft 404: server returns HTTP 200 for non-existent pages

Sprint 2: Core Fixes

+4

Medium effort, high structural impact

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

Send Feedback