Audit overview
3 categories need attention: Security, 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)
Content-Security-Policy header is missing
Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.
Cookie 'XSRF-TOKEN' 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.
Cookie 'laravel_session' 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.
No Content-Security-Policy header found
Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.
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.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
¥53,333 investment → ¥1,470,591/month returns + JPY 100,000,000 risk avoided
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 ~32%.
- Page takes 7.4s to loadUsers abandon at ~3s — you're 4.9s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 1.2sClicks on the primary CTA are ignored while JavaScript runs→ Break up long tasks; defer non-critical JavaScript to post-hydration
- No HSTS headerReturning visitors are briefly exposed to downgrade attacks on first request→ Set Strict-Transport-Security: max-age=31536000; includeSubDomains
- 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
- 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
Compliance Risk
¥100,000,000
- No privacy policy link detectedAPPI: JPY 100,000 – JPY 100,000,000
- 3 advertising/retargeting trackers detectedAPPI: JPY 100,000 – JPY 100,000,000
- Trackers detected but no cookie policy foundAPPI: JPY 100,000 – JPY 100,000,000
Bounce-Rate Cost
¥890,660 /mo
+31.8pp bounce · ~3,181 lost visitors/mo
CPC: JPY 280.00
Bandwidth Waste
¥101 /mo
8435.9 MB/mo × 11.940 JPY/GB
- Optimize transfer: save ~844 KB per page loadSaves ¥101/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 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
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.
2.46 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
7.40 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.19 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.030
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
6.64 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.
17.91 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.69 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.39 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
30 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.95 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.73 s
Categories
8Performance
All checks pass
Security
Content-Security-Policy header is missing
Accessibility
No <main> landmark found
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 Font Awesome sites score 75+ on Security; you're at 55 — closing this gap is the highest-leverage improvement.
Top 10% of HSTS sites score 82+ on Security; you're at 55 — closing this gap is the highest-leverage improvement.
Technology stack
Font Awesome, on PHP, with Nginx CDN
Stack Architecture
Amazon Advertising 
DoubleClick Floodlight 
Google Analytics 
Google Publisher Tag 
Google Tag Manager 
Font Awesome HSTS 
Laravel 
Open Graph 
RSS 
Ruby on Rails 
PHP 
Ruby 
Nginx 1.18.0All Detected Technologies (14)
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
PHP is a general-purpose scripting language used for web development.
Ruby is an open-source object-oriented programming language.
Font Awesome is a font and icon toolkit based on CSS and Less.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Laravel is a free, open-source PHP web framework.
Open Graph is a protocol that is used to integrate any web page into the social graph.
RSS is a family of web feed formats used to publish frequently updated works—such as blog entries, news headlines, audio, and video—in a standardized format.
Ruby on Rails is a server-side web application framework written in Ruby under the MIT License.
Amazon Advertising (formerly AMS or Amazon Marketing Services) is a service that works in a similar way to pay-per-click ads on Google.
Google Analytics is a free web analytics service that tracks and reports website traffic.
Google Publisher Tag (GPT) is an ad tagging library for Google Ad Manager which is used to dynamically build ad requests.
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.
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
14 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/e842452d-0146-4876-9143-08e8b07de749)<a href="https://beavercheck.com/results/e842452d-0146-4876-9143-08e8b07de749"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fjugem.jp" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fjugem.jpExport & 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 · 7h total → projected C (77)
Sprint 1: Quick Wins
+7Highest ROI — low effort, high impact
- · No <main> landmark found
- · Cookie 'XSRF-TOKEN' is missing the Secure flag
- · Cookie 'laravel_session' is missing the Secure flag
Sprint 2: Core Fixes
+2Medium effort, high structural impact
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found