Audit overview
3 categories need attention: Performance, and 2 others.
Fix Priority Matrix
5 findingsQuick Wins
3High impact, low effort — start here.
Strategic
2High impact, requires investment.
Easy Improvements
0Small gains, minimal effort.
Nothing in this quadrant — good news.
Deprioritize
0Low impact, high effort — do last.
Nothing in this quadrant — good news.
Screenshots
Top Priorities (5)
Page weighs 15.0 MB (4.6 MB transferred)
Informational: total page weight (uncompressed) and bytes actually transferred over the wire.
4 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.
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.
281 third-party resources (100% of weight)
Informational: third-party resource count and their share of page weight. High share caps perf gains from frontend optimization.
282 HTTP requests — consider bundling or reducing
High HTTP request count — bundling, sprite-ing, and HTTP/2 server push can reduce per-request overhead.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
¥45,333 investment → ¥88,191/month returns
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
7 barrier(s) likely increasing bounce by ~30%.
- Page takes 13.8s to loadUsers abandon at ~3s — you're 11.3s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 7.4sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- No Content-Security-Policy headerHigher XSS blast radius — one compromised script can exfiltrate the checkout form→ Ship a reporting-only CSP first, then enforce once violations are clean
- Layout shifts during page loadContent movement causes mis-clicks on CTAs and form fields→ Add width/height to images; reserve space for late-loading embeds
- Viewport disables user zoomVisitors 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
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.
Rates reflect fully-loaded developer cost including overhead
Warning:Cost of inaction
Bounce-Rate Cost
¥8,969 /mo
+29.9pp bounce · ~2,990 lost visitors/mo
CPC: JPY 3.00
Bandwidth Waste
¥173 /mo
14524.1 MB/mo × 11.940 JPY/GB
- Optimize transfer: save ~1.5 MB per page loadSaves ¥173/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.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
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
Your data stays in your browser — nothing is sent to our servers
Lighthouse
Mobile
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
6.87 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
13.75 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
7.39 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.191
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
17.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.
32.82 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
959 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.61 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
971 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.
11.08 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.
8.46 s
Categories
8Performance
Page weighs 15.0 MB (4.6 MB transferred)
Security
All checks pass
Accessibility
4 image(s) missing alt attribute
SEO
All checks pass
Infrastructure
All checks pass
Compliance
All checks pass
Content
All checks pass
Sustainability
All checks pass
How you compare
Where this site stands against peers running the same stack.
Top 10% of WordPress sites score 88+ on Performance; you're at 67 — closing this gap is the highest-leverage improvement.
Top 10% of Apple sites score 84+ on Performance; you're at 67 — closing this gap is the highest-leverage improvement.
Technology stack
WordPress, on Emotion, hosted on Next.js, with Nginx CDN
Stack Architecture
Datadog 
Google Analytics 
WordPress 
Chakra UI Facebook SDK Google Search Console HSTS Microsoft 365 
Open Graph 
React 
Segment 1.62.0
Webpack 
Emotion 
Nginx 1.28.0
Next.js 13.5.11All Detected Technologies (16)
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Next.js is a React framework for developing single page Javascript applications.
Emotion is a library designed for writing CSS styles with JavaScript.
Chakra UI is a simple, modular and accessible component library that gives you the building blocks you need to build your React applications.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Open Graph is a protocol that is used to integrate any web page into the social graph.
React is an open-source JavaScript library for building user interfaces or UI components.
Segment is a customer data platform (CDP) that helps you collect, clean, and control your customer data.
Webpack is an open-source JavaScript module bundler.
Datadog is a SaaS-based monitoring and analytics platform for large-scale applications and infrastructure.
Google Analytics is a free web analytics service that tracks and reports website traffic.
Observations (4)
WordPress detected — review security configuration
WordPress sites benefit from: protecting wp-login.php, disabling XML-RPC if unused, restricting REST API access, and keeping all plugins and themes up to date. Check the Security tab for specific findings.
No build tool detected
A framework (Apple) 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.
Next.js version may be outdated
Detected Next.js 13.5.11. The current major version is 14. Consider updating for security patches and new features.
Complex technology stack detected
16 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.
This badge auto-updates with your latest scan result.
[](https://beavercheck.com/results/3d52f91f-9574-4772-9cc8-6e5be5999077)<a href="https://beavercheck.com/results/3d52f91f-9574-4772-9cc8-6e5be5999077"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Frakuten.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Frakuten.comExport & share
Download the audit, share with your team, or grab a fix plan ready to copy into your tracker.
Copies markdown to clipboard
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 (81)
Sprint 1: Quick Wins
+5Highest ROI — low effort, high impact
- · Page weighs 15.0 MB (4.6 MB transferred)
- · No <main> landmark found
- · 281 third-party resources (100% of weight)
Sprint 2: Core Fixes
+2Medium effort, high structural impact
- · 4 image(s) missing alt attribute
- · 282 HTTP requests — consider bundling or reducing