Audit overview
Accessibility needs attention; the rest of the categories are in good shape.
Fix Priority Matrix
5 findingsQuick Wins
4High impact, low effort — start here.
Strategic
1High 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)
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.
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.
Soft 404: server returns HTTP 200 for non-existent pages
Soft 404s (HTTP 200 for missing pages) confuse Google — it indexes the 'not found' page as real content and ranks it.
145 third-party resources (96% of weight)
Informational: third-party resource count and their share of page weight. High share caps perf gains from frontend optimization.
162 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
IDR 2,583,333 investment → IDR 14,021,189/month returns + IDR 60,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
7 barrier(s) likely increasing bounce by ~28%.
- Page takes 16.3s to loadUsers abandon at ~3s — you're 13.8s over the 2.5s threshold→ Optimize render-blocking resources, preload the hero image, and compress images
- Page feels frozen for 13.1sClicks 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
- Thin contentUnder 300 words — visitors bounce looking for substance, search engines rank competitors first→ Add a substantive FAQ, product detail, or case-study section
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
IDR 60,000,000,000
- No privacy policy link detectedUU PDP: IDR 1,000,000,000 – IDR 60,000,000,000
- Trackers detected but no cookie policy foundUU PDP: IDR 1,000,000,000 – IDR 60,000,000,000
- Trackers detected but no privacy policy foundUU PDP: IDR 1,000,000,000 – IDR 60,000,000,000
Bounce-Rate Cost
IDR 14,013,650 /mo
+28.0pp bounce · ~2,803 lost visitors/mo
CPC: IDR 5000.00
Bandwidth Waste
IDR 7,539 /mo
5842.5 MB/mo × 1290.323 IDR/GB
- Optimize transfer: save ~584 KB per page loadSaves IDR 7,539/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.
4.14 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
16.27 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
13.14 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.085
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
13.20 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.
25.23 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.41 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
5.24 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
2.62 s
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.65 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.66 s
Categories
8Performance
145 third-party resources (96% of weight)
Security
All checks pass
Accessibility
1 link(s) with no accessible text
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 Amazon Route 53 sites score 95+ on SEO; you're at 74 — closing this gap is the highest-leverage improvement.
Top 10% of core-js sites score 96+ on SEO; you're at 74 — closing this gap is the highest-leverage improvement.
Technology stack
Amazon Route 53
Stack Architecture
Facebook Pixel 2.9.298
Google Analytics 
Google Tag Manager 
HTTP/3 Native app preferred 
Open Graph 
PWA 
React 18.3.1
Redux 
RequireJS 
Sentry 
core-js 3.29.0
lit-element 2.5.1 lit-html 1.4.1All Detected Technologies (21)
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Open Graph is a protocol that is used to integrate any web page into the social graph.
Progressive Web Apps (PWAs) are web apps built and enhanced with modern APIs to deliver enhanced capabilities, reliability, and installability while reaching anyone, anywhere, on any device, all with a single codebase.
React is an open-source JavaScript library for building user interfaces or UI components.
Redux is a predictable state container for JavaScript applications.
RequireJS is a JavaScript library and file loader which manages the dependencies between JavaScript files and in modular programming.
Sentry is an open-source platform for workflow productivity, aggregating errors from across the stack in real time.
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.
Facebook pixel is an analytics tool that allows you to measure the effectiveness of your advertising.
Google Analytics is a free web analytics service that tracks and reports website traffic.
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 (Amazon Route 53) 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
21 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/134f4c61-d649-4272-a648-f9ac48d96c7d)<a href="https://beavercheck.com/results/134f4c61-d649-4272-a648-f9ac48d96c7d"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fshopee.co.id" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fshopee.co.idExport & 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 · 5h total → projected C (79)
Sprint 1: Quick Wins
+5Highest ROI — low effort, high impact
- · No <main> landmark found
- · 1 link(s) with no accessible text
- · Soft 404: server returns HTTP 200 for non-existent pages
- · 145 third-party resources (96% of weight)
Sprint 2: Core Fixes
+1Medium effort, high structural impact
- · 162 HTTP requests — consider bundling or reducing