Skip to content
Recent Trends
Performance stable →
97
TTFB stable →
34ms
FCP stable →
2.0s
LCP stable →
2.1s
Scanned
2026-07-20 07:26 UTC
Worker
🇺🇸 New York
Duration
37.00s
Vs prev
Improved by +7

Global Performance

6/6 locations

Excellent global latency — average 38ms across 6 locations, fastest from Sao Paulo (16ms), slowest from Madrid (114ms). No CDN detected.

United Stated - New York
Full audit
34ms
DNS 10ms · TLS 13ms
United States - Santa Clara
26ms
DNS 8ms · TLS 9ms
Brazil - Sao Paulo
16ms
DNS 5ms · TLS 8ms
Spain - Madrid
114ms
DNS 29ms · TLS 32ms
Singapore - Singapore
17ms
DNS 6ms · TLS 9ms
Netherlands - Amsterdam
17ms
DNS 5ms · TLS 9ms
CDN: No CDN · Avg TTFB: 38ms · Cache: max-age=2592000

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

2 render-blocking <script src> tag(s) without async/defer

Performance issues directly impact user engagement and conversion rates.

Performance › JavaScript Blocking
Warning: 4

6 third-party resources (98% 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

Cookie 'GeoIP' has no SameSite attribute

Without SameSite, cookies ride along on cross-site requests — enabling CSRF attacks that SameSite=Lax blocks for free.

Security › Cookie Security
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. The 2 performance issues below shape how fast users perceive your page. 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 performance issues — Akamai's research found 53% of mobile users abandon pages over 3s.

Business case

What fixing the audit's findings is worth -- and what ignoring them keeps costing.

Return on investment

$825 investment → $4,024/month returns + USD 157,500 risk avoided

Investment
$825
8.3 h · 4 findings
Monthly returns
$4,024
$48,294/yr
Payback
0.2 mo
+5754% Y1
Regulatory risk avoided USD 157,500
Or — fix only the top 3 findings
$8000.2 mo payback · +5937% 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.
$25 — 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

6 barrier(s) likely increasing bounce by ~15%.

Barriers
6
6 warn
Bounce delta
+15pp
added vs baseline
Score
82
B
Speed
0
Trust
1
Usability
0
Content
3
Nav
2
  • 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
  • No structured data
    No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
    → Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
  • Thin content
    Under 300 words — visitors bounce looking for substance, search engines rank competitors first
    → Add a substantive FAQ, product detail, or case-study section
  • No skip-to-content link
    Keyboard and screen-reader users must tab through the entire header on every page
    → Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

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

Remediation cost

$825 8.3 developer hours at $100/hr
Quick wins
$25 1 fixes in ~15 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

$4,024 / month at risk ~$48,294 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • 5 non-essential cookie(s) set without consent banner
    CCPA/CPRA: USD 2,500 – USD 7,500
  • 2 tracking cookie(s) set before consent interaction
    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

$4,024 /mo

+15.0pp bounce · ~1,496 lost visitors/mo

CPC: USD 2.69

Bandwidth Waste

$0.02 /mo

219.1 MB/mo × 0.080 USD/GB

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

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

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

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

1.96 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.12 s

Desktop

100
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.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
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.

542 ms

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

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

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

553 ms

Categories

8
Avg score 81.0

How you compare

Where this site stands against peers running the same stack.

Google Search Console · 3916 peers
You 84
·
Avg 73
+11 above average
0 50 100
Compliance P1Accessibility P98Security P96Performance P90Sustainability P80Infrastructure P23SEO P26Content P34

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

Better than 96% of Google Search Console sites See full Google Search Console benchmark →
HSTS · 2639 peers
You 84
·
Avg 75
+9 above average
0 50 100
Compliance P3Accessibility P97Security P91Performance P84Infrastructure P18SEO P22Sustainability P75Content P30

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

Better than 91% of HSTS sites See full HSTS benchmark →

Technology stack

Google Search Console

2 technologies detected 1 stack layers Minimal

Stack Architecture

Framework
Google Search Console HSTS

All Detected Technologies (2)

Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=djm1t6aP_Yt6WNSj834eVqD83qomWtLP0_1NveYTBfU

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

Observations (2)

No build tool detected

A framework (Google Search Console) 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 2 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%2Fwikibooks.org)](https://beavercheck.com/sites/wikibooks.org)
<a href="https://beavercheck.com/sites/wikibooks.org"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwikibooks.org" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwikibooks.org

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

Sprint 1: Quick Wins

+2

Highest ROI — low effort, high impact

2 findings 0h → B (86)
  • · 6 third-party resources (98% of weight)
  • · Cookie 'GeoIP' has no SameSite attribute

Sprint 2: Core Fixes

+3

Medium effort, high structural impact

3 findings 8h → B (89)
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found
  • · 2 render-blocking <script src> tag(s) without async/defer

Send Feedback