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.

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

items: [map[reflowTime:60.083 source:map[type:text value:[unattributed]]] map[reflowTime:20.852 source:map[column:145879 line:0 type:source-location url:https://fe-static.xhscdn.com/formula-static/ranchi/public/js/main.e3c26d7.js urlProvider:network]] map[reflowTime:0.613 source:map[column:124678 line:0 type:source-location url:https://fe-static.xhscdn.com/formula-static/ranchi/public/js/main.e3c26d7.js urlProvider:network]] map[reflowTime:0.396 source:map[column:147142 line:0 type:source-location url:https://fe-static.xhscdn.com/formula-static/ranchi/public/js/main.e3c26d7.js urlProvider:network]]]

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

nodeLabel: div.banner > div.carousel-item > div.reds-video-box > span.reds-video-poster

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

selector: div.banner > div.carousel-item > div.reds-video-box > span.reds-video-poster

snippet: <span class="reds-video-poster" style="background-image: url("//picasso-static.xiaohongshu.com/fe-platform/24ab2e64…");" data-v-e2cec80e="" data-v-79f27e04="">

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
fe-static.xhscdn.com/formula-static/ranchi/public/css/allStyle.e1b9da3.css	40.6 KiB	912 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
fe-static.xhscdn.com/as/v1/3e44/public/bf7d4e32677698655a5cadc581fd09b3.js	2278277.0 s	899 B

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
9-15岁文史救星✨超实用的文学常识书 `section#69e5d926000000002200cfb8 > span.reds-img-container > picture.reds-img-box > img.reds-img`	/41247dcf-40a2-e357-f544-6d18eb2241cd?imageView2/1/w/360/...	40.8 KiB	19.7 KiB
不催不吼，娃居然主动学历史了 `section#69e738d80000000023017c74 > span.reds-img-container > picture.reds-img-box > img.reds-img`	/6287100b-5269-5624-eda2-511211f18b2f?imageView2/1/w/360/...	47.7 KiB	19.5 KiB
发布会直击｜能睡、能装、能“放电”的纯电SUV来了 `section#69e5c7e40000000023020b04 > span.reds-img-container > picture.reds-img-box > img.reds-img`	/ae1acd8e-4082-7bb3-2d30-26556bbf791e?imageView2/1/w/360/...	47.3 KiB	19.2 KiB
电动牙刷现在都这么卷了吗？后悔没早买！ `section#69e6fa8d00000000210112a0 > span.reds-img-container > picture.reds-img-box > img.reds-img`	/2a82afe7-80b7-f9bb-9f85-6f069e5765bf?imageView2/1/w/360/...	45.0 KiB	16.9 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

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.

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.2 s

URL	Time Spent
xiaohongshu.com/	1.2 s
www.xiaohongshu.com/	0.0 ms

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: 170 ms 38.3 KiB

URL	Transfer Size	Est Savings
fe-static.xhscdn.com/formula-static/ranchi/public/css/allStyle.e1b9da3.css	40.0 KiB	38.3 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
fe-static.xhscdn.com/formula-static/ranchi/public/js/main.e3c26d7.js	22.1 s	16.0 s	24 ms
fe-static.xhscdn.com/as/v2/fp/643f48183a62c46e6c924b3f0456767a.js	3.6 s	3.2 s	34 ms
fe-static.xhscdn.com/formula-static/ranchi/public/js/616.3e0efab.chunk.js	1.5 s	1.4 s	2.3 ms
Unattributable	1.2 s	62 ms	0.0 ms
www.xiaohongshu.com/	697 ms	48 ms	7.4 ms
fe-static.xhscdn.com/formula-static/ranchi/public/js/vendor.8eb661d.js	514 ms	185 ms	286 ms
fe-static.xhscdn.com/as/v1/f218/a15/public/04b29480233f4def5c875875b6bdc3b1.js	396 ms	326 ms	37 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	21.3 s
Style & Layout	6.0 s
Other	1.8 s
Script Parsing & Compilation	437 ms
Garbage Collection	282 ms
Parse HTML & CSS	187 ms
Rendering	118 ms

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

URL	Transfer Size	Est Savings
fe-static.xhscdn.com/formula-static/ranchi/public/js/vendor.8eb661d.js	579.2 KiB	214.0 KiB
fe-static.xhscdn.com/formula-static/ranchi/public/js/main.e3c26d7.js	64.3 KiB	28.2 KiB
/fe-platform/abf6e0874371419fa6fffa7540610e2013588fe6/htm...	45.2 KiB	22.9 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

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●User Timing marks and measures 30 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 10 animated elements found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 160 ms

●Server Backend Latencies 230 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○Avoid large layout shifts

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
你的生活指南 `nav#navbar > a.home > div.slogan > p`
打开看看 `div.tools > button.reds-button > span.reds-button-box > span.reds-button-text`

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.bottom-btn > div.bottom-btn-logo > div.img-placeholder > img `div.bottom-btn > div.bottom-btn-logo > div.img-placeholder > 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 `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>`

●Buttons have an accessible name

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

●Document has a `<title>` element

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

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

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

○Form elements have associated labels

○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

○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

○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

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
invalid/	`Failed to load resource: net::ERR_FAILED`
invalid/	`Failed to load resource: net::ERR_FAILED`
invalid/	`Failed to load resource: net::ERR_FAILED`
invalid/	`Failed to load resource: net::ERR_FAILED`
invalid/	`Failed to load resource: net::ERR_FAILED`
invalid/	`Failed to load resource: net::ERR_FAILED`
invalid/	`Failed to load resource: net::ERR_FAILED`
invalid/	`Failed to load resource: net::ERR_FAILED`

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

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
小红书 App 你的生活指南 `div.launch-app-container > div.fixed > nav#navbar > a.home`

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
div.bottom-btn > div.bottom-btn-logo > div.img-placeholder > img `div.bottom-btn > div.bottom-btn-logo > div.img-placeholder > 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

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