Audit overview
4 categories need attention: Performance, and 3 others.
Fix Priority Matrix
5 findingsQuick Wins
2High impact, low effort — start here.
Strategic
3High 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.
No Content-Security-Policy header found
Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.
Page weighs 12.0 MB (5.1 MB transferred)
Informational: total page weight (uncompressed) and bytes actually transferred over the wire.
1 control(s) without accessible label
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
1 link(s) with no accessible text
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Business case
What fixing the audit's findings is worth -- and what ignoring them keeps costing.
Return on investment
₩525,000 investment → ₩4,508,122/month returns + KRW 3,000,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
8 barrier(s) likely increasing bounce by ~29%.
- Page takes 17.1s to loadUsers abandon at ~3s — you're 14.6s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 2.3sClicks 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
- 1 form field(s) without a labelScreen 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
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
₩3,000,000,000
- No privacy policy link detectedPIPA: KRW 1,000,000 – KRW 3,000,000,000
- 2 advertising/retargeting trackers detectedPIPA: KRW 1,000,000 – KRW 3,000,000,000
- Trackers detected but no cookie policy foundPIPA: KRW 1,000,000 – KRW 3,000,000,000
Bounce-Rate Cost
₩4,506,388 /mo
+28.7pp bounce · ~2,875 lost visitors/mo
CPC: KRW 1567.57
Bandwidth Waste
₩1,734 /mo
16039.3 MB/mo × 108.108 KRW/GB
- Optimize transfer: save ~1.6 MB per page loadSaves ₩1,734/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.
7.52 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
17.14 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
2.27 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.045
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
18.07 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.
22.80 s
Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
2.95 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
5.81 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
595 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.
5.60 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.
5.81 s
Categories
8Performance
Page weighs 12.0 MB (5.1 MB transferred)
Security
Content-Security-Policy header is missing
Accessibility
1 control(s) without accessible label
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 Cart Functionality sites score 94+ on Infrastructure; you're at 70 — closing this gap is the highest-leverage improvement.
Technology stack
AMP
Stack Architecture
DoubleClick Floodlight 
Google AdSense 
Google Tag Manager 
Cart Functionality 
AMP Google Search Console HSTS 
Kakao 
Open Graph 
Sentry 
Svelte 
Swiper 
core-js 3.31.0
lit-element 3.1.2 lit-html 2.1.2All Detected Technologies (15)
Websites that have a shopping cart or checkout page, either using a known ecommerce platform or a custom solution.
AMP, originally created by Google, is an open-source HTML framework developed by the AMP open-source Project. AMP is designed to help webpages load faster.
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Kakao platform provides various services such as Kakao Talk, Kakao Talk Channel, Kakao Story as well as Kakao Pay, Kakao Commerce, Kakao Page provided by the subsidiaries. Users can use all Kakao platform services with a united account called Kakao Account.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Sentry is an open-source platform for workflow productivity, aggregating errors from across the stack in real time.
Svelte is a free and open-source front end compiler created by Rich Harris and maintained by the Svelte core team members.
Swiper is a JavaScript library that creates modern touch sliders with hardware-accelerated transitions.
core-js is a modular standard library for JavaScript, with polyfills for cutting-edge ECMAScript features.
lit-element is a simple base class for creating web components that work in any web page with any framework. lit-element uses lit-html to render into shadow DOM, and adds API to manage properties and attributes.
lit-html is a simple, modern, safe, small and fast HTML templating library for JavaScript.
Google AdSense is a program run by Google through which website publishers serve advertisements that are targeted to the site content and audience.
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 (AMP) 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
15 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/6f59e13e-35b7-4503-8f34-35eb3951508e)<a href="https://beavercheck.com/results/6f59e13e-35b7-4503-8f34-35eb3951508e"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fdaum.net" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fdaum.netExport & 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 · 8h total → projected C (77)
Sprint 1: Quick Wins
+4Highest ROI — low effort, high impact
- · Page weighs 12.0 MB (5.1 MB transferred)
- · 1 link(s) with no accessible text
Sprint 2: Core Fixes
+6Medium effort, high structural impact
- · 1 control(s) without accessible label
- · Content-Security-Policy header is missing
- · No Content-Security-Policy header found