Audit overview
4 categories need attention: Security, and 3 others.
Fix Priority Matrix
5 findingsQuick Wins
3High impact, low effort — start here.
Strategic
2High 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)
4 control(s) without accessible label
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
48 image-in-link without alt text
Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.
53 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.
69 image(s) missing alt attribute
Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.
9 button(s) with no accessible text
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
¥1,400 investment → ¥42,100/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
12 barrier(s) likely increasing bounce by ~42%.
- Page takes 22.5s to loadUsers abandon at ~3s — you're 20.0s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 7.6sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- Severe layout shift during page loadUsers mis-click when content jumps — converting intent into frustration→ Reserve space for images, ads, and embeds with explicit width/height
- 4 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">
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
- Trackers detected but no cookie policy foundPIPL: CNY 100,000 – CNY 50,000,000
- Trackers detected but no privacy policy foundPIPL: CNY 100,000 – CNY 50,000,000
Bounce-Rate Cost
¥42,094 /mo
+42.1pp bounce · ~4,209 lost visitors/mo
CPC: CNY 10.00
Bandwidth Waste
¥5.41 /mo
9471.2 MB/mo × 0.571 CNY/GB
- Optimize transfer: save ~947 KB per page loadSaves ¥5.41/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.
11.47 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
22.50 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
7.60 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.331
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
11.68 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.
23.68 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
5.28 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
16.57 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
8.81 s
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.
12.74 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.
16.57 s
Categories
8Performance
All checks pass
Security
All checks pass
Accessibility
4 control(s) without accessible label
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 71+ on Accessibility; you're at 29 — closing this gap is the highest-leverage improvement.
Technology stack
Day.js
Stack Architecture
Day.js 
DreamWeaver Google Search Console HSTS 
Hammer.js 2.0.8
Lodash 4.17.21
OWL Carousel 
Open Graph 
core-js 3.32.0
jQuery 3.6.0 jQuery Migrate 3.4.0
jQuery UI 1.13.2All Detected Technologies (12)
Dreamweaver is a development tool for creating, publishing, and managing websites and mobile content.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Hammer.js is a JavaScript library for adding touch gestures like swipe, pinch, and rotate to web applications.
Lodash is a JavaScript library which provides utility functions for common programming tasks using the functional programming paradigm.
OWL Carousel is an enabled jQuery plugin that lets you create responsive carousel sliders.
Open Graph is a protocol that is used to integrate any web page into the social graph.
core-js is a modular standard library for JavaScript, with polyfills for cutting-edge ECMAScript features.
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.
Query Migrate is a javascript library that allows you to preserve the compatibility of your jQuery code developed for versions of jQuery older than 1.9.
jQuery UI is a collection of GUI widgets, animated visual effects, and themes implemented with jQuery, Cascading Style Sheets, and HTML.
Observations (2)
No build tool detected
A framework (Day.js) 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
12 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/d61cc5a3-1b7f-4e9f-840c-48b53c840d3d)<a href="https://beavercheck.com/results/d61cc5a3-1b7f-4e9f-840c-48b53c840d3d"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ficbc.com.cn" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Ficbc.com.cnExport & 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 · 4h total → projected C (70)
Sprint 1: Quick Wins
+3Highest ROI — low effort, high impact
- · 48 image-in-link without alt text
- · 53 link(s) with no accessible text
- · 9 button(s) with no accessible text
Sprint 2: Core Fixes
+1Medium effort, high structural impact
- · 4 control(s) without accessible label
- · 69 image(s) missing alt attribute