Skip to content
CN · CNY (¥) · Estimated Applicable regulations: PIPL Dev cost: ¥350/hr How jurisdiction is detected
Scanned
2026-04-22 20:56 UTC
Worker
🇪🇸 Madrid
Duration
57.00s
Vs prev

Audit overview

5 categories need attention: Security, and 4 others.

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

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

Page weighs 11.7 MB (5.2 MB transferred)

Informational: total page weight (uncompressed) and bytes actually transferred over the wire.

Performance › Page Weight Budget
Critical: 5

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

Accessibility › Link & Button Quality
What fixing these means. Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 30.9s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. 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.
Your LCP is 30.9s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
1 accessibility issue excludes 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,363 investment → ¥40,976/month returns + CNY 50,000,000 risk avoided

Investment
¥2,363
6.8 h · 4 findings
Monthly returns
¥40,976
¥491,713/yr
Payback
0.1 mo
+20713% Y1
Regulatory risk avoided CNY 50,000,000
Or — fix only the top 3 findings
¥2,1880.1 mo payback · +22378% 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 ~41%.

Barriers
11
4 crit 7 warn
Bounce delta
+41pp
added vs baseline
Score
39
F
Speed
2
Trust
2
Usability
2
Content
3
Nav
2
  • Page takes 30.9s to load
    Users abandon at ~3s — you're 28.4s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • Page feels frozen for 762ms
    Clicks 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 load
    Users mis-click when content jumps — converting intent into frustration
    → Reserve space for images, ads, and embeds with explicit width/height
  • No viewport meta tag
    Mobile browsers render at desktop width and shrink — text unreadable, tap targets miniature
    → Add <meta name="viewport" content="width=device-width, initial-scale=1">
  • No HSTS header
    Returning 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

¥2,363 6.8 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

¥40,976 / month at risk ~¥491,713 / 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
  • Trackers detected but no cookie policy found
    PIPL: CNY 100,000 – CNY 50,000,000
  • Trackers detected but no privacy policy found
    PIPL: CNY 100,000 – CNY 50,000,000

Bounce-Rate Cost

¥40,967 /mo

+41.0pp bounce · ~4,097 lost visitors/mo

CPC: CNY 10.00

Bandwidth Waste

¥9.34 /mo

16349.4 MB/mo × 0.571 CNY/GB

  • Optimize transfer: save ~1.6 MB per page load
    Saves ¥9.34/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

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

6.56 s

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

30.87 s

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

762 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.323

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

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

30.87 s

Desktop

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

2.39 s

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

2.46 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.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

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

2.46 s

Categories

8
Avg score 68.2

How you compare

Where this site stands against peers running the same stack.

Facebook · 1434 peers
You 68
·
Avg 73
At average
0 50 100
Compliance P2Content P3Infrastructure P6Accessibility P10Security P20SEO P26Sustainability P37Performance P57

Top 10% of Facebook sites score 85+ on Compliance; you're at 66 — closing this gap is the highest-leverage improvement.

Better than 4% of Facebook sites See full Facebook benchmark →
Google Search Console · 3990 peers
You 68
·
Avg 74
-6 below average
0 50 100
Compliance P5Content P5Infrastructure P7Accessibility P11Security P22SEO P23Sustainability P29Performance P45

Top 10% of Google Search Console sites score 85+ on Compliance; you're at 66 — closing this gap is the highest-leverage improvement.

Better than 3% of Google Search Console sites See full Google Search Console benchmark →

Technology stack

Facebook

2 technologies detected 1 stack layers Minimal

Stack Architecture

Framework
Facebook Google Search Console

All Detected Technologies (2)

Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: facebook-domain-verification=hhckudlgb7mat1fknhja5ji5gb8qod
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=4aqFD_3eAhYXE_XXcgtsZldtIk2HiKUuThFew0F8Qtg

Observations (2)

No build tool detected

A framework (Facebook) 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.

Minimal technology footprint

Only 2 technologies detected. This suggests a simple setup with minimal dependencies — excellent for performance and security.

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%2Famazon.cn)](https://beavercheck.com/sites/amazon.cn)
<a href="https://beavercheck.com/sites/amazon.cn"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Famazon.cn" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Famazon.cn

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 · 7h total → projected C (78)

Sprint 1: Quick Wins

+6

Highest ROI — low effort, high impact

3 findings 1h → C (74)
  • · Page weighs 11.7 MB (5.2 MB transferred)
  • · HSTS header is missing
  • · 1 link(s) with no accessible text

Sprint 2: Core Fixes

+4

Medium effort, high structural impact

2 findings 6h → C (78)
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found

Send Feedback