Lighthouse Desktop

· 0 checks — Desktop 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
pss.bdstatic.com/r/www/static/font/cosmic/pc/cos-icon_f8a2aa1.woff2	515 ms
pss.bdstatic.com/static/superman/font/iconfont-fa013548a9.woff2	480 ms

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:2487.565 label:Time to first byte subpart:timeToFirstByte] map[duration:694.385 label:Resource load delay subpart:resourceLoadDelay] map[duration:501.428 label:Resource load duration subpart:resourceLoadDuration] map[duration:11.402 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-IMG

nodeLabel: div.s_form > div.s_form_wrapper > div#lg > img#s_lg_img

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

selector: div.s_form > div.s_form_wrapper > div#lg > img#s_lg_img

snippet: <img hidefocus="true" id="s_lg_img" class="index-logo-src" src="//www.baidu.com/img/PCtm_d9c8750bed0b3c7d089fa7d55720d6cf.png" width="270" height="129" onerror="this.src='//www.baidu.com/img/flexible/logo/pc/index.png';this.onerror=nul…" usemap="#mp">

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.s_form > div.s_form_wrapper > div#lg > img#s_lg_img

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

selector: div.s_form > div.s_form_wrapper > div#lg > img#s_lg_img

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
pss.bdstatic.com/r/www/static/font/cosmic/pc/cos-icon_20cec29.css	4.1 KiB	743 ms

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
hectorstatic.baidu.com/cd37ed75a9387c5b.js	3600.0 s	31.4 KiB
hectorstatic.baidu.com/96c9c06653ba892e.js	3600.0 s	27.1 KiB
/passApi/js/wrapper.js?cdnversion=1776358863982&_=1776358...	0.0 ms	7.2 KiB
/it/u=1627277417,3307578141&fm=3028&app=3028&f=PNG&fmt=au...	1611857.0 s	48.4 KiB

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.s_form > div.s_form_wrapper > div#lg > img#s_lg_img `div.s_form > div.s_form_wrapper > div#lg > img#s_lg_img`	www.baidu.com/img/PCtm_d9c8750bed0b3c7d089fa7d55720d6cf.png	15.1 KiB	11.3 KiB
div.panel-list_8jHmm > div.panel-sample_xVtAM > a.guide-bub-container_2skZT > img `div.panel-list_8jHmm > div.panel-sample_xVtAM > a.guide-bub-container_2skZT > img`	psstatic.cdn.bcebos.com/aife/static/wenxinlogo_1770695621000.png	6.9 KiB	6.7 KiB
div.s-hotsearch-title > a.hot-title > div.title-text > img.hot-title-icon `div.s-hotsearch-title > a.hot-title > div.title-text > img.hot-title-icon`	psstatic.cdn.bcebos.com/basics/aichat/hot_search_x3_1747880381000.png	6.2 KiB	6.0 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: 759 ms

URL	Time Spent
baidu.com/	759 ms
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

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

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
Other	3.2 s
Script Evaluation	1.3 s
Style & Layout	73 ms
Script Parsing & Compilation	71 ms
Parse HTML & CSS	30 ms
Garbage Collection	25 ms
Rendering	17 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

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

URL	Transfer Size	Est Savings
pss.bdstatic.com/static/superman/amd_modules/@baidu/video-meeting-1be7f62dac.js	50.0 KiB	18.2 KiB
/r/www/cache/static/protocol/https/home/js/nu_instant_sea...	14.4 KiB	6.3 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 33.1 KiB

URL	Transfer Size	Est Savings
:root{--fixed-top-offset:78px} …	22.5 KiB	21.6 KiB
.chat-input-background_3edHa { position: relative; } …	13.0 KiB	11.5 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 288.5 KiB

URL	Transfer Size	Est Savings
/r/www/cache/static/protocol/https/global/js/all_async_se...	232.9 KiB	179.3 KiB
pss.bdstatic.com/static/superman-san/app/chat-input/result_ad43ead.js	115.8 KiB	60.2 KiB
/r/www/cache/static/protocol/https/amd_modules/@baidu/gua...	39.2 KiB	24.9 KiB
pss.bdstatic.com/static/superman/amd_modules/@baidu/video-meeting-1be7f62dac.js	49.6 KiB	24.1 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.panel-list_8jHmm > div.panel-sample_xVtAM > a.guide-bub-container_2skZT > img `div.panel-list_8jHmm > div.panel-sample_xVtAM > a.guide-bub-container_2skZT > img`	psstatic.cdn.bcebos.com/aife/static/wenxinlogo_1770695621000.png

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

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Avoids enormous network payloads Total size was 1,726 KiB

●JavaScript execution time 1.2 s

●Avoid long main-thread tasks 20 long tasks found

●Network Requests

●Network Round Trip Times 320 ms

●Server Backend Latencies 220 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts 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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.chat-input-d-tooltip > div.tooltip-wrapper > div > div `div.chat-input-d-tooltip > div.tooltip-wrapper > div > div`

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
登录 `div#head > div.s_top_container > div#u1 > a#s-top-loginbtn`
换一换 `div#s-hotsearch-wrapper > div.s-hotsearch-title > a#hotsearch-refresh-btn > span.hot-refresh-text`
关于百度 `div#bottom_layer > div.s-bottom-layer-content > p.lh > a.text-color`
About Baidu `div#bottom_layer > div.s-bottom-layer-content > p.lh > a.text-color`
使用百度前必读 `div#bottom_layer > div.s-bottom-layer-content > p.lh > a.text-color`
帮助中心 `div#bottom_layer > div.s-bottom-layer-content > p.lh > a.text-color`
企业推广 `div#bottom_layer > div.s-bottom-layer-content > p.lh > a.text-color`
京公网安备11000002000001号 `div#bottom_layer > div.s-bottom-layer-content > p.lh > a.text-color`
京ICP证030173号 `div#bottom_layer > div.s-bottom-layer-content > p.lh > a.text-color`
互联网新闻信息服务许可证11220180008 `div#bottom_layer > div.s-bottom-layer-content > p.lh > span.text-color`
网络文化经营许可证：京网文〔2023〕1034-029号 `div#bottom_layer > div.s-bottom-layer-content > p.lh > span.text-color`
信息网络传播视听节目许可证 0110516 `div#bottom_layer > div.s-bottom-layer-content > p.lh > a.text-color`

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.s_form > div.s_form_wrapper > div#lg > img#s_lg_img `div.s_form > div.s_form_wrapper > div#lg > img#s_lg_img`
div.panel-list_8jHmm > div.panel-sample_xVtAM > a.guide-bub-container_2skZT > img `div.panel-list_8jHmm > div.panel-sample_xVtAM > a.guide-bub-container_2skZT > img`
div#s_top_feed > div.top-feed-body > div.to-top > img#up-top `div#s_top_feed > div.top-feed-body > div.to-top > img#up-top`
div#s_side_wrapper > div#s_qrcode_nologin > div.qrcode-layer > img.icon `div#s_side_wrapper > div#s_qrcode_nologin > div.qrcode-layer > img.icon`

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

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

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

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

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

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

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

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

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

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

○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

User Experience

Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more about user-friendly input fields.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.chat-input-wrapper > div.chat-input-container > div#chat-input-area > textarea#chat-textarea `div.chat-input-wrapper > div.chat-input-container > div#chat-input-area > textarea#chat-textarea`

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
SharedStorage	pss.bdstatic.com/r/www/cache/static/protocol/https/bundles/polyfill_9354efa.js line 17, col 548
Unload event listeners are deprecated and will be removed.	pss.bdstatic.com/static/superman/js/lib/jquery-1-edb203c114.10.2.js line 138, col 305
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	hectorstatic.baidu.com/96c9c06653ba892e.js
Fledge	hectorstatic.baidu.com/96c9c06653ba892e.js

●Uses HTTPS

●Avoids third-party cookies

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

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.s_form > div.s_form_wrapper > div#lg > img#s_lg_img `div.s_form > div.s_form_wrapper > div#lg > img#s_lg_img`
div.panel-list_8jHmm > div.panel-sample_xVtAM > a.guide-bub-container_2skZT > img `div.panel-list_8jHmm > div.panel-sample_xVtAM > a.guide-bub-container_2skZT > img`
div#s_top_feed > div.top-feed-body > div.to-top > img#up-top `div#s_top_feed > div.top-feed-body > div.to-top > img#up-top`
div#s_side_wrapper > div#s_qrcode_nologin > div.qrcode-layer > img.icon `div#s_side_wrapper > div#s_qrcode_nologin > div.qrcode-layer > img.icon`

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`