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.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:29.751 source:map[column:19013 line:1 type:source-location url:https://unpkg.zhimg.com/@cfe/sentry-script@1.3.1/dist/init.js urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:0.771 source:map[type:text value:[unattributed]]] map[reflowTime:0.225 source:map[column:455 line:16 type:source-location url:https://hm.baidu.com/hm.js?98beee57fd2ef70ccdd5ca52b9740c49 urlProvider:network]] map[reflowTime:0.612 source:map[column:50772 line:0 type:source-location url:https://static.zhihu.com/heifetz/chunks/zswsdid.993bf3e63383befd3ad6.js urlProvider:network]] map[reflowTime:5.211 source:map[column:65332 line:0 type:source-location url:https://static.zhihu.com/heifetz/chunks/zswsdid.993bf3e63383befd3ad6.js urlProvider:network]] map[reflowTime:24.54 source:map[column:65081 line:0 type:source-location url:https://static.zhihu.com/heifetz/chunks/zswsdid.993bf3e63383befd3ad6.js urlProvider:network]] map[reflowTime:0.56 source:map[column:26868 line:0 type:source-location url:https://static.zhihu.com/heifetz/chunks/zswsdid.993bf3e63383befd3ad6.js urlProvider:network]] map[reflowTime:0.116 source:map[column:32161 line:0 type:source-location url:https://static.zhihu.com/heifetz/chunks/zswsdid.993bf3e63383befd3ad6.js urlProvider:network]]]

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
static.zhihu.com/heifetz/main-signin-routes.216a26f4.b5c40ac2c6385d5afdce.css	3.7 KiB
static.zhihu.com/heifetz/main.216a26f4.c474a29726a94e27199a.css	26.6 KiB
static.zhihu.com/heifetz/8395.216a26f4.2afeae5366d99d24482a.css	27.9 KiB	301 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
cstaticdun.126.net/2.28.5/core-optimi.m25b40.v2.28.5.min.js?v=2960605	43200.0 s	179.6 KiB
cstaticdun.126.net/ir.2.0.13.min.js?v=29606057	43200.0 s	40.8 KiB
cstaticdun.126.net/load.min.js	43200.0 s	15.0 KiB
/api/v1/captcha/js?appId=captcha_register_login&captchaId...	0.0 ms	1.0 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.SignFlowHomepage > footer.SignFlowHomepage-footer > div.css-1xaekgw > img.css-1170n61`	pica.zhimg.com/80/v2-ccdb7828c12afff31a27e51593d23260_720w.png	8.2 KiB	7.7 KiB
知乎 LOGO `div > div.SignFlowHomepage > div.SignFlowHomepage-content > img.SignFlowHomepage-logo`	pic2.zhimg.com/80/v2-f6b1f64a098b891b4ea1e3104b5b71f6_720w.png	8.6 KiB	6.9 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: 1.6 s

URL	Time Spent
zhihu.com/	1.1 s
www.zhihu.com/	481 ms
www.zhihu.com/signin?next=%2F	0.0 ms

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.

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

URL	Transfer Size	Est Savings
static.zhihu.com/heifetz/8395.216a26f4.2afeae5366d99d24482a.css	27.5 KiB	26.7 KiB
.yidun.yidun--light.yidun--avoid.yidun--button .yidun_tip...	23.9 KiB	23.9 KiB
static.zhihu.com/heifetz/main.216a26f4.c474a29726a94e27199a.css	26.4 KiB	23.7 KiB

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.

URL	Total CPU Time	Script Evaluation	Script Parse
static.zhihu.com/amadeus-rn/web/shared-ef98b214814c8805.ca7a7ac003b24756.js	610 ms	588 ms	18 ms
static.zhihu.com/heifetz/main.app.3fbde678b8f61cebb7af.js	306 ms	265 ms	32 ms
www.zhihu.com/signin?next=%2F	289 ms	27 ms	0.8 ms
Unattributable	275 ms	74 ms	0.0 ms
unpkg.zhimg.com/@cfe/sentry-script@1.3.1/dist/init.js	186 ms	133 ms	1.2 ms
unpkg.zhimg.com/za-js-sdk@5.6.0/dist/zap.js	135 ms	123 ms	9.3 ms
cstaticdun.126.net/load.min.js	134 ms	132 ms	0.9 ms
static.zhihu.com/event/wza/4633_1/aria.js?appid=a3637ace5dc3a347f6863b0bac487599	129 ms	114 ms	10 ms
static.zhihu.com/heifetz/8395.app.67e4175617880cd253f4.js	108 ms	36 ms	62 ms
static.zhihu.com/event/react@17.0.2/umd/react.production.min.js	58 ms	53 ms	0.4 ms
cstaticdun.126.net/2.28.5/core-optimi.m25b40.v2.28.5.min.js?v=2960605	56 ms	41 ms	12 ms

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
Script Evaluation	1.8 s
Other	258 ms
Script Parsing & Compilation	257 ms
Style & Layout	228 ms
Garbage Collection	44 ms
Parse HTML & CSS	21 ms
Rendering	19 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
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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 1.4 MiB

URL	Transfer Size	Est Savings
static.zhihu.com/heifetz/8395.app.67e4175617880cd253f4.js	783.2 KiB	572.9 KiB
static.zhihu.com/heifetz/main.app.3fbde678b8f61cebb7af.js	370.7 KiB	259.7 KiB
static.zhihu.com/amadeus-rn/web/shared-1637117f027caece.06ea943e1ff2da6f.js	212.0 KiB	120.2 KiB
static.zhihu.com/event/wza/4633_1/aria.js?appid=a3637ace5dc3a347f6863b0bac487599	117.3 KiB	85.4 KiB
cstaticdun.126.net/2.28.5/core-optimi.m25b40.v2.28.5.min.js?v=2960605	178.5 KiB	78.0 KiB
static.zhihu.com/amadeus-rn/web/shared-ef98b214814c8805.ca7a7ac003b24756.js	302.4 KiB	75.0 KiB
static.zhihu.com/heifetz/vendor.007c46aa2a2931497960.js	67.2 KiB	32.5 KiB
static.zhihu.com/amadeus-rn/web/shared-4300cebafe39d3a8.f116bb4b1e6bf128.js	32.0 KiB	27.8 KiB
static.zhihu.com/amadeus-rn/web/shared-60696d0f627d269d.22e16f99938d401e.js	38.2 KiB	26.1 KiB
static.zhihu.com/amadeus-rn/web/shared-298c47547c387857.09656bfa740afbae.js	26.8 KiB	24.6 KiB
static.zhihu.com/amadeus-rn/web/shared-07e3b8d7f3535a74.cdca1797ddc5fc64.js	27.4 KiB	23.2 KiB
static.zhihu.com/amadeus-rn/web/lib-db784e6aa5c9c12d.7d9da96360fcf186.js	44.8 KiB	22.7 KiB
static.zhihu.com/amadeus-rn/web/shared-0e3d678a004c0d62.7fde73932b1707c9.js	52.9 KiB	22.3 KiB
static.zhihu.com/amadeus-rn/web/shared-212f2483116fd64c.5a90bf6e577935fc.js	28.0 KiB	22.0 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
static.zhihu.com/heifetz/8395.app.67e4175617880cd253f4.js	791.0 KiB
static.zhihu.com/heifetz/assets/sign_bg.47eec442.png	388.5 KiB
static.zhihu.com/heifetz/main.app.3fbde678b8f61cebb7af.js	374.6 KiB
static.zhihu.com/amadeus-rn/web/shared-ef98b214814c8805.ca7a7ac003b24756.js	305.2 KiB
static.zhihu.com/amadeus-rn/web/shared-1637117f027caece.06ea943e1ff2da6f.js	212.3 KiB
cstaticdun.126.net/2.28.5/core-optimi.m25b40.v2.28.5.min.js?v=2960605	179.6 KiB
static.zhihu.com/event/wza/4633_1/aria.js?appid=a3637ace5dc3a347f6863b0bac487599	118.0 KiB
unpkg.zhimg.com/za-js-sdk@5.6.0/dist/zap.js	73.7 KiB
static.zhihu.com/heifetz/vendor.007c46aa2a2931497960.js	67.4 KiB
static.zhihu.com/amadeus-rn/web/shared-0e3d678a004c0d62.7fde73932b1707c9.js	53.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
footer.SignFlowHomepage-footer > div.ZhihuRights > a > img `footer.SignFlowHomepage-footer > div.ZhihuRights > a > img`	pic3.zhimg.com/80/v2-d0289dc0a46fc5b15b3363ffa78cf6c7.png

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

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 2 user timings

●Avoid long main-thread tasks 8 long tasks found

●Network Requests

●Network Round Trip Times 310 ms

●Server Backend Latencies 280 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○LCP request discovery

○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

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
欢迎进入知乎 - 有问题，就会有答案,盲人用户使用操作智能引导，请按快捷键Ctrl+Alt+R；阅读详细操作说明请按快捷键Ctrl+Alt+问号键。 `body > a#ariaTipText`

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body `body`

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
中国 +86 `div.SignFlow-account > div.SignFlow-supportedCountriesSelectContainer > div.Popover > button#Popover2-toggle`
div > form.SignFlow > div.Login-options > button.Button `div > form.SignFlow > div.Login-options > button.Button`
div.css-10wc74s > div.Login-socialLogin > span.Login-socialButtonGroup > button.Button `div.css-10wc74s > div.Login-socialLogin > span.Login-socialButtonGroup > button.Button`
div.css-10wc74s > div.Login-socialLogin > span.Login-socialButtonGroup > button.Button `div.css-10wc74s > div.Login-socialLogin > span.Login-socialButtonGroup > button.Button`
div.css-10wc74s > div.Login-socialLogin > span.Login-socialButtonGroup > button.Button `div.css-10wc74s > div.Login-socialLogin > span.Login-socialButtonGroup > button.Button`

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 > a#ariaTipText > img `body > a#ariaTipText > 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.

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
中国 +86 `div.SignFlow-supportedCountriesSelectContainer > div.Popover > button#Popover2-toggle > span`
登录/注册 `div.SignContainer-inner > div > form.SignFlow > button.Button`
其他方式登录 `div.signQr-rightContainer > div.css-10wc74s > div.css-jr78vv > div.css-wna3id`
未注册手机验证后自动登录，注册即代表同意《知乎协议》《隐私保护指引》 `div.signQr-container > div.signQr-rightContainer > div.css-10wc74s > div.SignContainer-tip`
《知乎协议》 `div.signQr-rightContainer > div.css-10wc74s > div.SignContainer-tip > a`
《隐私保护指引》 `div.signQr-rightContainer > div.css-10wc74s > div.SignContainer-tip > a`

These are opportunities to improve the legibility of your content.

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

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

●`[role]`s have all required `[aria-*]` attributes

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

●Form elements have associated labels

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

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●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

●Links are distinguishable without relying on color.

●Links have a discernible name

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○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

○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

○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

○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

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

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

Best Practices

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.	unpkg.zhimg.com/@cfe/sentry-script@1.3.1/dist/init.js

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
www.zhihu.com/signin?next=%2F	`Access to XMLHttpRequest at 'https://118.89.204.198/resolv?host=www.zhihu.com&os_type=web' from origin 'https://www.zhihu.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
118.89.204.198/resolv?host=www.zhihu.com&os_type=web	`Failed to load resource: net::ERR_FAILED`

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 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 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 DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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
body > a#ariaTipText > img `body > a#ariaTipText > 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

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`