Skip to content
Scanned
2026-04-21 20:32 UTC
Worker
🇺🇸 Santa Clara
Duration
2.2m
Vs prev

Audit overview

4 categories need attention: Security, and 3 others.

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

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

HSTS header is missing

Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.

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

15 image-only link(s) without alt text

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Accessibility › Link & Button Quality
Critical: 5

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

Accessibility › Alt Text Quality
What fixing these means. Your site has several issues that may be affecting user experience and business outcomes. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.
3 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude 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,888 investment → ¥39,626/month returns + CNY 50,000,000 risk avoided

Investment
¥2,888
8.3 h · 5 findings
Monthly returns
¥39,626
¥475,516/yr
Payback
0.1 mo
+16368% Y1
Regulatory risk avoided CNY 50,000,000
Or — fix only the top 3 findings
¥2,1880.1 mo payback · +21638% 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.
¥263 — 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

11 barrier(s) likely increasing bounce by ~29%.

Barriers
11
1 crit 10 warn
Bounce delta
+29pp
added vs baseline
Score
60
C
Speed
2
Trust
2
Usability
1
Content
3
Nav
3
  • Page feels frozen for 12.5s
    Clicks on the primary CTA are ignored while JavaScript runs
    → Break up long tasks; defer non-critical JavaScript to post-hydration
  • Page loads in 4.0s
    Every additional 100ms above 2.5s costs conversions — you're 1.5s over
    → Target <2.5s LCP: defer non-critical scripts and optimize the hero image
  • No HSTS header
    Returning visitors are briefly exposed to downgrade attacks on first request
    → Set Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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
  • Viewport disables user zoom
    Visitors with low vision can't read the page — and some jurisdictions treat this as a legal risk
    → Remove user-scalable=no; drop maximum-scale if it's below 2

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Remediation cost

¥2,888 8.3 developer hours at ¥350/hr
Quick wins
¥263 2 fixes in ~45 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

¥29,218 / month at risk ~¥350,611 / 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
  • Privacy Policy not detected
    PIPL: CNY 100,000 – CNY 50,000,000

Bounce-Rate Cost

¥29,215 /mo

+29.2pp bounce · ~2,921 lost visitors/mo

CPC: CNY 10.00

Bandwidth Waste

¥2.90 /mo

5070.9 MB/mo × 0.571 CNY/GB

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

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Lighthouse

Mobile

43
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
54
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.
50
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.16 s

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

3.99 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

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

10.87 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.71 s

Desktop

36
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
58
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.
58
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.41 s

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

4.05 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

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

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

9.13 s

Categories

8
Avg score 67.0

How you compare

Where this site stands against peers running the same stack.

core-js · 1605 peers
You 65
·
Avg 72
-7 below average
0 50 100
Infrastructure P1Accessibility P2Compliance P4SEO P5Content P7Security P11Performance P79Sustainability P77

Top 10% of core-js sites score 94+ on Infrastructure; you're at 70 — closing this gap is the highest-leverage improvement.

Lodash · 227 peers
You 65
·
Avg 72
-7 below average
0 50 100

Technology stack

Lodash

5 technologies detected 2 stack layers 1 with CPE identifier Standard

Stack Architecture

Build
Webpack
Framework
Lodash Microsoft 365 Vue.js core-js 3.38.0

All Detected Technologies (5)

Lodash is a JavaScript library which provides utility functions for common programming tasks using the functional programming paradigm.

Categories JavaScript libraries Website https://www.lodash.com Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →
Categories Email Detected by BeaverCheck Evidence TXT SPF record includes spf.protection.outlook.com: v=spf1 include:spf.protection.partner.outlook.cn include:spf.protection.outlook.com ip4:139.217.239.155 ip4:40.72.104.225 ip4:40.73.101.7 ip4:42.159.185.160 ip4:40.73.72.23 ip4:139.224.113.34 ip4:106.15.199.98 ip4:47.100.175.65 ip4:106.14.162.178 -all

Vue.js is an open-source model–view–viewmodel JavaScript framework for building user interfaces and single-page applications.

Categories JavaScript frameworks Website https://vuejs.org Detected by BeaverCheck

core-js is a modular standard library for JavaScript, with polyfills for cutting-edge ECMAScript features.

Categories JavaScript libraries Website https://github.com/zloirock/core-js Detected by BeaverCheck
Categories Build Tool Website https://webpack.js.org Detected by BeaverCheck · Medium Evidence Chunk pattern: https://fe-static.xhscdn.com/formula-static/xhs-pc-web/public/resource/js/vendor.d091a147.js

Observations (0)

No specific observations.

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%2Fxiaohongshu.com)](https://beavercheck.com/sites/xiaohongshu.com)
<a href="https://beavercheck.com/sites/xiaohongshu.com"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fxiaohongshu.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fxiaohongshu.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 · 8h total → projected C (74)

Sprint 1: Quick Wins

+4

Highest ROI — low effort, high impact

2 findings 1h → D (69)
  • · HSTS header is missing
  • · 15 image-only link(s) without alt text

Sprint 2: Core Fixes

+5

Medium effort, high structural impact

3 findings 8h → C (74)
  • · 31 image(s) missing alt attribute
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found

Send Feedback