C — https://lazada.com | BeaverCheck Audit

Site Health

Score: 74 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Reasonable footprint with room for optimization.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

AOS · 48 peers

You 74

Avg 73

At average

0 50 100

Better than 52% of AOS sites See full AOS benchmark →

Bootstrap · 657 peers

You 74

Avg 73

At average

0 50 100

Better than 55% of Bootstrap sites See full Bootstrap benchmark →

Top Priorities (5)

/.svn/entries is publicly accessible

Security gaps expose your site and users to attacks, eroding trust.

Security › Information Leakage

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

is missing width/height — may cause layout shift

Performance issues directly impact user engagement and conversion rates.

Performance › Image Optimization

32 third-party resources (99% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Flazada.com)](https://beavercheck.com/results/76cfbbce-bfd3-4bc6-bfde-0db086534bee)

HTML

<a href="https://beavercheck.com/results/76cfbbce-bfd3-4bc6-bfde-0db086534bee"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Flazada.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Flazada.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 8.0s 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 user trust.

3 security gaps detected — browsers may warn visitors about your site.

Your LCP is 8.0s — fixing the 2 performance criticals could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

1 critical 7 warning

8 barrier(s) likely increasing bounce by ~28%.

Speed (1)

Page takes 8.0s to load

+12% bounce

Users abandon at ~3s — you're 5.5s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Trust (2)

No HSTS header

+1% bounce

Returning 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% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (4)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard 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

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

¥1,925 investment → ¥21,261/month returns + CNY 50,000,000 risk avoided

Payback period: < 1 month First-year ROI: +13153%

Investment

¥1,925

6h · 5 findings

Monthly returns

¥21,261 /mo

~¥255,130 / year

Conversions recovered ¥21,260
Bandwidth savings ¥1.22

Regulatory risk avoided

CNY 50,000,000

if kept compliant

PIPL CNY 50,000,000

Payback period

0 12mo 24mo

¥525 — in quick wins — start here for the fastest payback

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.

Full methodology & sources

Estimated Remediation Cost

¥1,925

5.5 developer hours at ¥350/hr

Based on China rates (¥350/hr)

Quick wins

¥525 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

¥ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

¥4,166,668 / month at risk

~¥50,000,015 / year if left unfixed

Compliance Risk

¥50,000,000

PIPL

No privacy policy link detected
PIPL: CNY 100,000 – CNY 50,000,000
Trackers detected but no cookie policy found
PIPL: CNY 100,000 – CNY 50,000,000
Trackers detected but no privacy policy found
PIPL: CNY 100,000 – CNY 50,000,000

+1 more

Bandwidth Waste

¥1.22 /mo

2142.2 MB/mo × 0.571 CNY/GB

Optimize transfer: save ~214 KB per page load
Saves ¥1.22/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.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

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

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

SEO

Core Web Vitals

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.27 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

7.99 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

139 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.053

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

9.04 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.

8.88 s

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

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.

Why this matters

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/bootstrap.4.3.1.min.css	0.0 ms	24.1 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/style.20220408.css	0.0 ms	8.8 KiB
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/js/base.js	0.0 ms	3.1 KiB
g.alicdn.com/code/lib/jquery/3.5.1/jquery.min.js	2422576.0 s	30.8 KiB
g.alicdn.com/code/lib/twitter-bootstrap/4.3.1/js/bootstrap.min.js	2054960.0 s	15.6 KiB
/aes/??tracker/3.0.0/index.js,tracker-plugin-pv/3.0.1/ind...	500377.0 s	10.3 KiB
g.alicdn.com/alilog/mlog/aplus_int.js	312176.0 s	6.0 KiB
g.alicdn.com/code/lib/aos/3.0.0-beta.6/aos.js	432915.0 s	5.3 KiB
g.alicdn.com/code/lib/popper.js/1.14.7/umd/popper.min.js	2318251.0 s	7.8 KiB
g.alicdn.com/code/lib/aos/3.0.0-beta.6/aos.css	482805.0 s	3.0 KiB
g.alicdn.com/code/lib/lozad.js/1.15.0/lozad.min.js	503493.0 s	1.7 KiB

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:3606.1679990234375 label:Time to first byte subpart:timeToFirstByte] map[duration:1356.8380009765624 label:Resource load delay subpart:resourceLoadDelay] map[duration:300.946 label:Resource load duration subpart:resourceLoadDuration] map[duration:12.691 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: ...

path: 1,HTML,1,BODY,0,MAIN,2,DIV,0,DIV,1,DIV,0,DIV,2,DIV,0,IMG

selector: div.col-xxl-6 > div.wrapper > div.d-block > img.leaders-image

snippet: <img data-srcset="https://lazada-com.oss-ap-southeast-1.aliyuncs.com/static/image/home-a-mal…" class="leaders-image lozad" alt="..." srcset="https://lazada-com.oss-ap-southeast-1.aliyuncs.com/static/image/home-a-mal…" data-loaded="true">

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: ...

path: 1,HTML,1,BODY,0,MAIN,2,DIV,0,DIV,1,DIV,0,DIV,2,DIV,0,IMG

selector: div.col-xxl-6 > div.wrapper > div.d-block > img.leaders-image

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.

URL	Protocol
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/bootstrap.4.3.1.min.css	http/1.1
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/style.20220408.css	http/1.1
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/image/logo_white.svg	http/1.1
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/js/base.js	http/1.1
/static/font/ProximaNovaFonts/proximanova-bold-webfont.woff2	http/1.1
/static/font/ProximaNovaFonts/proximanova-regular-webfont...	http/1.1
/static/font/ProximaNovaFonts/proximanova-semibold-webfon...	http/1.1
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/image/home-a-mall_x1.jpg	http/1.1
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/image/home-hero_x1.webp	http/1.1
/static/image/new-lazada-logo-small.png	http/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.

URL	Transfer Size	Duration
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/style.20220408.css	8.8 KiB	1.2 s
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/bootstrap.4.3.1.min.css	24.1 KiB	1.5 s
g.alicdn.com/code/lib/jquery/3.5.1/jquery.min.js	30.8 KiB	600 ms
g.alicdn.com/code/lib/lozad.js/1.15.0/lozad.min.js	1.7 KiB
g.alicdn.com/code/lib/aos/3.0.0-beta.6/aos.css	3.0 KiB	753 ms

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.8 s

URL	Time Spent
lazada.com/	2.8 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: 1.6 s

URL	Time Spent
lazada.com/en/	1.7 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

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 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: 170 ms 22.7 KiB

URL	Transfer Size	Est Savings
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/bootstrap.4.3.1.min.css	23.6 KiB	22.7 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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

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

Estimated savings: 1.0 s 147.7 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-QBXXWM23CD&cx=c&gtm=4e64k0	155.4 KiB	64.1 KiB
www.googletagmanager.com/gtag/js?id=UA-151331967-1	116.4 KiB	63.1 KiB
g.alicdn.com/code/lib/jquery/3.5.1/jquery.min.js	30.2 KiB	20.4 KiB

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

URL	Transfer Size	Est Savings
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/style.20220408.css	8.8 KiB	2.2 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.

	URL
... `div.col-xxl-6 > div.wrapper > div.d-block > img.leaders-image`	lazada-com.oss-ap-southeast-1.aliyuncs.com/static/image/home-a-mall_x1.jpg
Lazada Logo `div.col-10 > nav.navbar > a.navbar-brand > img`	lazada-com.oss-ap-southeast-1.aliyuncs.com/static/image/logo_white.svg
... `div.row > div.col-xxl-4 > div.wrapper > img.map-image`
... `div.col-xxl-6 > div.wrapper > div.d-block > 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

●Minify JavaScript

●Avoids enormous network payloads Total size was 697 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.6 s

●Minimizes main-thread work 1.2 s

●Avoid long main-thread tasks 5 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 260 ms

●Server Backend Latencies 1,280 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

○Avoid non-composited animations

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
Explore Jobs `div.col-xxl-3 > div.row > div.col-xxl-12 > a.btn`
© 2026 Lazada Group. `div.col-xxl-1 > div.row > div.col-10 > div#copy-right`
To report an issue or file a complaint, click here `div.col-xxl-1 > div.row > div.col-10 > div.d-block`

These are opportunities to improve the legibility of your content.

○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

●Buttons have an accessible name

●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

●Document has a `<title>` element

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

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

●Links are distinguishable without relying on color.

●Links have a discernible name

●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

○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

○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.

○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

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.

Source Description

Source	Description
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=1776891078223&gcd=13l3l3l2l1l1&npa=1&dma_cps=a&dma=1&_eu=AAAI&_geo=1&_rdi=1&are=1&cid=1476987356.1776891080&frm=0&pscdl=noapi&rcb=11&ul=en-us&_s=1&tag_exp=0~115938466~115938468~117266401~117512543~118463262&sid=1776891079&sct=1&seg=0&dl=https%3A%2F%2Flazada.com%2Fen%2F&dt=Home&en=page_view&_fv=1&_nsi=1&_ss=1&tfd=4941' 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=1776891078223&gcd=13l3l3l2l1l1&npa=1&dma_cps=a&dma=1&_eu=AAAI&_geo=1&_rdi=1&are=1&cid=1476987356.1776891080&frm=0&pscdl=noapi&rcb=11&ul=en-us&_s=1&tag_exp=0~115938466~115938468~117266401~117512543~118463262&sid=1776891079&sct=1&seg=0&dl=https%3A%2F%2Flazada.com%2Fen%2F&dt=Home&en=page_view&_fv=1&_nsi=1&_ss=1&tfd=4941. Refused to connect because it violates the document's Content Security Policy.

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=1776891078223&gcd=13l3l3l2l1l1&npa=1&dma_cps=a&dma=1&_eu=AAAI&_geo=1&_rdi=1&are=1&cid=1476987356.1776891080&frm=0&pscdl=noapi&rcb=11&ul=en-us&_s=1&tag_exp=0~115938466~115938468~117266401~117512543~118463262&sid=1776891079&sct=1&seg=0&dl=https%3A%2F%2Flazada.com%2Fen%2F&dt=Home&en=page_view&_fv=1&_nsi=1&_ss=1&tfd=4941' 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=1776891078223&gcd=13l3l3l2l1l1&npa=1&dma_cps=a&dma=1&_eu=AAAI&_geo=1&_rdi=1&are=1&cid=1476987356.1776891080&frm=0&pscdl=noapi&rcb=11&ul=en-us&_s=1&tag_exp=0~115938466~115938468~117266401~117512543~118463262&sid=1776891079&sct=1&seg=0&dl=https%3A%2F%2Flazada.com%2Fen%2F&dt=Home&en=page_view&_fv=1&_nsi=1&_ss=1&tfd=4941. 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

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 destination	Link 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 #	Content	Error
3	`<a id="a-link" href="https://g.alicdn.com/sd/punish/waf_block.html?wh_ttid=pc&qrcode=WKn-_qE48gYbdyGqVJbyQw\|aek0zQ\|wpE0hg_0\|AAAAZQ\|0&uuid=58a9fefea138f2061b7721aa5496f243&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=WKn-_qE48gYbdyGqVJbyQw\|aek0zQ\|wpE0hg_0\|AAAAZQ\|0&uuid=58a9fefea138f2061b7721aa5496f243&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`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

100

Accessibility

Best Practices

SEO

Core Web Vitals

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.

4.72 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

4.72 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 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.

6.37 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.

4.72 s

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.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

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.

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.

URL	Protocol
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/bootstrap.4.3.1.min.css	http/1.1
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/style.20220408.css	http/1.1
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/image/logo_white.svg	http/1.1
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/js/base.js	http/1.1
/static/font/ProximaNovaFonts/proximanova-semibold-webfon...	http/1.1
/static/font/ProximaNovaFonts/proximanova-bold-webfont.woff2	http/1.1
/static/font/ProximaNovaFonts/proximanova-regular-webfont...	http/1.1
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/image/home-hero_x1.webp	http/1.1
/static/image/new-lazada-logo-small.png	http/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.

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.

URL	Transfer Size	Duration
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/bootstrap.4.3.1.min.css	24.1 KiB	1.2 s
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/style.20220408.css	8.8 KiB	968 ms
g.alicdn.com/code/lib/jquery/3.5.1/jquery.min.js	30.8 KiB	80 ms
g.alicdn.com/code/lib/lozad.js/1.15.0/lozad.min.js	1.7 KiB
g.alicdn.com/code/lib/aos/3.0.0-beta.6/aos.css	3.0 KiB	202 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.

Request	Cache TTL	Transfer Size
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/bootstrap.4.3.1.min.css	0.0 ms	24.1 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/style.20220408.css	0.0 ms	8.8 KiB
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/js/base.js	0.0 ms	3.1 KiB
g.alicdn.com/code/lib/jquery/3.5.1/jquery.min.js	2422554.0 s	30.8 KiB
g.alicdn.com/code/lib/twitter-bootstrap/4.3.1/js/bootstrap.min.js	2054938.0 s	15.6 KiB
/aes/??tracker/3.0.0/index.js,tracker-plugin-pv/3.0.1/ind...	500355.0 s	10.3 KiB
g.alicdn.com/alilog/mlog/aplus_int.js	312155.0 s	6.0 KiB
g.alicdn.com/code/lib/aos/3.0.0-beta.6/aos.js	432893.0 s	5.3 KiB
g.alicdn.com/code/lib/popper.js/1.14.7/umd/popper.min.js	2318229.0 s	7.8 KiB
g.alicdn.com/code/lib/aos/3.0.0-beta.6/aos.css	482783.0 s	3.0 KiB
g.alicdn.com/code/lib/lozad.js/1.15.0/lozad.min.js	503471.0 s	1.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

URL	Time 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

URL	Time 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

URL	Transfer Size	Est Savings
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/style.20220408.css	8.8 KiB	2.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

URL	Transfer Size	Est Savings
lazada-com.oss-ap-southeast-1.aliyuncs.com/static/css/bootstrap.4.3.1.min.css	23.6 KiB	22.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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 147.4 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-QBXXWM23CD&cx=c&gtm=4e64k0	155.4 KiB	63.8 KiB
www.googletagmanager.com/gtag/js?id=UA-151331967-1	116.4 KiB	63.1 KiB
g.alicdn.com/code/lib/jquery/3.5.1/jquery.min.js	30.2 KiB	20.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

○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.

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.

Source Description

Source	Description
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.

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.

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

SEO

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 destination	Link 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 #	Content	Error
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`

Results for https://lazada.com

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (1)

Trust (2)

Content (4)

Navigation (1)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Best Practices

General

SEO

Content Best Practices

Crawling and Indexing

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best Practices

General

SEO

Content Best Practices

Crawling and Indexing

Keyboard Shortcuts