Skip to content
https://nu11cyber.com Export & share
Recent Trends
Performance stable →
95
TTFB stable →
747ms
FCP stable →
1.4s
LCP stable →
2.8s
Scanned
2026-05-28 07:13 UTC
Worker
🇺🇸 Santa Clara
Duration
45.00s
Vs prev
Improved by +3

Global Performance

6/6 locations

High global latency — average 663ms across 6 locations, fastest from Singapore (295ms), slowest from Sao Paulo (1127ms). Cloudflare edge cache (DYNAMIC). Cache-Control disables caching (no-store). 5 locations above the 500ms target.

United States - Santa Clara
Full audit
531ms
DNS 9ms · TLS 10ms
Singapore - Singapore
295ms
DNS 143ms · TLS 9ms
Spain - Madrid
731ms
DNS 40ms · TLS 22ms
Netherlands - Amsterdam
607ms
DNS 12ms · TLS 11ms
Brazil - Sao Paulo
1127ms
DNS 170ms · TLS 7ms
United Stated - New York
686ms
DNS 8ms · TLS 11ms
CDN: Cloudflare (DYNAMIC) · Avg TTFB: 663ms · Cache: no-store

Audit overview

All categories sit comfortably above the 70 threshold; this is a clean audit.

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

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

1 publicly-accessible JavaScript source map(s)

Source maps reveal original source code (variable names, comments, file structure) and are shipped to production by mistake almost universally. The standard fix is a one-line build-tool config change.

Security › Source Map Exposure
Warning: 5

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

Performance issues directly impact user engagement and conversion rates.

Performance › JavaScript Blocking
What fixing these means. Your site is in great shape. The remaining improvements are refinements rather than critical fixes. Your LCP of 3.2s 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 3.2s — 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

¥3,150 investment → ¥43,185/month returns + CNY 50,000,000 risk avoided

Investment
¥3,150
9.0 h · 5 findings
Monthly returns
¥43,185
¥518,220/yr
Payback
0.1 mo
+16351% Y1
Regulatory risk avoided CNY 50,000,000
Or — fix only the top 3 findings
¥2,2750.1 mo payback · +22679% 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.
¥350 — 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 ~15%.

Barriers
5
5 warn
Bounce delta
+15pp
added vs baseline
Score
85
A
Speed
1
Trust
2
Usability
0
Content
1
Nav
1
  • Page loads in 3.2s
    Every additional 100ms above 2.5s costs conversions — you're 688ms 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
  • 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

¥3,150 9.0 developer hours at ¥350/hr
Quick wins
¥350 2 fixes in ~60 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

¥38,370 / month at risk ~¥460,443 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

¥50,000,000

PIPL
  • 1 non-essential cookie(s) set without consent banner
    PIPL: CNY 100,000 – CNY 50,000,000

Bounce-Rate Cost

¥38,370 /mo

+15.3pp bounce · ~1,535 lost visitors/mo

CPC: CNY 25.00

Bandwidth Waste

¥0.35 /mo

611.0 MB/mo × 0.571 CNY/GB

  • Optimize transfer: save ~61 KB per page load
    Saves ¥0.35/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

86
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.
77
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.69 s

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

3.19 s

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

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

4.62 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.19 s

Desktop

96
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.
77
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.

873 ms

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

1.31 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.002

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

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

1.31 s

Categories

8
Avg score 87.4

How you compare

Where this site stands against peers running the same stack.

HSTS · 2531 peers
You 87
·
Avg 75
+12 above average
0 50 100
Sustainability P96Performance P95Security P93Content P93Accessibility P91Infrastructure P11Compliance P18SEO P43

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

Better than 95% of HSTS sites See full HSTS benchmark →
HTTP/3 · 1485 peers
You 87
·
Avg 75
+12 above average
0 50 100
Performance P95Security P95Content P94Sustainability P93Accessibility P92Infrastructure P9Compliance P16SEO P52

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

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

Technology stack

HSTS, with Cloudflare CDN

6 technologies detected 2 stack layers 2 with CPE identifier Complex

Stack Architecture

Framework
HSTS HTTP/3 Open Graph React 18.3.1
CDN
Cloudflare unpkg

All Detected Technologies (6)

Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.

Categories CDN Website https://www.cloudflare.com Detected by BeaverCheck Evidence Server header in redirect: cloudflare
This technology has a CPE identifier — check for known vulnerabilities Search NVD →
Categories CDN Detected by BeaverCheck · Medium Evidence Script URL contains unpkg.com: https://unpkg.com/react@18/umd/react.production.min.js

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

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

Open Graph is a protocol that is used to integrate any web page into the social graph.

Categories Miscellaneous Website https://ogp.me 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 Evidence Script URL: https://unpkg.com/react@18/umd/react.production.min.js, Script URL: https://unpkg.com/react-dom@18/umd/react-dom.production.min.js
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

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%2Fnu11cyber.com)](https://beavercheck.com/results/8308e8d9-623b-4de8-98ec-7ec314f76476)
<a href="https://beavercheck.com/results/8308e8d9-623b-4de8-98ec-7ec314f76476"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fnu11cyber.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fnu11cyber.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 · 9h total → projected A (93)

Sprint 1: Quick Wins

+2

Highest ROI — low effort, high impact

2 findings 1h → B (89)
  • · Soft 404: server returns HTTP 200 for non-existent pages
  • · 1 publicly-accessible JavaScript source map(s)

Sprint 2: Core Fixes

+4

Medium effort, high structural impact

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

Send Feedback