Skip to content
https://amap.com

Lighthouse Desktop

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

Detailed Report

Audit breakdown by category with detailed findings.

32

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.

RequestCache TTLTransfer Size
webapi.amap.com/theme/v1.3/controlbar/ctb.png0.0 ms91.2 KiB
o4.amap.com/icon/2.0.2.45/v1/1_0_s/icons_9?key=d1f15ad3fdf0c704434eaf23c7c186980.0 ms75.0 KiB
o4.amap.com/icon/2.0.2.45/v1/1_0_s/icons_1?key=d1f15ad3fdf0c704434eaf23c7c186980.0 ms47.3 KiB
o4.amap.com/icon/2.0.2.45/v1/1_0_s/icons_4?key=d1f15ad3fdf0c704434eaf23c7c186980.0 ms38.4 KiB
o4.amap.com/icon/2.0.2.45/v1/1_0_s/icons_64?key=d1f15ad3fdf0c704434eaf23c7c186980.0 ms37.1 KiB
/captcha-frontend/FeiLin/1.3.8/feilin021.58524ceb599edc58...2536745.0 s220.9 KiB
g.alicdn.com/AWSC/fireyejs/1.231.67/fireyejs.js2266013.0 s191.3 KiB
g.alicdn.com/captcha-frontend/dynamicJS/3.25.1/sg.041.f71ffcc04ab32956.js1855967.0 s150.4 KiB
g.alicdn.com/AWSC/et/1.83.41/et_f.js1651185.0 s109.7 KiB
g.alicdn.com/??AWSC/AWSC/awsc.js,sd/baxia-entry/baxiaCommon.js4963.0 s11.7 KiB
o.alicdn.com/captcha-frontend/aliyunCaptcha/AliyunCaptcha.js604800.0 s77.6 KiB
o.alicdn.com/baxia/baxia-entry-gray/index.js15.0 s6.8 KiB
/aes/??tracker/3.3.9/index.js,tracker-plugin-pv/3.0.6/ind...521324.0 s38.1 KiB
webapi.amap.com/theme/v2.0/logo@1x.png0.0 ms2.5 KiB
g.alicdn.com/??/sd/baxia/2.5.36/baxiaCommon.js1724601.0 s14.0 KiB
/dt/tracker/4.3.1/??tracker.Tracker.js,tracker.interfaceT...577817.0 s7.6 KiB
/_AMapService/v3/ip?key=d1f15ad3fdf0c704434eaf23c7c18698&...0.0 ms828 B
/_AMapService/v3/log/init?eventId=monitor.cdn&s=rsv3&prod...0.0 ms730 B
/_AMapService/v3/log/init?eventId=resource.load&s=rsv3&pr...0.0 ms729 B
g.alicdn.com/captcha-frontend/dynamicJS/3.25.1/main.css1851678.0 s6.9 KiB
g.alicdn.com/alilog/mlog/aplus_v2.js2237431.0 s6.5 KiB
w.cnzz.com/q_stat.php?id=1255626299&l=390.0 s372 B
5b2tin.tdum.alibaba.com/dss.js0.0 ms312 B
/ts?url=&token=gCoMkBmIJaXXw55eqsr6JKjUeHYLflZbojIYMoF28W...0.0 ms140 B
g.alicdn.com/alilog/mlog/aplus_v2.js2237431.0 s0 B

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:2.427 source:map[column:168010 line:0 type:source-location url:https://o.alicdn.com/captcha-frontend/aliyunCaptcha/AliyunCaptcha.js urlProvider:network]]]

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.

URLResource SizeEst Savings
div.root--jss-0-9 > div#left1776802855926 > a > img.leftImg--jss-0-28 div.root--jss-0-9 > div#left1776802855926 > a > img.leftImg--jss-0-28
a.amap.com/lbs-p/static/banner/passport_left_banner_default.jpg621.2 KiB590.3 KiB
div#themap > div.amap-controls > div.amap-control > div.amap-luopan div#themap > div.amap-controls > div.amap-control > div.amap-luopan
webapi.amap.com/theme/v1.3/controlbar/ctb.png94.4 KiB30.1 KiB
div.app-download-content > div.app-download-content__wrapper > div.app-download-qrcode > img.bannerQrcode div.app-download-content > div.app-download-content__wrapper > div.app-download-qrcode > img.bannerQrcode
amap.com/assets/biz/app-download/imgs/qrcode-2.png12.5 KiB12.1 KiB
div#rightInner1776802855926 > div#login-footer1776802855926 > div#message-login-agreement1776802855926 > div#messageLoginAgreementCheckedIcon1776802855926 div#rightInner1776802855926 > div#login-footer1776802855926 > div#message-login-agreement1776802855926 > div#messageLoginAgreementCheckedIcon1776802855926
a.amap.com/lbs-p/static/img/icons-0e114446.png12.3 KiB7.4 KiB

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:903.548 label:Time to first byte subpart:timeToFirstByte] map[duration:6708.043 label:Resource load delay subpart:resourceLoadDelay] map[duration:760.987 label:Resource load duration subpart:resourceLoadDuration] map[duration:39.498 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: div.root--jss-0-9 > div#left1776802855926 > a > img.leftImg--jss-0-28
path: 1,HTML,1,BODY,32,DIV,0,DIV,1,DIV,0,A,0,IMG
selector: div.root--jss-0-9 > div#left1776802855926 > a > img.leftImg--jss-0-28
snippet: <img class="leftImg--jss-0-28" alt="" src="https://a.amap.com/lbs-p/static/banner/passport_left_banner_default.jpg">

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: div.root--jss-0-9 > div#left1776802855926 > a > img.leftImg--jss-0-28
path: 1,HTML,1,BODY,32,DIV,0,DIV,1,DIV,0,A,0,IMG
selector: div.root--jss-0-9 > div#left1776802855926 > a > img.leftImg--jss-0-28
snippet: <img class="leftImg--jss-0-28" alt="" src="https://a.amap.com/lbs-p/static/banner/passport_left_banner_default.jpg">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLProtocol
amap.com/http/1.1
amap.com/assets/lib/mapTracker.jshttp/1.1
/maps?v=2.0&key=d1f15ad3fdf0c704434eaf23c7c18698&plugin=A...http/1.1
amap.com/build/map.c166ed75c4bbd270774c.jshttp/1.1
amap.com/service/locator?rand=0.4306063523654644http/1.1
/_AMapService/v3/log/init?eventId=resource.load&s=rsv3&pr...http/1.1
/mapsplugin?v=2.3.5.6&cls=AMap.MarkerClusterer&key=d1f15a...http/1.1
/mapsplugin?v=2.3.5.6&cls=AMap.Driving&key=d1f15ad3fdf0c7...http/1.1
/mapsplugin?v=2.3.5.6&cls=AMap.Transfer&key=d1f15ad3fdf0c...http/1.1
/mapsplugin?v=2.3.5.6&cls=AMap.Walking&key=d1f15ad3fdf0c7...http/1.1
/mapsplugin?v=2.3.5.6&cls=WebGLRender&key=d1f15ad3fdf0c70...http/1.1
/mapsplugin?v=2.3.5.6&cls=AMap.ControlBar&key=d1f15ad3fdf...http/1.1
webapi.amap.com/theme/v2.0/logo@1x.pnghttp/1.1
amap.com/build/lib.c166ed75c4bbd270774c.jshttp/1.1
amap.com/build/tools.c166ed75c4bbd270774c.jshttp/1.1
amap.com/build/main.c166ed75c4bbd270774c.jshttp/1.1
webapi.amap.com/theme/v1.3/controlbar/ctb.pnghttp/1.1
/maps/checkredirect?key=d1f15ad3fdf0c704434eaf23c7c18698&...http/1.1
/_AMapService/v3/log/init?eventId=monitor.cdn&s=rsv3&prod...http/1.1
amap.com/service/seo/trackhttp/1.1
amap.com/build/0.ad2037f422a90dbf8d1e.jshttp/1.1
amap.com/build/plugincss.e9c53b048845b31d3be8.jshttp/1.1
amap.com/assets/img/icon/ic-report-s.svghttp/1.1
amap.com/assets/biz/app-download/imgs/phone-icon.pnghttp/1.1
amap.com/assets/biz/app-download/imgs/close-btn.pnghttp/1.1
/mapsplugin?v=2.3.5.6&cls=AMap.Geolocation&key=d1f15ad3fd...http/1.1
amap.com/service/checklogin?http/1.1
amap.com/assets/img/scale.pnghttp/1.1
amap.com/service/cityList?version=http/1.1
amap.com/service/weather?adcode=110000http/1.1
amap.com/build/favesapi.830ccdc55fd720e349ec.jshttp/1.1
/assets/a.gif?uuid=a882ba4a-40ed-4893-8be6-baf398284281&p...http/1.1
amap.com/assets/biz/app-download/imgs/qrcode-2.pnghttp/1.1
amap.com/build/canvasjs.fcd63bc5dd75415ff597.jshttp/1.1
/mapsplugin?v=2.3.5.6&cls=AMap.CustomLayer&key=d1f15ad3fd...http/1.1
/assets/a.gif?uuid=a882ba4a-40ed-4893-8be6-baf398284281&p...http/1.1
amap.com/service/cardQueryhttp/1.1
/maps/ipLocation?platform=JS&s=rsv3&logversion=2.0&key=d1...http/1.1
amap.com/assets/img/defavatar.pnghttp/1.1
amap.com/service/fav/getFav?ver=http/1.1
amap.com/service/getHistory?type=301http/1.1
/mapsplugin?v=2.3.5.6&cls=AMap.Scale,AMap.RangingTool,AMa...http/1.1
amap.com/assets/tpl/canvas-contextMenu.html?v=1776802858596http/1.1
amap.com/service/regeo?longitude=116.405285&latitude=39.90871http/1.1
/mapsplugin?v=2.3.5.6&cls=AMap.CitySearch&key=d1f15ad3fdf...http/1.1
amap.com/assets/img/icon/ic-collection-o-r.svghttp/1.1
/assets/a.gif?uuid=a882ba4a-40ed-4893-8be6-baf398284281&p...http/1.1
/_AMapService/v3/ip?key=d1f15ad3fdf0c704434eaf23c7c18698&...http/1.1
amap.com/assets/img/beian.pnghttp/1.1

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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.

CategoryTime Spent
Other1.8 s
Script Evaluation1.5 s
Style & Layout156 ms
Script Parsing & Compilation126 ms
Rendering52 ms
Garbage Collection33 ms
Parse HTML & CSS13 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 reasonFailure type
The page has an unload handler in the main frame.Actionable
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable

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.8 KiB
URLTransfer SizeEst Savings
:root{--aliyun-captcha-z-index-base: 10000000} …4.1 KiB2.8 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.root--jss-0-9 > div#left1776802855926 > a > img.leftImg--jss-0-28 div.root--jss-0-9 > div#left1776802855926 > a > img.leftImg--jss-0-28
a.amap.com/lbs-p/static/banner/passport_left_banner_default.jpg
div.amap-copyright > span > a > img div.amap-copyright > span > a > img
amap.com/assets/img/beian.png

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

●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●Optimize viewport for mobile
●Minify JavaScript
●Reduce unused CSS
●Avoid long main-thread tasks 19 long tasks found
●Avoid non-composited animations 1 animated element found
●Network Requests
●Network Round Trip Times 290 ms
●Server Backend Latencies 110 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 390 ms
●Avoid large layout shifts 4 layout shifts found
○INP breakdown
○User Timing marks and measures
76

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
body > section#search > header.searchbox > img.usel body > section#search > header.searchbox > img.usel
section#search > header.searchbox > div.direntry > img.fa-dir section#search > header.searchbox > div.direntry > img.fa-dir
body > div#themap > a.amap-logo > img body > div#themap > a.amap-logo > img
div.amap-copyright > span > a > img div.amap-copyright > span > a > img
div.app-download-content > div.app-download-content__wrapper > div.app-download-qrcode > img.bannerQrcode div.app-download-content > div.app-download-content__wrapper > div.app-download-qrcode > img.bannerQrcode

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#themap > iframe body > div#themap > 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.mask--jss-0-16 > div.root--jss-0-9 > div#left1776802855926 > a div.mask--jss-0-16 > div.root--jss-0-9 > div#left1776802855926 > a

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.

○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
●Form elements have associated labels
●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
●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.
○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">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<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.
73

Best Practices

Trust and Safety

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.

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 / WarningSource
Unload event listeners are deprecated and will be removed.
Fledge
SharedStorage

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
%c%d font-size:0;color:transparent NaN

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.

●Uses HTTPS
●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
83

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 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#layerbox > div#layerbox_item > div.show-list > a.layer_item
路况 div#layerbox > div#layerbox_item > div.show-list > a.layer_item
测距 div#layerbox > div#layerbox_item > div.show-list > a.tool_item
地铁 div#layerbox > div#layerbox_item > div.show-list > a.layer_item
全屏 div#layerbox > div#layerbox_item > div.show-list > a.tool_item
更多 div#layerbox > div#layerbox_item > div.show-list > a.tool_item
邮编 div#layerbox > div#layerbox_item > div.postcode-dropdown > a.tool_item
刷新二维码 div#qrcodeLogin1776802855926 > div.qrcodeImgWrapper--jss-0-169 > div#refreshWrapper1776802855926 > a#refreshQrcode1776802855926

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
body > section#search > header.searchbox > img.usel body > section#search > header.searchbox > img.usel
section#search > header.searchbox > div.direntry > img.fa-dir section#search > header.searchbox > div.direntry > img.fa-dir
body > div#themap > a.amap-logo > img body > div#themap > a.amap-logo > img
div.amap-copyright > span > a > img div.amap-copyright > span > a > img
div.app-download-content > div.app-download-content__wrapper > div.app-download-qrcode > img.bannerQrcode div.app-download-content > div.app-download-content__wrapper > div.app-download-qrcode > img.bannerQrcode

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

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●robots.txt is valid
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`

Send Feedback