Global Performance
6/6 locations ✓High global latency — average 2208ms across 6 locations, fastest from Santa Clara (797ms), slowest from Singapore (6843ms). No CDN detected. Cache-Control disables caching (no-store). 6 locations above the 500ms target.
Audit overview
Compliance and Sustainability need attention; the other categories are in good shape.
Fix Priority Matrix
5 findingsQuick Wins
2High impact, low effort — start here.
Strategic
3High 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)
/.svn/entries is publicly accessible
Sensitive resource publicly accessible — restrict access or remove.
Content-Security-Policy header is missing
Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.
No Content-Security-Policy header found
Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.
Page weighs 12.5 MB (4.9 MB transferred)
Informational: total page weight (uncompressed) and bytes actually transferred over the wire.
17 link(s) with no accessible text
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
¥2,625 investment → ¥31,615/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
9 barrier(s) likely increasing bounce by ~32%.
- Page takes 25.4s to loadUsers abandon at ~3s — you're 22.9s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 1.9sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- 7 broken link(s) on the pageClicks land on 404s — trust drops and the session often ends→ Fix or remove the broken destinations surfaced on the Content tab
- 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
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
- No privacy policy link detectedPIPL: CNY 100,000 – CNY 50,000,000
- Privacy Policy not detectedPIPL: CNY 100,000 – CNY 50,000,000
Bounce-Rate Cost
¥31,606 /mo
+31.6pp bounce · ~3,161 lost visitors/mo
CPC: CNY 10.00
Bandwidth Waste
¥8.78 /mo
15363.2 MB/mo × 0.571 CNY/GB
- Optimize transfer: save ~1.5 MB per page loadSaves ¥8.78/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 5 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.
3.98 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
25.44 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.93 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.036
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
10.22 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.
27.96 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.74 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
5.41 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
192 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.004
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
4.31 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.
6.61 s
Categories
8Performance
Page weighs 12.5 MB (4.9 MB transferred)
Security
/.svn/entries is publicly accessible
Accessibility
17 link(s) with no accessible text
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 core-js sites score 85+ on Compliance; you're at 67 — closing this gap is the highest-leverage improvement.
Top 10% of HSTS sites score 95+ on Infrastructure; you're at 79 — closing this gap is the highest-leverage improvement.
Technology stack
HSTS, on styled-components, hosted on Tengine, with Alibaba Cloud CDN CDN
Stack Architecture
Open Graph 
React 19.1.1
Tanx 
Three.js 160
core-js 2.6.12
styled-components 5.3.11
Alibaba Cloud CDN 
Tengine All Detected Technologies (9)
Alibaba Cloud CDN is a global network of servers designed to deliver high-performance, low-latency content to users around the world. It is a cloud-based service provided by Alibaba Cloud, a subsidiary of the Alibaba Group, that enables businesses to accelerate the delivery of their web content, including images, videos, and static files, to end-users.
Tengine is a web server which is based on the Nginx HTTP server.
Styled components is a CSS-in-JS styling framework that uses tagged template literals in JavaScript.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
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.
Tanx is a platform for media resource management and business-cooperation workflows.
Three.js is a cross-browser JavaScript library and application programming interface used to create and display animated 3D computer graphics in a web browser using WebGL.
core-js is a modular standard library for JavaScript, with polyfills for cutting-edge ECMAScript features.
Observations (3)
Runtime exposed via X-Powered-By header
The X-Powered-By header reveals 'styled-components 5.3.11'. Remove this header in production to reduce information leakage.
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.
This badge auto-updates with your latest scan result.
[](https://beavercheck.com/results/8b1c46b6-3b41-4b69-8172-97445dff8c52)<a href="https://beavercheck.com/results/8b1c46b6-3b41-4b69-8172-97445dff8c52"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fcn.aliyun.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fcn.aliyun.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 · 8h total → projected B (85)
Sprint 1: Quick Wins
+4Highest ROI — low effort, high impact
- · Page weighs 12.5 MB (4.9 MB transferred)
- · 17 link(s) with no accessible text
Sprint 2: Core Fixes
+5Medium effort, high structural impact
- · /.svn/entries is publicly accessible
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found