United Stated · New York Completed: Apr 16, 2026 18:07 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 73 / 100
Based on 8 categories, 0 sections
Decent speed, but optimizing further could improve engagement.
Good foundation, but a few gaps could be exploited.
Several issues make your site difficult for assistive technology users.
Solid SEO basics — a few optimizations could boost rankings.
Solid infrastructure — fast server responses across the board.
Mostly compliant — a few items need attention.
Rich content metadata — your pages look great everywhere.
Reasonable footprint with room for optimization.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
1 link(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
No <main> landmark found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
Soft 404: server returns HTTP 200 for non-existent pages
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
145 third-party resources (96% of weight)
Performance issues directly impact user engagement and conversion rates.
162 HTTP requests — consider bundling or reducing
Performance issues directly impact user engagement and conversion rates.
High impact, low effort — start here.
Nothing in this quadrant — good news.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](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.idThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 16.3s 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.
7 barrier(s) likely increasing bounce by ~28%.
Page takes 16.3s to load
+12% bounceUsers abandon at ~3s — you're 13.8s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 13.1s
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
Thin content
+3% bounceUnder 300 words — visitors bounce looking for substance, search engines rank competitors first
Fix: Add a substantive FAQ, product detail, or case-study section
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
1 broken link(s) on the page
+2% bounceClicks land on 404s — trust drops and the session often ends
Fix: Fix or remove the broken destinations surfaced on the Content tab
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
IDR 4,250,000 investment → IDR 7,539/month returns + IDR 60,000,000,000 risk avoided
IDR 4,250,000
8h · 5 findings
IDR 7,539 /mo
~IDR 90,465 / year
IDR 60,000,000,000
if kept compliant
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.
8.5 developer hours at Rp500000/hr
Based on Indonesia rates (Rp500000/hr)
IDR 5,000,007,539 / month at risk
~IDR 60,000,090,465 / year if left unfixed
IDR 60,000,000,000
+1 more
IDR 7,539 /mo
5842.5 MB/mo × 1290.323 IDR/GB
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
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
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
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
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| connect.facebook.net/en_US/fbevents.js | 1200.0 s | 96.4 KiB |
| connect.facebook.net/en_US/bundle/sdk.js/ | 1200.0 s | 77.7 KiB |
| /signals/config/466924370133774?v=2.9.298&r=stable&domain... | 1200.0 s | 45.5 KiB |
| /shopee/shopee-trackingsdk-live-sg/amd/@shopee/tracking-c... | 600.0 s | 9.3 KiB |
| deo.shopeemobile.com/shopee/shopee-trackingsdk-live-sg/require-trackingsdk.js | 600.0 s | 8.0 KiB |
| /shopee/shopee-trackingsdk-live-sg/amd/@shopee/tracking-u... | 600.0 s | 6.5 KiB |
| connect.facebook.net/en_US/sdk.js | 1200.0 s | 5.0 KiB |
| /shopee/shopee-trackingsdk-live-sg/amd/@shopee/tracking-a... | 600.0 s | 3.1 KiB |
| /shopee/shopee-trackingsdk-live-sg/@shopee/tracking-loade... | 600.0 s | 2.6 KiB |
| static.hotjar.com/c/hotjar-955851.js?sv=7 | 60.0 s | 434 B |
| /tr/?id=466924370133774&ev=PageView&dl=https%3A%2F%2Fshop... | 0.0 ms | 19 B |
| /tr/?id=466924370133774&ev=PageView&dl=https%3A%2F%2Fshop... | 0.0 ms | 16 B |
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| /shopee/shopee-mobilemall-live-sg/homepagefe/mobilemall-h... | 164.7 KiB | 97.7 KiB |
| accounts.google.com/gsi/client | 95.3 KiB | 80.1 KiB |
| www.googletagmanager.com/gtag/js?id=G-SW6D8G0HXK&cx=c>m=4e64f0 | 170.7 KiB | 64.9 KiB |
| www.googletagmanager.com/gtag/destination?id=DC-9469210&cx=c>m=4e64f0 | 129.2 KiB | 61.2 KiB |
| connect.facebook.net/en_US/bundle/sdk.js/ | 77.6 KiB | 50.0 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-WJZQSJF | 189.6 KiB | 48.6 KiB |
| /shopee/shopee-mobilemall-live-sg/assets/entry-modules.04... | 78.1 KiB | 47.1 KiB |
| /shopee/shopee-mobilemall-live-sg/assets/bundle.9811d316d... | 113.5 KiB | 36.8 KiB |
| deo.shopeemobile.com/shopee/modules-federation/live/0/react-dom/18.3.1.js | 57.6 KiB | 34.8 KiB |
| connect.facebook.net/en_US/fbevents.js | 96.3 KiB | 31.7 KiB |
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Performance issues directly impact user engagement and conversion rates.
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 23.8 s |
| Other | 1.8 s |
| Script Parsing & Compilation | 782 ms |
| Style & Layout | 445 ms |
| Garbage Collection | 303 ms |
| Rendering | 107 ms |
| Parse HTML & CSS | 79 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /shopee/shopee-mobilemall-live-sg/homepagefe/mobilemall-h... | 12.4 KiB | 12.3 KiB |
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
div.OccmOl > div.SRdzOV > div._9ugfa > img.KVL3LP div.OccmOl > div.SRdzOV > div._9ugfa > img.KVL3LP | /shopee/shopee-mobilemall-live-sg/assets/c81b58e2faa48467... |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Lupa? form > div.giO_kv > div.M5BAAU > a.ZDkWzm |
Log in dengan no. handphone form > div.giO_kv > div.Q_qgPY > a.BEMmse |
SYARAT LAYANAN div.giO_kv > div.h87Zfk > div.gUfXef > a.bSQMGe |
KEBIJAKAN PRIVASI div.giO_kv > div.h87Zfk > div.gUfXef > a.bSQMGe |
Daftar div.app-container > div.Ff1HOv > div.xO4N2y > a.ZDkWzm |
Oke div.app-container > div.OccmOl > div.hvRr71 > button.stardust-button |
These are opportunities to improve the legibility of your content.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.OccmOl > div.SRdzOV > div._9ugfa > img.KVL3LP div.OccmOl > div.SRdzOV > div._9ugfa > img.KVL3LP |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| SharedStorage | /shopee/shopee-mobilemall-live-sg/assets/sfu-latest.8bedd... line 4, col 46586 |
| AttributionReporting | connect.facebook.net/en_US/fbevents.js line 279, col 769 |
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.OccmOl > div.SRdzOV > div._9ugfa > img.KVL3LP div.OccmOl > div.SRdzOV > div._9ugfa > img.KVL3LP |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — 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
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Performance issues directly impact user engagement and conversion rates.
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
Log In
Log in dengan QR
LOG IN
Lupa Password
ATAU
Facebook
Google
Dengan login,… div.kr8eST > div.r0dQ_c > div > div.UCVQlJ | deo.shopeemobile.com/shopee/shopee-pcmall-live-sg/assets/031b0e72a254e6a6.png | 235.2 KiB | 133.6 KiB |
Worldmap div.UsynuF > div.pEpvVk > div.eaZxNW > img.lEhskN | deo.shopeemobile.com/shopee/shopee-pcmall-live-sg/assets/1c8bdaaf45e1fd48.png | 37.2 KiB | 18.9 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /shopee/shopee-pcmall-live-sg/assets/bundle.9b0f374b2311b... | 17.2 KiB | 16.3 KiB |
| /shopee/shopee-pcmall-live-sg/homepagefe/pcmall-homepagef... | 14.3 KiB | 14.2 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| /shopee/shopee-pcmall-live-sg/homepagefe/pcmall-homepagef... | 143.9 KiB | 109.1 KiB |
| /shopee/shopee-pcmall-live-sg/assets/entry-modules.0e48ae... | 118.4 KiB | 82.5 KiB |
| accounts.google.com/gsi/client | 95.3 KiB | 80.1 KiB |
| www.googletagmanager.com/gtag/js?id=G-SW6D8G0HXK&cx=c>m=4e64f0 | 170.7 KiB | 65.6 KiB |
| www.googletagmanager.com/gtag/destination?id=DC-9469210&cx=c>m=4e64f0 | 129.2 KiB | 61.3 KiB |
| /shopee/shopee-pcmall-live-sg/assets/bundle.6e0f816ad3da8... | 173.7 KiB | 58.0 KiB |
| connect.facebook.net/en_US/bundle/sdk.js/ | 77.6 KiB | 50.0 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-WJZQSJF | 189.6 KiB | 49.5 KiB |
| deo.shopeemobile.com/shopee/modules-federation/live/0/react-dom/18.3.1.js | 57.6 KiB | 34.7 KiB |
| connect.facebook.net/en_US/fbevents.js | 96.3 KiB | 32.7 KiB |
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| /shopee/shopee-pcmall-live-sg/assets/sfu-latest.1b17eeecc... | 2.1 s | 2.0 s | 15 ms |
| /shopee/shopee-pcmall-live-sg/assets/entry-modules.0e48ae... | 2.0 s | 1.9 s | 18 ms |
| /shopee/modules-federation/live/0/shopee__web_enhance_sap... | 387 ms | 382 ms | 0.4 ms |
| Unattributable | 367 ms | 29 ms | 0.0 ms |
| www.googletagmanager.com/gtm.js?id=GTM-WJZQSJF | 274 ms | 234 ms | 25 ms |
| /shopee/shopee-pcmall-live-sg/assets/9392.97e8cf470bae32d... | 207 ms | 205 ms | 1.3 ms |
| /shopee/shopee-pcmall-live-sg/assets/bundle.6e0f816ad3da8... | 177 ms | 130 ms | 39 ms |
| shopee.co.id/ | 139 ms | 26 ms | 3.7 ms |
| www.googletagmanager.com/gtag/js?id=G-SW6D8G0HXK&cx=c>m=4e64f0 | 114 ms | 98 ms | 16 ms |
| /signals/config/466924370133774?v=2.9.298&r=stable&domain... | 111 ms | 104 ms | 6.0 ms |
| deo.shopeemobile.com/shopee/modules-federation/live/0/react-dom/18.3.1.js | 103 ms | 77 ms | 0.0 ms |
| www.googletagmanager.com/gtag/destination?id=DC-9469210&cx=c>m=4e64f0 | 62 ms | 51 ms | 11 ms |
| /shopee/modules-federation/live/0/shopee__tracking-hoc/0.... | 57 ms | 56 ms | 0.0 ms |
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 5.6 s |
| Other | 496 ms |
| Script Parsing & Compilation | 182 ms |
| Garbage Collection | 107 ms |
| Style & Layout | 96 ms |
| Rendering | 26 ms |
| Parse HTML & CSS | 23 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Pilih bahasa Anda
Bahasa Indonesia
English body.shopee-no-scroll > div#modal > div.SqO999 > div.UsynuF |
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
form > div.wIH_BM > div.YxyuDT > button.px6VFi form > div.wIH_BM > div.YxyuDT > button.px6VFi |
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
ul.tYFPu_ > li.wdBnpK > a.yIJgtJ > img.AlFaz4 ul.tYFPu_ > li.wdBnpK > a.yIJgtJ > img.AlFaz4 |
ul.tYFPu_ > li.wdBnpK > a.yIJgtJ > img.AlFaz4 ul.tYFPu_ > li.wdBnpK > a.yIJgtJ > img.AlFaz4 |
ul.tYFPu_ > li.wdBnpK > a.yIJgtJ > img.AlFaz4 ul.tYFPu_ > li.wdBnpK > a.yIJgtJ > img.AlFaz4 |
ul.tYFPu_ > li.wdBnpK > a.yIJgtJ > img.AlFaz4 ul.tYFPu_ > li.wdBnpK > a.yIJgtJ > img.AlFaz4 |
ul.tYFPu_ > li.wdBnpK > a.yIJgtJ > img.AlFaz4 ul.tYFPu_ > li.wdBnpK > a.yIJgtJ > img.AlFaz4 |
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
nav.XTygfR > div.aSMz_B > div.ssCjSz > a.jsl9A1 nav.XTygfR > div.aSMz_B > div.ssCjSz > a.jsl9A1 |
div._92W8Vw > div.KhSVKK > div.ZJ5g1O > a.EbRO8C div._92W8Vw > div.KhSVKK > div.ZJ5g1O > a.EbRO8C |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Butuh bantuan? nav.XTygfR > div.aSMz_B > div.bX0Ln8 > a.kFs6aX |
Log in dengan QR div._92W8Vw > div.KhSVKK > div.ZJ5g1O > div.YqPlXG |
ATAU div.iXeFvH > div.tctXCO > div.yxW8PM > span.eNWshb |
Syarat, Ketentuan dan Kebijakan dari Shopee div.iXeFvH > div.C5J4mr > div.vEK4AR > a.pIN8ZZ |
Kebijakan Privasi div.iXeFvH > div.C5J4mr > div.vEK4AR > a.pIN8ZZ |
Baru di Shopee?
Daftar div > div.VAy83y > div.BGz463 > div.mT7wZj |
Daftar div.VAy83y > div.BGz463 > div.mT7wZj > a.JOxeOr |
© Shopee 2026. Hak Cipta Dilindungi div > div.mUnW9g > div.URvGxz > div.Pc3d01 |
Negara: div.mUnW9g > div.URvGxz > div.hLS7q8 > div.whkXnv |
Argentina div.URvGxz > div.hLS7q8 > div.FvfvFP > a.fPod4n |
Singapura div.URvGxz > div.hLS7q8 > div.FvfvFP > a.fPod4n |
Indonesia div.URvGxz > div.hLS7q8 > div.FvfvFP > a.fPod4n |
Thailand div.URvGxz > div.hLS7q8 > div.FvfvFP > a.fPod4n |
Malaysia div.URvGxz > div.hLS7q8 > div.FvfvFP > a.fPod4n |
Vietnam div.URvGxz > div.hLS7q8 > div.FvfvFP > a.fPod4n |
Filipina div.URvGxz > div.hLS7q8 > div.FvfvFP > a.fPod4n |
Brazil div.URvGxz > div.hLS7q8 > div.FvfvFP > a.fPod4n |
México div.URvGxz > div.hLS7q8 > div.FvfvFP > a.fPod4n |
Taiwan div.URvGxz > div.hLS7q8 > div.FvfvFP > a.fPod4n |
Bahasa Indonesia div.pEpvVk > div.S9b8DU > div.oHpRV2 > button.shopee-button-outline |
English div.pEpvVk > div.S9b8DU > div.oHpRV2 > button.shopee-button-outline |
These are opportunities to improve the legibility of your content.
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
lompat ke konten utama div#main > div > section.G9LJcQ > button.stardust-button |
These are opportunities to improve keyboard navigation in your application.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| AttributionReporting | connect.facebook.net/en_US/fbevents.js line 279, col 769 |
| SharedStorage | /shopee/shopee-pcmall-live-sg/assets/sfu-latest.1b17eeecc... line 37, col 46586 |
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Performance issues directly impact user engagement and conversion rates.
| Uncrawlable Link |
|---|
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
logo div.WgSr6D > ul.n9X8as > li.Ei2TcA > a.HOyEnn |
To appear in search results, crawlers need access to your app.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
ul.tYFPu_ > li.wdBnpK > a.yIJgtJ > img.AlFaz4 ul.tYFPu_ > li.wdBnpK > a.yIJgtJ > img.AlFaz4 |
ul.tYFPu_ > li.wdBnpK > a.yIJgtJ > img.AlFaz4 ul.tYFPu_ > li.wdBnpK > a.yIJgtJ > img.AlFaz4 |
ul.tYFPu_ > li.wdBnpK > a.yIJgtJ > img.AlFaz4 ul.tYFPu_ > li.wdBnpK > a.yIJgtJ > img.AlFaz4 |
ul.tYFPu_ > li.wdBnpK > a.yIJgtJ > img.AlFaz4 ul.tYFPu_ > li.wdBnpK > a.yIJgtJ > img.AlFaz4 |
ul.tYFPu_ > li.wdBnpK > a.yIJgtJ > img.AlFaz4 ul.tYFPu_ > li.wdBnpK > a.yIJgtJ > img.AlFaz4 |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback