Audit overview
3 categories need attention: Security, and 2 others.
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)
Content-Security-Policy header is missing
Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.
HSTS header is missing
Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.
No Content-Security-Policy header found
Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.
26 image-only link(s) without alt text
Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.
3 control(s) without accessible label
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
¥2,713 investment → ¥63,484/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
11 barrier(s) likely increasing bounce by ~40%.
- Page takes 8.3s to loadUsers abandon at ~3s — you're 5.8s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- 3 form field(s) without a labelScreen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes→ Associate every input with a visible <label for="…">; add autocomplete attributes
- No viewport meta tagMobile browsers render at desktop width and shrink — text unreadable, tap targets miniature→ Add <meta name="viewport" content="width=device-width, initial-scale=1">
- 8 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
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
¥40,236 /mo
+40.2pp bounce · ~4,024 lost visitors/mo
CPC: CNY 10.00
Bandwidth Waste
¥1.09 /mo
1911.7 MB/mo × 0.571 CNY/GB
- Optimize transfer: save ~191 KB per page loadSaves ¥1.09/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
Categories
8Performance
All checks pass
Security
Content-Security-Policy header is missing
Accessibility
26 image-only link(s) without alt 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 jQuery sites score 76+ on Security; you're at 57 — closing this gap is the highest-leverage improvement.
Technology stack
RequireJS 2.1.11, on OpenResty, with Nginx CDN
Stack Architecture
RequireJS 2.1.11
Vue.js 3.3.9
jQuery 1.8.3
OpenResty 1.15.8.3
Nginx All Detected Technologies (5)
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
OpenResty is a web platform based on nginx which can run Lua scripts using its LuaJIT engine.
RequireJS is a JavaScript library and file loader which manages the dependencies between JavaScript files and in modular programming.
Vue.js is an open-source model–view–viewmodel JavaScript framework for building user interfaces and single-page applications.
jQuery is a JavaScript library which is a free, open-source software designed to simplify HTML DOM tree traversal and manipulation, as well as event handling, CSS animation, and Ajax.
Observations (4)
Server version exposed in headers
The Server header reveals 'OpenResty 1.15.8.3'. Exposing exact server versions helps attackers target known vulnerabilities. Consider configuring your server to hide version information.
jQuery loaded alongside a modern framework
Both jQuery and Vue.js are loaded. Modern frameworks handle DOM manipulation natively. jQuery may be unnecessary and adds ~30KB to the page weight. Check the Performance tab for bundle analysis.
No build tool detected
A framework (RequireJS) 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.
jQuery version may be outdated
Detected jQuery 1.8.3. The current major version is 3. Consider updating for security patches and new features.
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/75e2557a-8183-478a-907f-6678b1169253)<a href="https://beavercheck.com/results/75e2557a-8183-478a-907f-6678b1169253"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fso.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fso.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 C (78)
Sprint 1: Quick Wins
+4Highest ROI — low effort, high impact
- · HSTS header is missing
- · 26 image-only link(s) without alt text
Sprint 2: Core Fixes
+5Medium effort, high structural impact
- · 3 control(s) without accessible label
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found