Skip to content
JP · JPY (¥) · Estimated Applicable regulations: APPI Dev cost: ¥8,000/hr How jurisdiction is detected
Scanned
2026-05-15 07:16 UTC
Worker
🇪🇸 Madrid
Duration
1.1m
Vs prev

Global Performance

6/6 locations

High global latency — average 1755ms across 6 locations, fastest from Singapore (1048ms), slowest from Sao Paulo (2216ms). No CDN detected. 6 locations above the 500ms target.

Spain - Madrid
Full audit
1981ms
DNS 274ms · TLS 266ms
Singapore - Singapore
1048ms
DNS 154ms · TLS 85ms
United States - Santa Clara
1247ms
DNS 229ms · TLS 116ms
United Stated - New York
1919ms
DNS 524ms · TLS 178ms
Netherlands - Amsterdam
2121ms
DNS 496ms · TLS 234ms
Brazil - Sao Paulo
2216ms
DNS 603ms · TLS 278ms
CDN: No CDN · Avg TTFB: 1755ms · Cache: max-age=10800

Audit overview

Compliance needs attention; the rest of the categories are in good shape.

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

Missing <html lang> attribute (WCAG 3.1.1)

Missing <html lang> attribute -- screen readers default to the user's system language and pronounce content with the wrong phonetics.

Accessibility › Document Language
Critical: 2

No <main> landmark found

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Accessibility › Landmark Structure
Warning: 3

is missing width/height — may cause layout shift

Performance issues directly impact user engagement and conversion rates.

Performance › Image Optimization
Warning: 4

22 third-party resources (50% of weight)

Informational: third-party resource count and their share of page weight. High share caps perf gains from frontend optimization.

Performance › Page Weight Inventory
Warning: 5

47 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
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 6.6s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute to it. Addressing the critical issues below would have the most immediate impact on your audience reach.
2 accessibility issues exclude users who rely on assistive technology.
Your LCP is 6.6s — fixing the 2 performance criticals could bring it under Google's 2.5s 'Good' threshold.
1 security gap 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

¥50,000 investment → ¥1,470,813/month returns + JPY 100,000,000 risk avoided

Investment
¥50,000
6.3 h · 4 findings
Monthly returns
¥1,470,813
¥17,649,762/yr
Payback
0.0 mo
+35200% Y1
Regulatory risk avoided JPY 100,000,000
Or — fix only the top 3 findings
¥18,0000.0 mo payback · +97954% 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.
¥2,000 — 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

9 barrier(s) likely increasing bounce by ~38%.

Barriers
9
3 crit 6 warn
Bounce delta
+38pp
added vs baseline
Score
52
D
Speed
2
Trust
2
Usability
1
Content
3
Nav
1
  • Page takes 6.6s to load
    Users abandon at ~3s — you're 4.1s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • Page feels frozen for 852ms
    Clicks on the primary CTA are ignored while JavaScript runs
    → Break up long tasks; defer non-critical JavaScript to post-hydration
  • 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
  • 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

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

Remediation cost

¥50,000 6.3 developer hours at ¥8000/hr
Quick wins
¥2,000 2 fixes in ~15 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

Cost of inaction

¥9,388,162 / month at risk ~¥112,657,942 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

¥100,000,000

APPI
  • No privacy policy link detected
    APPI: JPY 100,000 – JPY 100,000,000
  • Privacy Policy not detected
    APPI: JPY 100,000 – JPY 100,000,000

Bounce-Rate Cost

¥1,054,764 /mo

+37.7pp bounce · ~3,767 lost visitors/mo

CPC: JPY 280.00

Bandwidth Waste

¥64 /mo

5380.6 MB/mo × 11.940 JPY/GB

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

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

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

6.63 s

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

852 ms

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

0.002

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

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

11.60 s

Desktop

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

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

4.10 s

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

22 ms

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

0.002

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

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

4.14 s

Categories

8
Avg score 79.1

How you compare

Where this site stands against peers running the same stack.

HSTS · 2429 peers
You 82
·
Avg 75
+7 above average
0 50 100
Compliance P2Security P98Accessibility P91Infrastructure P19Content P31Performance P69SEO P32Sustainability P60

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

Better than 91% of HSTS sites See full HSTS benchmark →
Nginx · 956 peers
You 82
·
Avg 74
+8 above average
0 50 100
Compliance P2Security P95Accessibility P89SEO P21Infrastructure P25Content P27Sustainability P66Performance P65

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

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

Technology stack

HSTS, on PHP, with Nginx CDN

3 technologies detected 3 stack layers 2 with CPE identifier Standard

Stack Architecture

Framework
HSTS
Runtime
PHP
CDN
Nginx

All Detected Technologies (3)

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 →

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

Observations (1)

No build tool detected

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

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%2Fokinawa.dearswedding-resort.jp)](https://beavercheck.com/results/58818790-53f0-4a50-95f5-237fa00f9c99)
<a href="https://beavercheck.com/results/58818790-53f0-4a50-95f5-237fa00f9c99"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fokinawa.dearswedding-resort.jp" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fokinawa.dearswedding-resort.jp

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

Sprint 1: Quick Wins

+4

Highest ROI — low effort, high impact

3 findings 0h → B (86)
  • · Missing <html lang> attribute (WCAG 3.1.1)
  • · No <main> landmark found
  • · 22 third-party resources (50% of weight)

Sprint 2: Core Fixes

+2

Medium effort, high structural impact

2 findings 6h → B (88)
  • · is missing width/height — may cause layout shift
  • · 47 inline style attribute(s) detected

Send Feedback