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
j1.58cdn.com.cn/m58/m3/js/jq.mobi.min_v20190517180203.js	0.0 ms	6.4 KiB
c.58cdn.com.cn/m58/m3/css/m4/m.all_v20190307183824.css	0.0 ms	4.0 KiB
c.58cdn.com.cn/m58/m3/css/m5.city_v20180716182440.css	0.0 ms	3.4 KiB
j1.58cdn.com.cn/m58/m3/js/m3.city.search.js?v=20180716	0.0 ms	2.1 KiB
j1.58cdn.com.cn/wuxianfe/m_homepage/nobuild/city_m3.ui_v20250710163140.js	432000.0 s	13.9 KiB
j1.58cdn.com.cn/m58/m3/js/m.lazyload_v20160812110246.js	300.0 s	1.3 KiB
/ga/url/?path=/location//locate//eq/fail/denied/&referer=...	0.0 ms	560 B
img.58cdn.com.cn/m58/m4/index/index_ico5.png	1728000.0 s	5.5 KiB
m.58.com/ga/url/?path=/location/city/click/&referer=&callback=jsonp_callback2	0.0 ms	545 B
img.58cdn.com.cn/m58/m3/img/u_del.png	1728000.0 s	4.1 KiB
img.58cdn.com.cn/logo/m58/46_44/logo.png	1728000.0 s	2.4 KiB
img.58cdn.com.cn/m58/m4/index/index_post.png	1728000.0 s	508 B

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.

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
j1.58cdn.com.cn/wuxianfe/m_homepage/nobuild/city_m3.ui_v20250710163140.js	13.9 KiB
c.58cdn.com.cn/m58/m3/css/m4/m.all_v20190307183824.css	4.0 KiB
j1.58cdn.com.cn/m58/m3/js/m.lazyload_v20160812110246.js	1.3 KiB
j1.58cdn.com.cn/m58/m3/js/jq.mobi.min_v20190517180203.js	6.4 KiB
c.58cdn.com.cn/m58/m3/css/m5.city_v20180716182440.css	3.4 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: 7.4 s

URL	Time Spent
58.com/	1.8 s
m.58.com/w/	1.8 s
m.58.com/bj/	3.5 s
m.58.com/city.html?from=iperror	330 ms
m.58.com/city.html?from=iperror	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: 589 ms

URL	Time Spent
m.58.com/city.html?from=iperror	689 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

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

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: 0.0 ms 5.1 KiB

URL	Transfer Size	Est Savings
j1.58cdn.com.cn/wuxianfe/m_homepage/nobuild/city_m3.ui_v20250710163140.js	13.7 KiB	5.1 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 300 ms 33.9 KiB

URL	Transfer Size	Est Savings
j1.58cdn.com.cn/beidou-sdk/browser/bundle.min.js	70.6 KiB	33.9 KiB

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
Style & Layout	1.6 s
Script Evaluation	829 ms
Other	562 ms
Rendering	210 ms
Script Parsing & Compilation	83 ms
Parse HTML & CSS	61 ms

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.body_div > div.header > a.logo_a > img`	img.58cdn.com.cn/logo/m58/46_44/logo.png
body > img `body > img`	/ga/?utmac=MO-35618414-1&utmn=493076949&utmr=http...
body > img `body > img`	/ga/?utmac=MO-35618414-1&utmn=1541527709&utmr=htt...

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

●Network dependency tree

●Optimize viewport for mobile

●Minify CSS

●Reduce unused CSS

●Avoids enormous network payloads Total size was 324 KiB

●JavaScript execution time 0.8 s

●Avoid long main-thread tasks 9 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 340 ms

●Server Backend Latencies 10 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid large layout shifts 1 layout shift found

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

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.header > div.login > span > a.publish`
A(以A为开头的城市名) `div.body_div > div.city_box > h4 > p`
B(以B为开头的城市名) `div.body_div > div.city_box > h4 > p`
C(以C为开头的城市名) `div.body_div > div.city_box > h4 > p`
D(以D为开头的城市名) `div.body_div > div.city_box > h4 > p`
E(以E为开头的城市名) `div.body_div > div.city_box > h4 > p`
F(以F为开头的城市名) `div.body_div > div.city_box > h4 > p`
G(以G为开头的城市名) `div.body_div > div.city_box > h4 > p`
H(以H为开头的城市名) `div.body_div > div.city_box > h4 > p`
J(以J为开头的城市名) `div.body_div > div.city_box > h4 > p`
K(以K为开头的城市名) `div.body_div > div.city_box > h4 > p`
L(以L为开头的城市名) `div.body_div > div.city_box > h4 > p`
M(以M为开头的城市名) `div.body_div > div.city_box > h4 > p`
N(以N为开头的城市名) `div.body_div > div.city_box > h4 > p`
P(以P为开头的城市名) `div.body_div > div.city_box > h4 > p`
Q(以Q为开头的城市名) `div.body_div > div.city_box > h4 > p`
R(以R为开头的城市名) `div.body_div > div.city_box > h4 > p`
S(以S为开头的城市名) `div.body_div > div.city_box > h4 > p`
T(以T为开头的城市名) `div.body_div > div.city_box > h4 > p`
W(以W为开头的城市名) `div.body_div > div.city_box > h4 > p`
X(以X为开头的城市名) `div.body_div > div.city_box > h4 > p`
Y(以Y为开头的城市名) `div.body_div > div.city_box > h4 > p`
Z(以Z为开头的城市名) `div.body_div > div.city_box > h4 > p`
普通版 `div.body_div > div.newFooter > p.footer_nav > a`
电脑版 `div.body_div > div.newFooter > p.footer_nav > a`
客户端 `div.body_div > div.newFooter > p.footer_nav > a#gotodownload`
手机58网：58.com 京公网备案信息11010502000809 京ICP证060405号 \| 京ICP备10012705号-2 `body > div.body_div > div.newFooter > p.footer_bot`
060405 `div.body_div > div.newFooter > p.footer_bot > a`
10012705 `div.body_div > div.newFooter > p.footer_bot > a`

These are opportunities to improve the legibility of your content.

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 > img `body > img`
body > img `body > img`

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.

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`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.city_page `html.city_page`

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

●Links are distinguishable without relying on color.

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

●Heading elements appear in a sequentially-descending order

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

○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

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

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

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

○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
m.58.com/city.html?from=iperror	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
j1.58cdn.com.cn/wuxianfe/m_homepage/pkg/index/index_common_homepage.js?v=247.js
j1.58cdn.com.cn/wuxianfe/m_homepage/nobuild/city_m3.ui_v20250710163140.js line 469, col 38

●Avoids deprecated APIs

●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 browser errors logged to the console

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

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
5	`Disallow: link.58.com`	`Pattern should either be empty, start with "/" or "*"`
6	`Disallow: link.58.com/*`	`Pattern should either be empty, start with "/" or "*"`
15	`Disallow: cheapi.58.com*`	`Pattern should either be empty, start with "/" or "*"`
16	`Disallow: cheapi.58.com/*`	`Pattern should either be empty, start with "/" or "*"`

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

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.

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 > img `body > img`
body > img `body > 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

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`