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.

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
o4.amap.com/icon/2.0.2.45/v1/1_0_s/icons_9?key=ab403a9b356e63c917ff05b037cd3e7d	0.0 ms	75.0 KiB
o4.amap.com/icon/2.0.2.45/v1/1_0_s/icons_1?key=ab403a9b356e63c917ff05b037cd3e7d	0.0 ms	47.3 KiB
o4.amap.com/icon/2.0.2.45/v1/1_0_s/icons_4?key=ab403a9b356e63c917ff05b037cd3e7d	0.0 ms	38.4 KiB
o4.amap.com/icon/2.0.2.45/v1/1_0_s/icons_64?key=ab403a9b356e63c917ff05b037cd3e7d	0.0 ms	37.1 KiB
g.alicdn.com/AWSC/fireyejs/1.231.67/fireyejs.js	2266037.0 s	191.3 KiB
g.alicdn.com/AWSC/et/1.83.41/et_f.js	1651192.0 s	109.7 KiB
g.alicdn.com/??/AWSC/AWSC/awsc.js,/sd/baxia-entry/baxiaCommon.js	4109.0 s	11.2 KiB
g.alicdn.com/AWSC/et/1.77.4/et_f.js	2252987.0 s	85.7 KiB
webapi.amap.com/theme/v2.0/logo@2x.png	0.0 ms	4.8 KiB
/aes/??tracker/3.3.9/index.js,tracker-plugin-pv/3.0.6/ind...	521976.0 s	23.3 KiB
g.alicdn.com/code/npm/@alife/amap-tracker/0.1.0/index.umd.es5.production.js	366005.0 s	9.1 KiB
g.alicdn.com/??/sd/baxia/2.5.36/baxiaCommon.js	1724622.0 s	14.0 KiB
g.alicdn.com/secdev/entry/index.js	2193.0 s	1.2 KiB
g.alicdn.com/alilog/mlog/aplus_wap.js	2312414.0 s	6.0 KiB
/_AMapService/v3/log/init?eventId=resource.load&s=rsv3&pr...	0.0 ms	533 B
/_AMapService/v3/log/init?eventId=monitor.cdn&s=rsv3&prod...	0.0 ms	533 B
48kx9i.tdum.alibaba.com/dss.js	0.0 ms	313 B
g.alicdn.com/AWSC/et/1.83.41/et_f.js	1651192.0 s	0 B
g.alicdn.com/??/sd/baxia/2.5.36/baxiaCommon.js	1724622.0 s	0 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.103281] map[node:map[boundingRect:map[bottom:823 height:738 left:0 right:412 top:85 width:412] lhId:page-1-DIV nodeLabel:50 公里 path:1,HTML,1,BODY,18,DIV,0,DIV selector:body.pg-index > div.common_center > div.map_all snippet:<div class="map_all default_map_action" style="z-index: 3; display: block; top: 85px;"> type:node] score:0.103281]]

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:1855.5700009765626 label:Time to first byte subpart:timeToFirstByte] map[duration:3021.3139990234376 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-DIV

nodeLabel: 50 公里

path: 1,HTML,1,BODY,18,DIV,0,DIV,0,DIV

selector: body.pg-index > div.common_center > div.map_all > div#map

snippet: <div id="map" class="amap-container" style="background-color: rgb(247, 247, 247);">

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
res.wx.qq.com/open/js/jweixin-1.6.0.js	13.2 KiB	1.2 s
a.amap.com/pc/static/config/config_m/lbs_m_about.js	1.0 KiB	933 ms
/aes/??tracker/3.3.9/index.js,tracker-plugin-pv/3.0.6/ind...	23.3 KiB	1.4 s
g.alicdn.com/alilog/mlog/aplus_wap.js	6.0 KiB	903 ms
g.alicdn.com/code/npm/@alife/amap-tracker/0.1.0/index.umd.es5.production.js	9.1 KiB	1.1 s
g.alicdn.com/secdev/entry/index.js	1.2 KiB	753 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
地图路线附近 `body.pg-index > div.common_navi > div.mainnavibar`	m.amap.com/img/common/common_header_icon_new.png?v=e1c5711d	6.0 KiB	4.8 KiB

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
/maps?v=2.0&key=d1f15ad3fdf0c704434eaf23c7c18698&plugin=A...	http/1.1
/maps?v=2.0&key=ab403a9b356e63c917ff05b037cd3e7d&plugin=A...	http/1.1
/mapsplugin?v=2.3.5.6&cls=WebGLRender&key=ab403a9b356e63c...	http/1.1
webapi.amap.com/theme/v2.0/logo@2x.png	http/1.1
webapi.amap.com/maps/ipCity?key=ed87ba018e839b372c6c4c75878b542c&callback=jsonp2	http/1.1
/maps/checkredirect?key=ab403a9b356e63c917ff05b037cd3e7d&...	http/1.1

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: 3.3 s

URL	Time Spent
amap.com/	1.8 s
m.amap.com/?amapexchange=%2F	1.5 s
m.amap.com/	0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
50 公里 `body.pg-index > div.common_center > div.map_all`	0.103

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 2.0 s 356.3 KiB

URL	Transfer Size	Est Savings
/maps?v=2.0&key=ab403a9b356e63c917ff05b037cd3e7d&plugin=A...	285.2 KiB	180.0 KiB
m.amap.com/	165.1 KiB	134.6 KiB
amap.com/assets/lib/mapTracker.js	55.1 KiB	21.0 KiB
g.alicdn.com/AWSC/et/1.77.4/et_f.js	85.7 KiB	20.7 KiB

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
/maps?v=2.0&key=ab403a9b356e63c917ff05b037cd3e7d&plugin=A...	5.4 s	1.9 s	80 ms
/aes/??tracker/3.3.9/index.js,tracker-plugin-pv/3.0.6/ind...	2.5 s	2.3 s	72 ms
Unattributable	641 ms	8.1 ms	0.3 ms
g.alicdn.com/AWSC/et/1.83.41/et_f.js	588 ms	497 ms	50 ms
a.amap.com/pc/static/config/config_m/mapTracker.js	546 ms	514 ms	14 ms
m.amap.com/	513 ms	242 ms	130 ms
amap.com/assets/lib/mapTracker.js	307 ms	281 ms	9.4 ms
g.alicdn.com/AWSC/fireyejs/1.231.67/fireyejs.js	245 ms	208 ms	34 ms
/mapsplugin?v=2.3.5.6&cls=WebGLRender&key=ab403a9b356e63c...	190 ms	155 ms	34 ms
g.alicdn.com/alilog/mlog/aplus_wap.js	144 ms	107 ms	35 ms
g.alicdn.com/??/sd/baxia/2.5.36/baxiaCommon.js	81 ms	23 ms	6.5 ms
g.alicdn.com/AWSC/et/1.77.4/et_f.js	73 ms	52 ms	20 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	6.7 s
Other	4.2 s
Script Parsing & Compilation	508 ms
Garbage Collection	131 ms
Style & Layout	102 ms
Parse HTML & CSS	66 ms
Rendering	22 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

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 60.1 KiB

URL	Transfer Size	Est Savings
@charset "UTF-8";html,body,div,span,form,iframe,h1,h2,h3,h4,h5,p,em,img,ol,ul,li{margin:0;padding:0; … } …	49.4 KiB	48.3 KiB
@charset "UTF-8";.detail_header_container{height:45px;background:#fff;display:flex; … } …	11.8 KiB	11.8 KiB

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

●Optimize DOM size

●Font display

●Forced reflow

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,423 KiB

●Avoid long main-thread tasks 20 long tasks found

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

●Network Requests

●Network Round Trip Times 290 ms

●Server Backend Latencies 210 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP request discovery

○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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.searchbox_bar > form.C_search_index_form > div.inputbox > button.button `div.searchbox_bar > form.C_search_index_form > div.inputbox > button.button`

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
div.common_center > div.map_all > div#map > iframe `div.common_center > div.map_all > div#map > iframe`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.common_center > div.map_all > div.map_zoom > a.map_zoomin `div.common_center > div.map_all > div.map_zoom > a.map_zoomin`
div.common_center > div.map_all > div.map_zoom > a.map_zoomout `div.common_center > div.map_all > div.map_zoom > a.map_zoomout`
body.pg-index > div.common_center > div.map_all > a.map_locate `body.pg-index > div.common_center > div.map_all > a.map_locate`

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.

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
div.searchbox_bar > form.C_search_index_form > div.inputbox > input.C_commonInput `div.searchbox_bar > form.C_search_index_form > div.inputbox > input.C_commonInput`

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

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

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

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

●Form elements have associated labels

●Document has a `<title>` element

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

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

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

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

○`[accesskey]` values are unique

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

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

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

○Deprecated ARIA roles were not used

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

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

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

○`[role]` values are valid

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

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

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

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

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

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

○ARIA IDs are unique

○No form fields have multiple labels

○Heading elements appear in a sequentially-descending order

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

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

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

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

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

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

Best Practices

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
?sourceApplication=amap_mo&page_url=index_index&page_type...	Allowed

Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more about the geolocation permission.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source
a.amap.com/pc/static/config/config_m/mapTracker.js

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
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
127.0.0.1:6677/geolocation?to=3000&_=1776802835870&callback=jsonp1	`Failed to load resource: net::ERR_CONNECTION_REFUSED`

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
/maps?v=2.0&key=ab403a9b356e63c917ff05b037cd3e7d&plugin=A...
m.amap.com/

●Avoids third-party cookies

●Allows users to paste into input fields

●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

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

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://m.amap.com/robots.txt`

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
地图 `div.common_navi > div.mainnavibar > div.J_prevent > a`
路线 `div.common_navi > div.mainnavibar > div.J_prevent > a`
附近 `div.common_navi > div.mainnavibar > div#wx_open_app_go_nearby > a`

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

○Structured data is valid

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●robots.txt is valid

●Document has a valid `hreflang`

○Image elements have `[alt]` attributes

○Document has a valid `rel=canonical`