Skip to content
https://lazada.com

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

58

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.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:4282.044999023437 label:Time to first byte subpart:timeToFirstByte] map[duration:1141.4650009765626 label:Resource load delay subpart:resourceLoadDelay] map[duration:597.615 label:Resource load duration subpart:resourceLoadDuration] map[duration:1684.752 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-DIV
nodeLabel: HOME ABOUT PRESS & MEDIA CAREERS CONTACTS ECOMMERCE IS CHANGING AND WE'RE LEADI…
path: 1,HTML,1,BODY,0,MAIN,1,DIV,0,DIV
selector: body > main > div#first > div.row
snippet: <div class="row align-items-end mb-5 home-bg aos-init aos-animate" data-aos="fade-up">

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-DIV
nodeLabel: HOME ABOUT PRESS & MEDIA CAREERS CONTACTS ECOMMERCE IS CHANGING AND WE'RE LEADI…
path: 1,HTML,1,BODY,0,MAIN,1,DIV,0,DIV
selector: body > main > div#first > div.row
snippet: <div class="row align-items-end mb-5 home-bg aos-init aos-animate" data-aos="fade-up">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLProtocol
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/bootstrap.4.3.1.min.csshttp/1.1
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/style.20220408.csshttp/1.1
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/image/logo_white.svghttp/1.1
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/js/base.jshttp/1.1
/static/font/ProximaNovaFonts/proximanova-semibold-webfon...http/1.1
/static/font/ProximaNovaFonts/proximanova-bold-webfont.woff2http/1.1
/static/font/ProximaNovaFonts/proximanova-regular-webfont...http/1.1
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/image/home-hero_x1.webphttp/1.1
/static/image/new-lazada-logo-small.pnghttp/1.1

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
value: no origins were preconnected
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

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/bootstrap.4.3.1.min.css24.1 KiB1.2 s
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/style.20220408.css8.8 KiB968 ms
g.alicdn.com/code/lib/jquery/3.5.1/jquery.min.js30.8 KiB80 ms
g.alicdn.com/code/lib/lozad.js/1.15.0/lozad.min.js1.7 KiB
g.alicdn.com/code/lib/aos/3.0.0-beta.6/aos.css3.0 KiB202 ms

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.

RequestCache TTLTransfer Size
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/bootstrap.4.3.1.min.css0.0 ms24.1 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/style.20220408.css0.0 ms8.8 KiB
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/js/base.js0.0 ms3.1 KiB
g.alicdn.com/code/lib/jquery/3.5.1/jquery.min.js2422554.0 s30.8 KiB
g.alicdn.com/code/lib/twitter-bootstrap/4.3.1/js/bootstrap.min.js2054938.0 s15.6 KiB
/aes/??tracker/3.0.0/index.js,tracker-plugin-pv/3.0.1/ind...500355.0 s10.3 KiB
g.alicdn.com/alilog/mlog/aplus_int.js312155.0 s6.0 KiB
g.alicdn.com/code/lib/aos/3.0.0-beta.6/aos.js432893.0 s5.3 KiB
g.alicdn.com/code/lib/popper.js/1.14.7/umd/popper.min.js2318229.0 s7.8 KiB
g.alicdn.com/code/lib/aos/3.0.0-beta.6/aos.css482783.0 s3.0 KiB
g.alicdn.com/code/lib/lozad.js/1.15.0/lozad.min.js503471.0 s1.7 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 2.6 s
URLTime Spent
lazada.com/2.6 s
lazada.com/en/0.0 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 2.4 s
URLTime Spent
lazada.com/en/2.5 s

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

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 2.2 KiB
URLTransfer SizeEst Savings
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/style.20220408.css8.8 KiB2.2 KiB

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 22.1 KiB
URLTransfer SizeEst Savings
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/bootstrap.4.3.1.min.css23.6 KiB22.1 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 147.4 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/js?id=G-QBXXWM23CD&cx=c&gtm=4e64k0155.4 KiB63.8 KiB
www.googletagmanager.com/gtag/js?id=UA-151331967-1116.4 KiB63.1 KiB
g.alicdn.com/code/lib/jquery/3.5.1/jquery.min.js30.2 KiB20.4 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.
... div.col-xxl-6 > div.wrapper > div.d-none > img.leaders-image
... div.row > div.col-xxl-4 > div.wrapper > img.map-image
... div.col-xxl-6 > div.wrapper > div.d-none > img.leaders-image

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

●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●Improve image delivery
●Optimize viewport for mobile
●Max Potential First Input Delay 20 ms
●Minify JavaScript
●Avoids enormous network payloads Total size was 651 KiB
●User Timing marks and measures 5 user timings
●JavaScript execution time 0.0 s
●Minimizes main-thread work 0.4 s
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 260 ms
●Server Backend Latencies 1,620 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
○INP breakdown
○Avoid long main-thread tasks
○Avoid non-composited animations
○Avoid large layout shifts
100

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.

○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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 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
○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
○Buttons have an accessible name
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○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
○Form elements have associated labels
○Links are distinguishable without relying on color.
○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.
○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.
92

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
www.googletagmanager.com/gtag/js?id=G-QBXXWM23CD&cx=c&gtm=4e64k0 line 230, col 390
Connecting to 'https://region1.google-analytics.com/g/collect?v=2&tid=G-QBXXWM23CD&gtm=45je64k0v887236688za20g&_p=1776891099579&gcd=13l3l3l2l1l1&npa=1&dma_cps=a&dma=1&_eu=AAAI&_geo=1&_rdi=1&are=1&cid=164517523.1776891101&frm=0&pscdl=noapi&rcb=5&ul=en-us&_s=1&tag_exp=0~115616985~115938465~115938468~117266400~117512542~117884344&sid=1776891100&sct=1&seg=0&dl=https%3A%2F%2Flazada.com%2Fen%2F&dt=Home&en=page_view&_fv=1&_nsi=1&_ss=1&tfd=5320' violates the following Content Security Policy directive: "connect-src 'self' 'unsafe-inline' https://sg.mmstat.com https://log.mmstat.com https://www.google-analytics.com https://g.alicdn.com https://dev.g.alicdn.com https://pre-aidc-jobs.alibaba.com https://aidc-jobs.alibaba.com". The action has been blocked.
www.googletagmanager.com/gtag/js?id=G-QBXXWM23CD&cx=c&gtm=4e64k0 line 230, col 390
Fetch API cannot load https://region1.google-analytics.com/g/collect?v=2&tid=G-QBXXWM23CD&gtm=45je64k0v887236688za20g&_p=1776891099579&gcd=13l3l3l2l1l1&npa=1&dma_cps=a&dma=1&_eu=AAAI&_geo=1&_rdi=1&are=1&cid=164517523.1776891101&frm=0&pscdl=noapi&rcb=5&ul=en-us&_s=1&tag_exp=0~115616985~115938465~115938468~117266400~117512542~117884344&sid=1776891100&sct=1&seg=0&dl=https%3A%2F%2Flazada.com%2Fen%2F&dt=Home&en=page_view&_fv=1&_nsi=1&_ss=1&tfd=5320. Refused to connect because it violates the document's Content Security Policy.

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy
●Uses HTTPS
●Avoids deprecated APIs
●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
●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
75

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

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
aidc.jubao.alibaba.com/here
aidc.jubao.alibaba.com/here

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

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #ContentError
3<a id="a-link" href="https://g.alicdn.com/sd/punish/waf_block.html?wh_ttid=pc&qrcode=TuBal8i_p2XaWZv-IOjViw|aek04w|wpE0hg_0|AAAAZQ|0&uuid=4ee05a97c8bfa765da599bfe20e8d58b&origin=https%3A%2F%2Flazada.com%3A443%2Fen%2Frobots.txt"></a>Unknown directive
4<script>Syntax not understood
5 document.getElementById("a-link").click();Syntax not understood
7 window._config_ = {Syntax not understood
8 "action": "block",Unknown directive
9 "url": "https://g.alicdn.com/sd/punish/block_h5.html?wh_ttid=pc&qrcode=TuBal8i_p2XaWZv-IOjViw|aek04w|wpE0hg_0|AAAAZQ|0&uuid=4ee05a97c8bfa765da599bfe20e8d58b&origin=https%3A%2F%2Flazada.com%3A443%2Fen%2Frobots.txt"Unknown directive
10 };Syntax not understood
11</script>Syntax not understood
12<!--rgv587_flag:sm-->Unknown directive

To appear in search results, crawlers need access to your app.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Page has successful HTTP status code
●Links are crawlable
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`

Send Feedback