Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: Cupom exclusivo para sua primeira compra. Frete Grátis. Cadastre-se.

path: 0,DIV,7,DIV,1,SECTION,0,DIV,0,DIV,0,UL,1,LI,0,DIV,0,A,0,PICTURE,1,IMG

selector: div.stardust-carousel__item-inner-wrapper > a.bWc0R0 > picture.UkIsx8 > img.uXN1L5

snippet: <img loading="lazy" class="uXN1L5 lazyload OXpSi2" srcset="https://down-br.img.susercontent.com/file/br-11134258-81z1k-mi1qsyhk90qq71…" src="https://down-br.img.susercontent.com/file/br-11134258-81z1k-mi1qsyhk90qq71…" height="220" alt="Cupom exclusivo para sua primeira compra. Frete Grátis. Cadastre-se." elementtiming="shopee:heroComponentPaint" width="412">

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
connect.facebook.net/en_US/bundle/sdk.js/	1200.0 s	77.7 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.4 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.1 KiB
/shopee/shopee-trackingsdk-live-sg/amd/@shopee/tracking-a...	600.0 s	3.2 KiB
/shopee/shopee-trackingsdk-live-sg/@shopee/tracking-loade...	600.0 s	2.6 KiB
vlibras.gov.br/app//assets/access_icon.svg	604800.0 s	0 B
vlibras.gov.br/app//assets/access_popup.jpg	604800.0 s	0 B

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.3 s 400.0 KiB

URL	Transfer Size	Est Savings
/shopee/shopee-mobilemall-live-sg/homepagefe/mobilemall-h...	208.9 KiB	122.5 KiB
accounts.google.com/gsi/client	95.4 KiB	80.2 KiB
deo.shopeemobile.com/shopee/modules-federation/live/0/react-dom/18.3.1.js	109.3 KiB	64.9 KiB
connect.facebook.net/en_US/bundle/sdk.js/	77.6 KiB	50.1 KiB
/shopee/shopee-mobilemall-live-sg/assets/entry-modules.04...	78.1 KiB	46.1 KiB
/shopee/shopee-mobilemall-live-sg/assets/bundle.9811d316d...	113.5 KiB	36.3 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
/shopee/shopee-mobilemall-live-sg/assets/entry-modules.04...	8.2 s	7.7 s	39 ms
/shopee/shopee-mobilemall-live-sg/assets/sfu-latest.8bedd...	5.2 s	4.7 s	67 ms
/shopee/modules-federation/live/0/shopee__web_enhance_sap...	4.2 s	3.9 s	1.9 ms
Unattributable	1.3 s	164 ms	0.0 ms
/shopee/shopee-mobilemall-live-sg/assets/bundle.9811d316d...	968 ms	813 ms	141 ms
shopee.com.br/	890 ms	153 ms	18 ms
/shopee/shopee-mobilemall-live-sg/assets/4585.7d496fc4ce3...	588 ms	578 ms	5.7 ms
/shopee/modules-federation/live/0/react-helmet-async/1.0....	363 ms	306 ms	0.0 ms
deo.shopeemobile.com/shopee/modules-federation/live/0/react-dom/18.3.1.js	200 ms	142 ms	0.0 ms
/shopee/shopee-trackingsdk-live-sg/amd/@shopee/tracking-c...	167 ms	131 ms	4.8 ms
/shopee/shopee-mobilemall-live-sg/homepagefe/mobilemall-h...	159 ms	40 ms	97 ms
/shopee/shopee-mobilemall-live-sg/flashsale/802.a80952160...	144 ms	138 ms	0.8 ms
connect.facebook.net/en_US/bundle/sdk.js/	135 ms	102 ms	32 ms
/shopee/shopee-mobilemall-live-sg/homepagefe/313.d65e3253...	106 ms	19 ms	87 ms
/shopee/shopee-mobilemall-live-sg/assets/LoginByPassword....	104 ms	100 ms	3.3 ms
accounts.google.com/gsi/client	95 ms	61 ms	34 ms
/shopee/shopee-mobilemall-live-sg/assets/VLibrasIntegrati...	66 ms	57 ms	6.3 ms
deo.shopeemobile.com/shopee/shopee-trackingsdk-live-sg/require-trackingsdk.js	60 ms	57 ms	2.5 ms
/shopee/modules-federation/live/0/shopee__tracking-hoc/0....	51 ms	49 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	19.5 s
Other	2.2 s
Script Parsing & Compilation	592 ms
Style & Layout	490 ms
Garbage Collection	295 ms
Rendering	144 ms
Parse HTML & CSS	114 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

Why this matters

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 16.7 KiB

URL	Transfer Size	Est Savings
/*! Project: 'mobilemall'; Module: 'homepagefe'; Slot: 'm...	16.7 KiB	16.7 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,993 KiB

●User Timing marks and measures 33 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 8 animated elements found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 140 ms

●Server Backend Latencies 360 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 290 ms

●Avoid large layout shifts 15 layout shifts found

○INP breakdown

Accessibility

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Esqueceu? `form > div.giO_kv > div.M5BAAU > a.ZDkWzm`
Fazer login com SMS `form > div.giO_kv > div.Q_qgPY > a.BEMmse`
Termos de serviço `div.giO_kv > div.h87Zfk > div.gUfXef > a.bSQMGe`
Política de privacidade `div.giO_kv > div.h87Zfk > div.gUfXef > a.bSQMGe`
Cadastrar `div.app-container > div.Ff1HOv > div.xO4N2y > a.ZDkWzm`
Políticas de privacidade `div.GC86yH > div.hOpgIu > div.jxhcVp > a.awfPZz`
Configurações de cookies `div.GC86yH > div.hOpgIu > div.tqCgC8 > div.mS2i2a`
Aceitar todos os cookies `div.tqCgC8 > div.zTffSG > button.Sz8Dv3 > span.UkQpO3`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Políticas de privacidade `div.GC86yH > div.hOpgIu > div.jxhcVp > a.awfPZz`

These are opportunities to improve the legibility of your content.

Best practices

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.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●The page contains a heading, skip link, or landmark region

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○`[role]` values are valid

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○Heading elements appear in a sequentially-descending order

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

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

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

SEO

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.

Content Best Practices

Canonical links suggest which URL to show in search results. Learn more about canonical links.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`