Skip to content
Scanned
2026-05-29 03:43 UTC
Worker
🇪🇸 Madrid
Duration
58.00s
Vs prev

Global Performance

6/6 locations

High global latency — average 1044ms across 6 locations, fastest from Amsterdam (590ms), slowest from Sao Paulo (1865ms). No CDN detected. 6 locations above the 500ms target.

Spain - Madrid
Full audit
611ms
DNS 406ms · TLS 29ms
Netherlands - Amsterdam
590ms
DNS 419ms · TLS 18ms
United States - Santa Clara
910ms
DNS 339ms · TLS 156ms
United Stated - New York
1608ms
DNS 479ms · TLS 89ms
Singapore - Singapore
682ms
DNS 110ms · TLS 158ms
Brazil - Sao Paulo
1865ms
DNS 740ms · TLS 208ms
CDN: No CDN · Avg TTFB: 1044ms · Cache: private

Audit overview

3 categories need attention: Accessibility, and 2 others.

Fix Priority Matrix

5 findings

Quick Wins

4

High impact, low effort — start here.

Strategic

1

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

Cookie 'PHPSESSID' is missing the Secure flag

A cookie without the Secure flag can leak over HTTP — in HSTS-protected sites, this is still a defense-in-depth gap.

Security › Cookie Security
Critical: 3

Cookie 'admin_lang' is missing the Secure flag

A cookie without the Secure flag can leak over HTTP — in HSTS-protected sites, this is still a defense-in-depth gap.

Security › Cookie Security
Critical: 4

Cookie 'home_lang' is missing the Secure flag

A cookie without the Secure flag can leak over HTTP — in HSTS-protected sites, this is still a defense-in-depth gap.

Security › Cookie Security
Critical: 5

Cookie 'lang_info' is missing the Secure flag

A cookie without the Secure flag can leak over HTTP — in HSTS-protected sites, this is still a defense-in-depth gap.

Security › Cookie Security
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.
5 security gaps detected — browsers may warn visitors about your site.

Business case

What fixing the audit's findings is worth -- and what ignoring them keeps costing.

Return on investment

¥1,400 investment → ¥31,910/month returns + CNY 50,000,000 risk avoided

Investment
¥1,400
4.0 h · 5 findings
Monthly returns
¥31,910
¥382,917/yr
Payback
0.0 mo
+27251% Y1
Regulatory risk avoided CNY 50,000,000
Or — fix only the top 3 findings
¥1,2250.0 mo payback · +31159% 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.
¥350 — 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

12 barrier(s) likely increasing bounce by ~27%.

Barriers
12
12 warn
Bounce delta
+27pp
added vs baseline
Score
64
C
Speed
2
Trust
2
Usability
2
Content
3
Nav
3
  • Page loads in 3.3s
    Every additional 100ms above 2.5s costs conversions — you're 770ms over
    → Target <2.5s LCP: defer non-critical scripts and optimize the hero image
  • High main-thread blocking time
    Page is non-interactive for 274ms after first paint
    → Defer third-party scripts and split large bundles
  • 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
  • 1 form field(s) without a label
    Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes
    → Associate every input with a visible <label for="…">; add autocomplete attributes

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

Remediation cost

¥1,400 4.0 developer hours at ¥350/hr
Quick wins
¥350 4 fixes in ~60 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

¥26,522 / month at risk ~¥318,264 / 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
  • 7 non-essential cookie(s) set without consent banner
    PIPL: CNY 100,000 – CNY 50,000,000
  • 1 advertising/retargeting trackers detected
    PIPL: CNY 100,000 – CNY 50,000,000

Bounce-Rate Cost

¥26,513 /mo

+26.5pp bounce · ~2,651 lost visitors/mo

CPC: CNY 10.00

Bandwidth Waste

¥9.48 /mo

16585.9 MB/mo × 0.571 CNY/GB

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

84
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
61
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
75
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.23 s

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

3.27 s

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

274 ms

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

0.009

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.

6.59 s

Desktop

96
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
61
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
75
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.

500 ms

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

799 ms

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.

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

799 ms

Categories

8
Avg score 73.5

How you compare

Where this site stands against peers running the same stack.

Font Awesome · 559 peers
You 76
·
Avg 73
At average
0 50 100
Compliance P1Infrastructure P5Security P91Content P10Performance P81Accessibility P80Sustainability P41SEO P51

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

Better than 73% of Font Awesome sites See full Font Awesome benchmark →
HSTS · 2556 peers
You 76
·
Avg 75
At average
0 50 100
Compliance P1Infrastructure P3Content P6Security P79Accessibility P73Performance P70Sustainability P35SEO P56

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

Better than 56% of HSTS sites See full HSTS benchmark →

Technology stack

Font Awesome, on PHP, with Nginx CDN

9 technologies detected 4 stack layers 2 with CPE identifier Enterprise

Stack Architecture

Analytics
Google Ads Google Ads Conversion Tracking Google Analytics Google Tag Manager
Framework
Font Awesome HSTS HTTP/3
Runtime
PHP
CDN
Nginx

All Detected Technologies (9)

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
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

PHP is a general-purpose scripting language used for web development.

Categories Programming languages Website https://php.net Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Font Awesome is a font and icon toolkit based on CSS and Less.

Categories Font scripts Website https://fontawesome.com/ Detected by BeaverCheck

HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.

Categories Security Website https://www.rfc-editor.org/rfc/rfc6797#section-6.1 Detected by BeaverCheck

HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.

Categories Miscellaneous Website https://httpwg.org/ Detected by BeaverCheck

Google Ads is an online advertising platform developed by Google.

Categories Advertising Website https://ads.google.com Detected by BeaverCheck

Google Ads Conversion Tracking is a free tool that shows you what happens after a customer interacts with your ads.

Categories Analytics Website https://support.google.com/google-ads/answer/1722022 Detected by BeaverCheck

Google Analytics is a free web analytics service that tracks and reports website traffic.

Categories Analytics Website https://google.com/analytics Detected by BeaverCheck

Google Tag Manager is a tag management system (TMS) that allows you to quickly and easily update measurement codes and related code fragments collectively known as tags on your website or mobile app.

Categories Tag managers Website https://www.google.com/tagmanager Detected by BeaverCheck Evidence Script URL contains www.googletagmanager.com: https://www.googletagmanager.com/gtag/js?id=G-D0CQJXQ4G5&cx=c&gtm=4e65r2

Observations (2)

No build tool detected

A framework (Font Awesome) 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

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

BeaverCheck badge

This badge auto-updates with your latest scan result.

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.jxdeco-packaging.com)](https://beavercheck.com/results/c03515d1-9e22-41fa-ac61-3d6b14cf5bdd)
<a href="https://beavercheck.com/results/c03515d1-9e22-41fa-ac61-3d6b14cf5bdd"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.jxdeco-packaging.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.jxdeco-packaging.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 · 4h total → projected B (82)

Sprint 1: Quick Wins

+6

Highest ROI — low effort, high impact

4 findings 1h → B (82)
  • · Cookie 'PHPSESSID' is missing the Secure flag
  • · Cookie 'admin_lang' is missing the Secure flag
  • · Cookie 'home_lang' is missing the Secure flag
  • · Cookie 'lang_info' is missing the Secure flag

Sprint 2: Core Fixes

Medium effort, high structural impact

1 findings 3h → B (82)
  • · Content-Security-Policy header is missing

Send Feedback