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.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
ms.bdstatic.com/se/wiseindex/head/wise/static/nicons/n-icons-00ee3b10.woff	665 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
div#userinfo-wrap > div.result-molecule > div.square-bubble-entrance > img.square-bubble-dynamic `div#userinfo-wrap > div.result-molecule > div.square-bubble-entrance > img.square-bubble-dynamic`	search-operate.cdn.bcebos.com/6c727ddb2cd9103e2b271f0e4c33bbeb.gif	72.2 KiB	47.7 KiB
head_icon `div.aside-header-and-padding-bottom > div.asideheader > div.user-info > img.head-icon`	/se/static/indexatom/personalcenter/assets/img/default_ic...	23.8 KiB	22.0 KiB
百度一下,你就知道 `div.result-molecule > div#logo > a.index_logo-wrap__J7H-U > img#wiseindex-bdlogo`	psstatic.cdn.bcebos.com/basics/2025_wiseindex/wiseindex-logo_1756889417000.png	24.6 KiB	19.5 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:2329.725 label:Time to first byte subpart:timeToFirstByte] map[duration:62.665 label:Resource load delay subpart:resourceLoadDelay] map[duration:2697.526 label:Resource load duration subpart:resourceLoadDuration] map[duration:8.981 label:Element render delay subpart:elementRenderDelay]]

lhId: page-2-IMG

nodeLabel: 百度一下,你就知道

path: 2,HTML,1,BODY,3,DIV,0,DIV,3,DIV,2,DIV,0,DIV,0,A,0,IMG

selector: div.result-molecule > div#logo > a.index_logo-wrap__J7H-U > img#wiseindex-bdlogo

snippet: <img id="wiseindex-bdlogo" src="https://psstatic.cdn.bcebos.com/basics/2025_wiseindex/wiseindex-logo_17568…" class="index_logo-img__3cFQS" data-doodle="" alt="百度一下,你就知道">

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-2-IMG

nodeLabel: 百度一下,你就知道

path: 2,HTML,1,BODY,3,DIV,0,DIV,3,DIV,2,DIV,0,DIV,0,A,0,IMG

selector: div.result-molecule > div#logo > a.index_logo-wrap__J7H-U > img#wiseindex-bdlogo

snippet: <img id="wiseindex-bdlogo" src="https://psstatic.cdn.bcebos.com/basics/2025_wiseindex/wiseindex-logo_17568…" class="index_logo-img__3cFQS" data-doodle="" 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

value: No additional origins are good candidates for preconnecting

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
psstatic.cdn.bcebos.com/basics/2025_wiseglobal/esl_1758513732000.ts	21.9 KiB	1.7 s
ms.bdstatic.com/se/wiseindex/head/wise/static/js/base/index-a398d05c.js	13.4 KiB	351 ms
ms.bdstatic.com/se/wiseindex/base-script/wise/static/index-fda1a248.js	1.9 KiB
ms.bdstatic.com/se/wiseindex/head/wise/static/css/index-cb86-77ac99e2.css	6.7 KiB	1.4 s

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
search-operate.cdn.bcebos.com/6c727ddb2cd9103e2b271f0e4c33bbeb.gif	52766.0 s	72.9 KiB
s.bdstatic.com/common/openjs/openBox.js?_v=2026-04-16-17	3600.0 s	12.3 KiB
s.bdstatic.com/common/openjs/openBox.js?_v=2026416	3600.0 s	12.3 KiB
sv.bdstatic.com/static/fecommon/growth/release/core.js?_sv=2026041617	1209600.0 s	24.6 KiB
/tc?tcreq4log=1&r=1776358838429&logid=1288747300822659446...	0.0 ms	430 B
/tc?tcreq4log=1&r=1776358841054&logid=1288747300822659446...	0.0 ms	336 B
/tc?tcreq4log=1&r=1776358841058&logid=1288747300822659446...	0.0 ms	336 B
/it/u=1538419461,3591049189&fm=3028&app=3028&f=PNG&fmt=au...	1179808.0 s	954 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: 1.4 s

URL	Time Spent
baidu.com/	1.4 s
www.baidu.com/	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

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

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

URL	Transfer Size	Est Savings
sv.bdstatic.com/static/fecommon/growth/release/core.js?_sv=2026041617	24.2 KiB	11.6 KiB

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

URL	Transfer Size	Est Savings
.tab_news{text-align:left;background:#fff} …	14.2 KiB	14.1 KiB
ms.bdstatic.com/se/wiseindex/search-box/wise/static/global-cb86-3792fc16.css	13.8 KiB	11.7 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: 0.0 ms 110.1 KiB

URL	Transfer Size	Est Savings
ms.bdstatic.com/se/wiseindex/amd_modules/@baidu/mcp-search/dist/index_4071ee4.js	51.2 KiB	39.1 KiB
/se/wiseindex/amd_modules/@baidu/wise-invoke-app/dist/amd...	42.8 KiB	27.9 KiB
ms.bdstatic.com/se/wiseindex/bottom-script/wise/static/lib/index-1447e5c2.js	36.1 KiB	21.8 KiB
ms.bdstatic.com/se/wiseindex/bottom-script/wise/static/start/index-d11791ce.js	31.0 KiB	21.3 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.result-molecule > div#logo > a.index_logo-wrap__J7H-U > img#wiseindex-bdlogo`	psstatic.cdn.bcebos.com/basics/2025_wiseindex/wiseindex-logo_1756889417000.png

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

●Max Potential First Input Delay 70 ms

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Avoids enormous network payloads Total size was 790 KiB

●JavaScript execution time 0.5 s

●Minimizes main-thread work 1.6 s

●Avoid long main-thread tasks 2 long tasks found

●Network Requests

●Network Round Trip Times 230 ms

●Server Backend Latencies 410 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

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

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
百度一下 `form#index-form > div > div.con-wrap > button#index-bn`
使用百度前必读 Baidu 京ICP证030173号 `div.result-molecule > div#bottom > div#foot > a#index-copyright`
京公网安备11000002000001号 `div.result-molecule > div#bottom > div#foot > a.recordcode`

These are opportunities to improve the legibility of your content.

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.

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#userinfo-wrap > div.result-molecule > div.square-bubble-entrance > img.square-bubble-dynamic `div#userinfo-wrap > div.result-molecule > div.square-bubble-entrance > img.square-bubble-dynamic`

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`

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

●Input buttons have discernible text.

●Form elements have associated labels

●Document has a `<title>` element

●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

●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

●Identical links have the same purpose.

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

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

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

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

○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
?action=sendIntent&minver=7.4&params=%7B%22intent%22%3A%2...	Allowed
/?data=fCMxIzsjMi8xLzUjLSMyIzsjSlR5cW4yN2M5b2Y3cTIye3s1c3...	Allowed with warning

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.	hm.baidu.com/hm.js?12423ecbc0e2ca965d84259063d35238 line 1, col 274

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
/?data=fCMxIzsjMi8xLzUjLSMyIzsjSlR5cW4yN2M5b2Y3cTIye3s1c3...	`Failed to load resource: net::ERR_CONNECTION_REFUSED`
ext.baidu.com/rest/id-mapping/cuid?callback=_box_jsonp848	`Failed to load resource: the server responded with a status of 403 (Forbidden)`
ext.baidu.com/rest/id-mapping/cuid?callback=_box_jsonp852	`Failed to load resource: the server responded with a status of 403 (Forbidden)`
ext.baidu.com/rest/id-mapping/cuid?callback=_box_jsonp843	`Failed to load resource: the server responded with a status of 403 (Forbidden)`

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Mixed content

●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

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

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#userinfo-wrap > div.result-molecule > div.square-bubble-entrance > img.square-bubble-dynamic `div#userinfo-wrap > div.result-molecule > div.square-bubble-entrance > img.square-bubble-dynamic`

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

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`