Skip to content
Scanned
2026-10-04 13:21 UTC
Worker
🇪🇸 Madrid
Duration
1.2m
Vs prev
—

Global Performance

6/6 locations ✓

High global latency — average 2020ms across 6 locations, fastest from Madrid (843ms), slowest from Amsterdam (3567ms). No CDN (document or assets). Cache-Control header is missing. 6 locations above the 500ms target.

Spain - Madrid
Full audit
843ms
DNS 282ms · TLS 190ms
United Stated - New York
1226ms
DNS 547ms · TLS 230ms
Singapore - Singapore
1263ms
DNS 271ms · TLS 334ms
Netherlands - Amsterdam
3567ms
DNS 848ms · TLS 340ms
United States - Santa Clara
2513ms
DNS 698ms · TLS 268ms
Brazil - Sao Paulo
2709ms
DNS 672ms · TLS 345ms
CDN: No CDN (document or assets) · Avg TTFB: 2020ms · Cache: No cache headers

Audit overview

Compliance and Content need attention; the other categories are in good shape.

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

Your mail setup has problems.

zhailaoban.com fails 2 mail checks: No DMARC record found, No SPF record found. This is the kind of misconfiguration that sends your mail to spam.

Get a full deliverability audit — €179, 48h →

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 favicon or icon links detected

Without a favicon, your tab shows a blank icon and bookmarks look unbranded — amateur signal in every browser surface.

Accessibility › Favicon & Branding
Warning: 4

16 inline style attribute(s) detected

Inline style attributes force `style-src 'unsafe-inline'` in any CSP -- effectively negating CSP's XSS-mitigation value for stylesheets.

Security › CSP Inline-Style Readiness
Warning: 5

Cross-Origin-Embedder-Policy header is missing

COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.

Security › Security Headers
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Addressing the critical issues below would have the most immediate impact on your user trust.
4 security gaps detected — browsers may warn visitors about your site.
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

¥3,063 investment → ¥48,859/month returns + CNY 50,000,000 risk avoided

Investment
¥3,063
8.8 h · 5 findings
Monthly returns
¥48,859
¥586,306/yr
Payback
0.1 mo
+19045% Y1
Regulatory risk avoided CNY 50,000,000
Or — fix only the top 3 findings
¥1,313 → 0.0 mo payback · +44571% 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

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

Barriers
8
2 crit 6 warn
Bounce delta
+29pp
added vs baseline
Score
62
C
Speed
1
Trust
2
Usability
1
Content
2
Nav
2
  • Page takes 7.3s to load
    Users abandon at ~3s — you're 4.8s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • 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 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
  • No Open Graph tags
    Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
    → Add og:title, og:description, og:image, og:url to the page head

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

Remediation cost

¥3,063 8.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

¥29,446 / month at risk ~¥353,357 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

¥50,000,000

PIPL
  • No privacy policy found (page links and common paths checked)
    PIPL: CNY 100,000 – CNY 50,000,000
  • Privacy Policy not detected
    PIPL: CNY 100,000 – CNY 50,000,000

Bounce-Rate Cost

¥29,444 /mo

+29.4pp bounce · ~2,944 lost visitors/mo

CPC: CNY 10.00

Bandwidth Waste

¥2.04 /mo

3569.9 MB/mo × 0.571 CNY/GB

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

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

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

7.30 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.466

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

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

7.51 s

Desktop

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

966 ms

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

2.24 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.421

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

1.26 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.24 s

Categories

8
Avg score 80.8

How you compare

Where this site stands against peers running the same stack.

Ubuntu · 83 peers
You 82
·
Avg 75
+7 above average
0 50 100
Better than 85% of Ubuntu sites See full Ubuntu benchmark →
Nginx · 1126 peers
You 82
·
Avg 75
+7 above average
0 50 100
Content P10Performance P87Accessibility P86Compliance P15Infrastructure P19Sustainability P76Security P74SEO P71

Top 10% of Nginx sites score 97+ on Content; you're at 67 — closing this gap is the highest-leverage improvement.

Better than 85% of Nginx sites See full Nginx benchmark →

Technology stack

Ubuntu, with Nginx CDN

2 technologies detected 2 stack layers 2 with CPE identifier Minimal

Stack Architecture

Framework
Ubuntu
CDN
Nginx 1.24.0

All Detected Technologies (2)

Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.

Categories Web servers, Reverse proxies Website https://nginx.org/en Detected by BeaverCheck Evidence Server header: nginx/1.24.0 (Ubuntu)
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Ubuntu is a free and open-source operating system on Linux for the enterprise server, desktop, cloud, and IoT.

Categories Operating systems Website https://www.ubuntu.com/server Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Observations (2)

No build tool detected

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

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 · 9h total → projected B (89)

Sprint 1: Quick Wins

+4

Highest ROI — low effort, high impact

2 findings 1h → B (86)
  • · HSTS header is missing
  • · No favicon or icon links detected

Sprint 2: Core Fixes

+3

Medium effort, high structural impact

3 findings 8h → B (89)
  • · Content-Security-Policy header is missing
  • · Cross-Origin-Embedder-Policy header is missing
  • · 16 inline style attribute(s) detected

Send Feedback