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.

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.

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,2,DIV,0,DIV,0,DIV,2,DIV,0,DIV,0,DIV,0,A,0,IMG

selector: div.icons3-wrapper-inner > div.icons3-item-wrapper-first > a.icons3-item > img.icons3-item-img

snippet: <img class="icons3-item-img" draggable="true" src="//gw.alicdn.com/imgextra/i2/O1CN01qrrUAN1wRjrhtfk6Q_!!6000000006305-2-tps-…" alt="淘票票">

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

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
g.alicdn.com/sd/ncpc/nc.js?t=2015052012	3600.0 s	56.5 KiB
ugcdn.taobao.com/app/starlink/core/m.js?id=2690	0.0 ms	26.5 KiB
ugcdn.taobao.com/app/starlink/core/m.js?id=2690	0.0 ms	26.5 KiB
ugcdn.taobao.com/app/starlink/core/m.js?id=2690	0.0 ms	26.5 KiB
ugcdn.taobao.com/app/starlink/core/index.js?id=169	0.0 ms	26.5 KiB
g.alicdn.com/??/AWSC/AWSC/awsc.js,/sd/baxia/2.5.31/baxiaCommon.js	7200.0 s	17.4 KiB
o.alicdn.com/baxia/baxia-entry-gray/index.js	15.0 s	6.6 KiB
o.alicdn.com/baxia/baxia-entry-gray/index.js	15.0 s	6.6 KiB
g.alicdn.com/AWSC/AWSC/awsc.js	7200.0 s	3.9 KiB
g.alicdn.com/AWSC/AWSC/awsc.js	7200.0 s	3.9 KiB
o.alicdn.com/baxia/baxia-entry-gray/index.js	15.0 s	314 B
/nocaptcha/initialize.jsonp?a=CF_APP_TBLogin_PC&t=7f936fa...	0.0 ms	277 B
/nocaptcha/initialize.jsonp?a=CF_APP_TBLogin_PC&t=7f939fa...	0.0 ms	276 B
/nocaptcha/initialize.jsonp?a=CF_APP_TBLogin_PC&t=7f936fa...	0.0 ms	275 B
o.alicdn.com/baxia/baxia-entry-gray/index.js	15.0 s	203 B
g.alicdn.com/sd/ncpc/nc.js?t=2015052012	3600.0 s	0 B
g.alicdn.com/sd/ncpc/nc.js?t=2015052012	3600.0 s	0 B
g.alicdn.com/??/AWSC/AWSC/awsc.js,/sd/baxia/2.5.31/baxiaCommon.js	7200.0 s	0 B
g.alicdn.com/??/AWSC/AWSC/awsc.js,/sd/baxia/2.5.31/baxiaCommon.js	7200.0 s	0 B
g.alicdn.com/AWSC/AWSC/awsc.js	7200.0 s	0 B
g.alicdn.com/AWSC/AWSC/awsc.js	7200.0 s	0 B

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

URL	Time Spent
taobao.com/	1.4 s
www.taobao.com/	751 ms
main.m.taobao.com/?sprefer=sypc00	0.0 ms

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 JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 150 ms 21.5 KiB

URL	Transfer Size	Est Savings
g.alicdn.com/dinamic/h5-tb-home/3.3.45/index.min.js	104.9 KiB	21.5 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: 150 ms 542.4 KiB

URL	Transfer Size	Est Savings
x.alicdn.com/vip/havana-nlogin/0.10.35/index.js	228.2 KiB	136.5 KiB
x.alicdn.com/vip/havana-nlogin/0.10.35/index.js	228.2 KiB	136.5 KiB
x.alicdn.com/vip/havana-nlogin/0.10.35/index.js	228.2 KiB	136.3 KiB
g.alicdn.com/dinamic/h5-tb-home/3.3.45/index.min.js	104.6 KiB	35.1 KiB
g.alicdn.com/sd/ncpc/nc.js?t=2015052012	56.1 KiB	32.7 KiB
g.alicdn.com/sd/ncpc/nc.js?t=2015052012	56.1 KiB	32.6 KiB
g.alicdn.com/sd/ncpc/nc.js?t=2015052012	56.1 KiB	32.6 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
g.alicdn.com/AWSC/fireyejs/1.234.20/fireyejs.js	3.8 s	3.4 s	342 ms
x.alicdn.com/vip/havana-nlogin/0.10.35/index.js	3.0 s	2.1 s	380 ms
Unattributable	2.2 s	704 ms	0.0 ms
g.alicdn.com/AWSC/WebUMID/1.93.0/um.js	1.7 s	687 ms	86 ms
g.alicdn.com/AWSC/et/1.83.41/et_f.js	1.7 s	1.5 s	141 ms
g.alicdn.com/AWSC/uab/1.140.0/collina.js	590 ms	430 ms	145 ms
g.alicdn.com/alilog/mlog/aplus_v2.js	557 ms	428 ms	110 ms
g.alicdn.com/sd/ncpc/nc.js?t=2015052012	404 ms	243 ms	124 ms
main.m.taobao.com/?sprefer=sypc00	342 ms	77 ms	3.1 ms
/login.htm?redirectURL=https%3A%2F%2Fh5api.m.taobao.com%3...	321 ms	43 ms	22 ms
g.alicdn.com/dinamic/h5-tb-home/3.3.45/index.min.js	238 ms	172 ms	62 ms
g.alicdn.com/mtb/lib-mtop/2.6.1/mtop.js	201 ms	174 ms	17 ms
g.alicdn.com/??/AWSC/AWSC/awsc.js,/sd/baxia/2.5.31/baxiaCommon.js	193 ms	128 ms	27 ms
/??jstracker/sdk-assests/5.6.29/index.js,universal/polyfi...	191 ms	125 ms	9.9 ms
/h5/mtop.taobao.wireless.home.awesome.h5.get/1.0/?jsv=2.6...	183 ms	129 ms	4.3 ms
ugcdn.taobao.com/app/starlink/core/m.js?id=2690	170 ms	112 ms	40 ms
g.alicdn.com/sd/baxia/2.5.36/baxiaCommon.js	146 ms	123 ms	4.7 ms
ugcdn.taobao.com/app/starlink/core/index.js?id=169	143 ms	126 ms	13 ms
g.alicdn.com/alilog/mlog/aplus_wap.js	128 ms	93 ms	32 ms
/login.htm?redirectURL=https%3A%2F%2Fh5api.m.taobao.com%3...	122 ms	23 ms	8.8 ms
/login.htm?redirectURL=https%3A%2F%2Fh5api.m.taobao.com%3...	110 ms	21 ms	7.9 ms
o.alicdn.com/baxia/baxia-entry-gray/index.js	96 ms	77 ms	9.7 ms
g.alicdn.com/secdev/sufei_data/3.9.14/index.js	79 ms	64 ms	14 ms
/h5/com.taobao.wireless.chanel.realtimerecommond/2.0/?jsv...	56 ms	50 ms	4.5 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	11.2 s
Other	1.8 s
Style & Layout	1.7 s
Script Parsing & Compilation	1.6 s
Garbage Collection	235 ms
Parse HTML & CSS	129 ms
Rendering	115 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
The page has an unload handler in the main frame.	Actionable
The page has an unload handler in a sub frame.	Actionable

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

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Reduce unused CSS

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

●Avoid long main-thread tasks 20 long tasks found

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

●Network Requests

●Network Round Trip Times 260 ms

●Server Backend Latencies 180 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 4 layout shifts found

○INP breakdown

○User Timing marks and measures

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

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.sc-ifAKCX > div.topbar-wrapper > div.topbar-hd > img.logo `div.sc-ifAKCX > div.topbar-wrapper > div.topbar-hd > img.logo`
div.topbar-wrapper > div.topbar-ld > div > img.signIn `div.topbar-wrapper > div.topbar-ld > div > img.signIn`
body > div.J_MIDDLEWARE_FRAME_WIDGET > div > img `body > div.J_MIDDLEWARE_FRAME_WIDGET > div > img`
body > div#tcodeSideBar > img `body > div#tcodeSideBar > img`
body > div#tcodeSideBar > img `body > div#tcodeSideBar > img`
body > div.J_MIDDLEWARE_FRAME_WIDGET > div > img `body > div.J_MIDDLEWARE_FRAME_WIDGET > div > img`

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > div.J_MIDDLEWARE_FRAME_WIDGET > iframe `body > div.J_MIDDLEWARE_FRAME_WIDGET > iframe`
body > div.J_MIDDLEWARE_FRAME_WIDGET > iframe `body > div.J_MIDDLEWARE_FRAME_WIDGET > iframe`
body > div.baxia-dialog > div.baxia-dialog-content > iframe#baxia-dialog-content `body > div.baxia-dialog > div.baxia-dialog-content > iframe#baxia-dialog-content`

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●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

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

○`[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

○Heading elements appear in a sequentially-descending order

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

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

○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

○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

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URL	Request Resolution
/tbopen/index.html?h5Url=https%3A%2F%2Fm.taobao.com%2Find...	Allowed

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
Unload event listeners are deprecated and will be removed.	g.alicdn.com/AWSC/et/1.83.41/et_f.js line 1, col 263123

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
g.alicdn.com/AWSC/fireyejs/1.234.20/fireyejs.js	`Permissions policy violation: accelerometer is not allowed in this document.`
g.alicdn.com/AWSC/uab/1.140.0/collina.js line 1, col 28648	`Permissions policy violation: accelerometer is not allowed in this document.`
g.alicdn.com/AWSC/fireyejs/1.234.20/fireyejs.js	`Permissions policy violation: accelerometer is not allowed in this document.`
g.alicdn.com/secdev/sufei_data/3.9.14/index.js	`Permissions policy violation: accelerometer is not allowed in this document.`
g.alicdn.com/AWSC/fireyejs/1.234.20/fireyejs.js	`Permissions policy violation: accelerometer is not allowed in this document.`
g.alicdn.com/AWSC/fireyejs/1.234.20/fireyejs.js	`Permissions policy violation: accelerometer is not allowed in this document.`
g.alicdn.com/AWSC/uab/1.140.0/collina.js line 1, col 28648	`Permissions policy violation: accelerometer is not allowed in this document.`
g.alicdn.com/AWSC/fireyejs/1.234.20/fireyejs.js	`Permissions policy violation: accelerometer is not allowed in this document.`
g.alicdn.com/AWSC/fireyejs/1.234.20/fireyejs.js	`Permissions policy violation: accelerometer is not allowed in this document.`
g.alicdn.com/AWSC/uab/1.140.0/collina.js line 1, col 28648	`Permissions policy violation: accelerometer is not allowed in this document.`
g.alicdn.com/secdev/sufei_data/3.9.14/index.js	`Permissions policy violation: accelerometer is not allowed in this document.`
g.alicdn.com/secdev/sufei_data/3.9.14/index.js	`Permissions policy violation: accelerometer is not allowed in this document.`
g.alicdn.com/secdev/sufei_data/3.9.14/index.js	`Permissions policy violation: gyroscope is not allowed in this document.`
g.alicdn.com/secdev/sufei_data/3.9.14/index.js	`Permissions policy violation: gyroscope is not allowed in this document.`
g.alicdn.com/secdev/sufei_data/3.9.14/index.js	`Permissions policy violation: gyroscope is not allowed in this document.`

●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 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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

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.

Crawling and Indexing

Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
`https://main.m.taobao.com/robots.txt`

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

Content Best Practices

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.sc-ifAKCX > div.topbar-wrapper > div.topbar-hd > img.logo `div.sc-ifAKCX > div.topbar-wrapper > div.topbar-hd > img.logo`
div.topbar-wrapper > div.topbar-ld > div > img.signIn `div.topbar-wrapper > div.topbar-ld > div > img.signIn`
body > div.J_MIDDLEWARE_FRAME_WIDGET > div > img `body > div.J_MIDDLEWARE_FRAME_WIDGET > div > img`
body > div#tcodeSideBar > img `body > div#tcodeSideBar > img`
body > div#tcodeSideBar > img `body > div#tcodeSideBar > img`
body > div.J_MIDDLEWARE_FRAME_WIDGET > div > img `body > div.J_MIDDLEWARE_FRAME_WIDGET > div > img`

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

○Structured data is valid

●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

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`