Global Performance
6/6 locations ✓High global latency — average 2331ms across 6 locations, fastest from Santa Clara (493ms), slowest from Singapore (7307ms). Cloudflare edge cache (DYNAMIC). Cache-Control disables caching (no-store). 5 locations above the 500ms target.
Audit overview
All categories sit comfortably above the 70 threshold; this is a clean audit.
Fix Priority Matrix
5 findingsQuick Wins
4High impact, low effort — start here.
Strategic
1High impact, requires investment.
Easy Improvements
0Small gains, minimal effort.
Nothing in this quadrant — good news.
Deprioritize
0Low impact, high effort — do last.
Nothing in this quadrant — good news.
Screenshots
Top Priorities (5)
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.
2 render-blocking <script src> tag(s) without async/defer
Performance issues directly impact user engagement and conversion rates.
HSTS max-age is too short (0s, should be ≥ 31536000s)
Short HSTS max-age leaves a downgrade-attack window every time the cache expires — set ≥ 1 year.
Unattributable: 408ms CPU time
Informational: CPU time spent on this resource. Total >1s is a perf budget violation.
frame-ancestors directive is missing
Security gaps expose your site and users to attacks, eroding trust.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
¥1,079 investment → ¥52,249/month returns + CNY 50,000,000 risk avoided
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 ~19%.
- Page loads in 3.3sEvery additional 100ms above 2.5s costs conversions — you're 805ms over→ Target <2.5s LCP: defer non-critical scripts and optimize the hero image
- No HSTS headerReturning visitors are briefly exposed to downgrade attacks on first request→ Set Strict-Transport-Security: max-age=31536000; includeSubDomains
- No Content-Security-Policy headerHigher 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 loadContent movement causes mis-clicks on CTAs and form fields→ Add width/height to images; reserve space for late-loading embeds
- Thin contentUnder 300 words — visitors bounce looking for substance, search engines rank competitors first→ Add a substantive FAQ, product detail, or case-study section
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
Remediation cost
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.
Rates reflect fully-loaded developer cost including overhead
Warning:Cost of inaction
Compliance Risk
¥50,000,000
- 1 non-essential cookie(s) set without consent bannerPIPL: CNY 100,000 – CNY 50,000,000
Bounce-Rate Cost
¥46,614 /mo
+18.6pp bounce · ~1,865 lost visitors/mo
CPC: CNY 25.00
Bandwidth Waste
¥0.56 /mo
985.6 MB/mo × 0.571 CNY/GB
- Optimize transfer: save ~99 KB per page loadSaves ¥0.56/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.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 1 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
Your data stays in your browser — nothing is sent to our servers
Lighthouse
Mobile
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
2.52 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.30 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.141
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.55 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.30 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
710 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
804 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.050
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
875 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.
804 ms
Categories
8Performance
2 render-blocking <script src> tag(s) without async/defer
Security
HSTS max-age is too short (0s, should be ≥ 31536000s)
Accessibility
Soft 404: server returns HTTP 200 for non-existent pages
SEO
All checks pass
Infrastructure
All checks pass
Compliance
All checks pass
Content
All checks pass
Sustainability
All checks pass
How you compare
Where this site stands against peers running the same stack.
Top 10% of HSTS sites score 96+ on SEO; you're at 91 — closing this gap is the highest-leverage improvement.
Top 10% of HTTP/3 sites score 96+ on SEO; you're at 91 — closing this gap is the highest-leverage improvement.
Technology stack
HSTS, with Cloudflare CDN
Stack Architecture
HTTP/3 
Open Graph 
React 18.3.1
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.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Open Graph is a protocol that is used to integrate any web page into the social graph.
React is an open-source JavaScript library for building user interfaces or UI components.
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.
This badge auto-updates with your latest scan result.
[](https://beavercheck.com/results/a87f096e-a6a9-44e9-95e1-e5ec7efff691)<a href="https://beavercheck.com/results/a87f096e-a6a9-44e9-95e1-e5ec7efff691"><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.comExport & share
Download the audit, share with your team, or grab a fix plan ready to copy into your tracker.
Copies markdown to clipboard
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 · 3h total → projected A+ (97)
Sprint 1: Quick Wins
+4Highest ROI — low effort, high impact
- · Soft 404: server returns HTTP 200 for non-existent pages
- · Unattributable: 408ms CPU time
- · HSTS max-age is too short (0s, should be ≥ 31536000s)
- · frame-ancestors directive is missing
Sprint 2: Core Fixes
Medium effort, high structural impact
- · 2 render-blocking <script src> tag(s) without async/defer