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.

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
网址 `div#scroller > ul.slide > li.cont-item-nav > a.item-0`	so1.360tres.com/t019d90cf0b338386ce.png	16.4 KiB	14.1 KiB
问答 `div#scroller > ul.slide > li.cont-item-nav > a.item-7`	so1.360tres.com/t01f923269991d92e8e.png	14.8 KiB	12.4 KiB
良医 `div#scroller > ul.slide > li.cont-item-nav > a.item-1`	so1.360tres.com/t01eb92ea006e6768c8.png	13.7 KiB	11.4 KiB
翻译 `div#scroller > ul.slide > li.cont-item-nav > a.item-8`	so1.360tres.com/t01c0f01d9ccda41893.png	12.9 KiB	10.5 KiB
地图 `div#scroller > ul.slide > li.cont-item-nav > a.item-6`	so1.360tres.com/t01fa7f2a8592fcbb5a.png	11.5 KiB	9.1 KiB
视频 `div#scroller > ul.slide > li.cont-item-nav > a.item-3`	so1.360tres.com/t014c9f32cdc38225d6.png	10.7 KiB	8.3 KiB
图片 `div#scroller > ul.slide > li.cont-item-nav > a.item-4`	so1.360tres.com/t012e4d67e0a7d2db6e.png	10.6 KiB	8.3 KiB
百科 `div#scroller > ul.slide > li.cont-item-nav > a.item-5`	so1.360tres.com/t0119ae4dccbc403f76.png	10.0 KiB	7.7 KiB
资讯 `div#scroller > ul.slide > li.cont-item-nav > a.item-2`	so1.360tres.com/t01e448f2b4e421b799.png	9.7 KiB	7.3 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:5755.7490009765625 label:Time to first byte subpart:timeToFirstByte] map[duration:1933.8019990234375 label:Resource load delay subpart:resourceLoadDelay] map[duration:670.183 label:Resource load duration subpart:resourceLoadDuration] map[duration:13.327 label:Element render delay subpart:elementRenderDelay]]

lhId: page-9-H1

nodeLabel: 360搜索

path: 1,HTML,1,BODY,2,DIV,0,DIV,0,DIV,0,HEADER,0,DIV,2,H1

selector: div.home > header#hd > div.in > h1.i-logo

snippet: <h1 data-v-289aa4f3="" class="i-logo">

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-9-H1

nodeLabel: 360搜索

path: 1,HTML,1,BODY,2,DIV,0,DIV,0,DIV,0,HEADER,0,DIV,2,H1

selector: div.home > header#hd > div.in > h1.i-logo

snippet: <h1 data-v-289aa4f3="" class="i-logo">

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

value: No additional origins are good candidates for preconnecting

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
/cloud_config?keys=footer.html&from=m.so.com&callback=_js...	0.0 ms	719 B
/api/weather_info.php?type=area,air,realtime&app=searchAp...	3600.0 s	568 B
/mso/disp.gif?pro=m_so&pid=home_next&u=https%3A%2F%2Fm.so...	0.0 ms	190 B
/mso/srp.gif?pro=m_so&pid=home_next&u=https%3A%2F%2Fm.so....	0.0 ms	189 B

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
so.com/	1.4 s
www.so.com/?src=so.com	1.4 s
m.so.com/?src=so.com	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.0 s

URL	Time Spent
m.so.com/?src=so.com	1.1 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

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: 910 ms 187.9 KiB

URL	Transfer Size	Est Savings
m.so.com/?src=so.com	298.8 KiB	128.9 KiB
m.so.com/?src=so.com	59.8 KiB	35.7 KiB
m.so.com/?src=so.com	30.6 KiB	23.3 KiB

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
Pages with cache-control:no-store header cannot enter back/forward cache.	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 50.5 KiB

URL	Transfer Size	Est Savings
.slide-left-enter-active[data-v-287aee8c]{-webkit-transition:all .3s ease;transition:all .3s ease} …	59.2 KiB	50.5 KiB

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

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Max Potential First Input Delay 50 ms

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 622 KiB

●JavaScript execution time 0.4 s

●Minimizes main-thread work 0.9 s

●Avoid long main-thread tasks 1 long task found

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

●Network Requests

●Network Round Trip Times 240 ms

●Server Backend Latencies 790 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid large layout shifts 1 layout shift 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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
12℃ 良73 北京 `header#hd > div.in > div > div#weather`
今日热搜加满一箱油将少花22 5国可用微信支付成品油价或年内首降日地震冲击半导体链福州拉响防空警报英雄接英雄行政被要求掌勺全员健身… `div#page > div > div.home > div#bd`

These are opportunities to improve the usage of ARIA in your application which 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
12℃ `div > div#weather > span.info > a`
73 `div#weather > span.pm25 > a > b.pm25-num`
北京 `div > div#weather > a.poi > span.city`
搜索 `div.in > div#search-box > form > button.search-btn`
今日热搜 `div#bd > div > section.hotnews-wrap > div.hn-title`

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.skin-default > img `body.skin-default > img`

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
header#hd > div.in > div > a.i-user `header#hd > div.in > div > a.i-user`

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#home_next `html#home_next`

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-*]` attributes match their roles

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

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

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

●Buttons have an accessible name

●Form elements have associated labels

●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

●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

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○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

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

○Identical links have the same purpose.

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

100

Best Practices

●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

●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

●Detected JavaScript libraries

●Page has valid source maps

○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 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.in > div > div#weather > a.poi`
360搜索 `header#hd > div.in > h1.i-logo > a`

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.skin-default > img `body.skin-default > img`

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`