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 04:48 UTC
Worker
🇪🇸 Madrid
Duration
44.00s
Vs prev

Global Performance

6/6 locations

High global latency — average 765ms across 6 locations, fastest from Singapore (343ms), slowest from Sao Paulo (1319ms). No CDN detected. Cache-Control disables caching (no-store). 5 locations above the 500ms target.

Spain - Madrid
Full audit
821ms
DNS 54ms · TLS 256ms
United Stated - New York
647ms
DNS 31ms · TLS 206ms
Netherlands - Amsterdam
680ms
DNS 99ms · TLS 194ms
United States - Santa Clara
780ms
DNS 313ms · TLS 157ms
Singapore - Singapore
343ms
DNS 227ms · TLS 40ms
Brazil - Sao Paulo
1319ms
DNS 401ms · TLS 308ms
CDN: No CDN · Avg TTFB: 765ms · Cache: no-store

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

Cookie 'sl-session' is missing the Secure flag

A cookie without the Secure flag can leak over HTTP — in HSTS-protected sites, this is still a defense-in-depth gap.

Security › Cookie Security
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

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

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

¥2,538 investment → ¥51,998/month returns + CNY 50,000,000 risk avoided

Investment
¥2,538
7.3 h · 5 findings
Monthly returns
¥51,998
¥623,980/yr
Payback
0.0 mo
+24490% Y1
Regulatory risk avoided CNY 50,000,000
Or — fix only the top 3 findings
¥2,1880.0 mo payback · +28425% 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.
¥438 — 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 ~18%.

Barriers
5
5 warn
Bounce delta
+18pp
added vs baseline
Score
85
A
Speed
1
Trust
1
Usability
1
Content
1
Nav
1
  • Page loads in 3.6s
    Every additional 100ms above 2.5s costs conversions — you're 1.1s over
    → Target <2.5s LCP: defer non-critical scripts and optimize the hero image
  • 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
  • Layout shifts during page load
    Content movement causes mis-clicks on CTAs and form fields
    → Add width/height to images; reserve space for late-loading embeds
  • 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

¥2,538 7.3 developer hours at ¥350/hr
Quick wins
¥438 3 fixes in ~75 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

¥43,957 / month at risk ~¥527,487 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

¥50,000,000

PIPL
  • No privacy policy link detected
    PIPL: CNY 100,000 – CNY 50,000,000
  • 1 non-essential cookie(s) set without consent banner
    PIPL: CNY 100,000 – CNY 50,000,000
  • Privacy Policy not detected
    PIPL: CNY 100,000 – CNY 50,000,000

Bounce-Rate Cost

¥43,957 /mo

+17.6pp bounce · ~1,758 lost visitors/mo

CPC: CNY 25.00

Bandwidth Waste

¥0.32 /mo

560.8 MB/mo × 0.571 CNY/GB

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

79
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.
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.01 s

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

3.65 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.140

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

3.19 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.65 s

Desktop

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

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

1.44 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.087

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

1.39 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.44 s

Categories

8
Avg score 82.8

How you compare

Where this site stands against peers running the same stack.

HSTS · 2531 peers
You 83
·
Avg 75
+8 above average
0 50 100
Compliance P1Accessibility P91Performance P90Content P84Security P83Infrastructure P18Sustainability P76SEO P31

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

Better than 91% of HSTS sites See full HSTS benchmark →
HTTP/3 · 1485 peers
You 83
·
Avg 75
+8 above average
0 50 100
Compliance P1Accessibility P92Performance P90Infrastructure P14Security P84Content P83Sustainability P62SEO P42

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

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

Technology stack

HSTS, with unpkg CDN

5 technologies detected 2 stack layers 1 with CPE identifier Standard

Stack Architecture

Framework
HSTS HTTP/3 Open Graph React 18.3.1
CDN
unpkg

All Detected Technologies (5)

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/302a1f1a-3f9b-4a2d-a839-2fd19851b8f8)
<a href="https://beavercheck.com/results/302a1f1a-3f9b-4a2d-a839-2fd19851b8f8"><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 · 7h total → projected A (90)

Sprint 1: Quick Wins

+5

Highest ROI — low effort, high impact

3 findings 1h → B (88)
  • · Cookie 'sl-session' is missing the Secure flag
  • · Soft 404: server returns HTTP 200 for non-existent pages
  • · 1 publicly-accessible JavaScript source map(s)

Sprint 2: Core Fixes

+2

Medium effort, high structural impact

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

Send Feedback