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

items: [map[reflowTime:48.138 source:map[column:72319 line:2 type:source-location url:https://s1.hdslb.com/bfs/seed/log/report/log-reporter.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:99.738 source:map[type:text value:[unattributed]]] map[reflowTime:1.564 source:map[column:69824 line:1 type:source-location url:https://s1.hdslb.com/bfs/seed/log/report/log-reporter.js urlProvider:network]] map[reflowTime:46.574 source:map[column:69570 line:1 type:source-location url:https://s1.hdslb.com/bfs/seed/log/report/log-reporter.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-IMG

nodeLabel: 终于来了！大疆Pocket 4上手

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

selector: div.bfs-img-wrap > div.bfs-img > picture.b-img__inner > img

snippet: <img src="//i1.hdslb.com/bfs/archive/18363340c0b4de9cfcd415a0f94b1abbc693c2e8.jpg@38…" alt="终于来了！大疆Pocket 4上手" loading="lazy" onload="bmgCmptOnload(this)" onerror="bmgCmptOnerror(this)">

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

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
s1.hdslb.com/bfs/seed/jinkela/short/minntaki-wasm-sdk/bili-sc-sdk.umd.js	600.0 s	151.7 KiB
s1.hdslb.com/bfs/seed/log/report/log-reporter.js	600.0 s	41.8 KiB
s1.hdslb.com/bfs/seed/log/report/14.d6cf9.function.chunk.js	600.0 s	33.6 KiB
s1.hdslb.com/bfs/seed/jinkela/short/b-mirror/biliMirror.umd.mini.js	600.0 s	32.7 KiB
s1.hdslb.com/bfs/seed/jinkela/short/reporter-pb/index.js	600.0 s	30.6 KiB
s1.hdslb.com/bfs/seed/jinkela/kv-sdk/index.js	600.0 s	5.9 KiB
s1.hdslb.com/bfs/seed/log/report/512.4a4c4.function.chunk.js	600.0 s	2.5 KiB
s1.hdslb.com/bfs/seed/log/report/86.e192d.function.chunk.js	600.0 s	2.1 KiB
s1.hdslb.com/bfs/seed/log/report/950.3cf17.function.chunk.js	600.0 s	1.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: 2.5 s

URL	Time Spent
bilibili.com/	1.5 s
www.bilibili.com/	1.0 s
m.bilibili.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

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: 1.1 s 200.1 KiB

URL	Transfer Size	Est Savings
/bfs/static/jinkela/mstation-h5-new/2.mstation.986ddeb408...	313.2 KiB	119.4 KiB
/bfs/static/jinkela/mstation-h5-new/6.mstation.986ddeb408...	80.6 KiB	31.5 KiB
/bfs/static/jinkela/mstation-h5-new/14.mstation.986ddeb40...	67.3 KiB	27.5 KiB
/bfs/static/jinkela/mstation-h5-new/0.mstation.986ddeb408...	68.1 KiB	21.7 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: 450 ms 69.4 KiB

URL	Transfer Size	Est Savings
/bfs/static/jinkela/mstation-h5-new/css/mstation.2.986dde...	39.6 KiB	35.6 KiB
/bfs/static/jinkela/mstation-h5-new/css/mstation.6.986dde...	19.7 KiB	18.4 KiB
/bfs/static/jinkela/mstation-h5-new/css/mstation.14.986dd...	17.1 KiB	15.4 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: 1.2 s 277.3 KiB

URL	Transfer Size	Est Savings
/bfs/static/jinkela/mstation-h5-new/2.mstation.986ddeb408...	310.8 KiB	138.3 KiB
/bfs/static/jinkela/mstation-h5-new/14.mstation.986ddeb40...	67.0 KiB	51.9 KiB
/bfs/static/jinkela/mstation-h5-new/6.mstation.986ddeb408...	79.8 KiB	36.3 KiB
/bfs/static/jinkela/mstation-h5-new/0.mstation.986ddeb408...	63.0 KiB	29.4 KiB
s1.hdslb.com/bfs/seed/jinkela/short/b-mirror/biliMirror.umd.mini.js	31.3 KiB	21.4 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
/bfs/static/jinkela/mstation-h5-new/0.mstation.986ddeb408...	1.3 s	1.0 s	42 ms
s1.hdslb.com/bfs/seed/jinkela/short/minntaki-wasm-sdk/bili-sc-sdk.umd.js	751 ms	555 ms	45 ms
Unattributable	715 ms	198 ms	0.0 ms
m.bilibili.com/	657 ms	40 ms	30 ms
s1.hdslb.com/bfs/seed/log/report/log-reporter.js	535 ms	274 ms	16 ms
/bfs/static/jinkela/mstation-h5-new/2.mstation.986ddeb408...	247 ms	23 ms	200 ms
s1.hdslb.com/bfs/seed/jinkela/short/reporter-pb/index.js	142 ms	120 ms	18 ms
s1.hdslb.com/bfs/seed/log/report/14.d6cf9.function.chunk.js	108 ms	88 ms	18 ms
/bfs/static/jinkela/mstation-h5-new/6.mstation.986ddeb408...	94 ms	2.6 ms	87 ms
s1.hdslb.com/bfs/seed/jinkela/short/b-mirror/biliMirror.umd.mini.js	78 ms	53 ms	13 ms
/bfs/static/jinkela/mstation-h5-new/14.mstation.986ddeb40...	67 ms	2.1 ms	64 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	3.1 s
Style & Layout	758 ms
Other	701 ms
Script Parsing & Compilation	540 ms
Parse HTML & CSS	202 ms
Garbage Collection	63 ms
Rendering	44 ms

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
/bfs/static/jinkela/mstation-h5-new/2.mstation.986ddeb408...	314.2 KiB
/bfs/static/jinkela/mstation-h5-new/4.mstation.986ddeb408...	286.4 KiB
/bfs/static/jinkela/mstation-h5-new/11.mstation.986ddeb40...	249.0 KiB
/bfs/static/jinkela/mstation-h5-new/13.mstation.986ddeb40...	242.2 KiB
/bfs/static/jinkela/mstation-h5-new/9.mstation.986ddeb408...	205.4 KiB
/bfs/static/jinkela/mstation-h5-new/3.mstation.986ddeb408...	162.0 KiB
s1.hdslb.com/bfs/seed/jinkela/short/minntaki-wasm-sdk/bili-sc-sdk.umd.js	151.7 KiB
/bfs/static/jinkela/mstation-h5-new/5.mstation.986ddeb408...	88.0 KiB
/bfs/static/jinkela/mstation-h5-new/6.mstation.986ddeb408...	81.5 KiB
/bfs/static/jinkela/mstation-h5-new/7.mstation.986ddeb408...	80.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

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Avoid long main-thread tasks 15 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 240 ms

●Server Backend Latencies 310 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

○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
Download App `div.m-navbar > div.right > m-open-app.m-open-app > div.open-app-img`
Open in App `m-open-app.m-open-app > button.v5-button > div.v5-button__content__wrap > span`

These are opportunities to improve the legibility of your content.

Names and labels

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
div.suspension-box > div.m-navbar > div.right > a.search `div.suspension-box > div.m-navbar > div.right > a.search`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
首页番剧国创纪录片电影电视剧影视娱乐音乐舞蹈动画绘画鬼畜游戏资讯知识人工智能科技数码汽车时尚美妆家装房产户外潮流健… `div > div.v-switcher__header > div.v-switcher__header__tabs__wrap > ul.v-switcher__header__tabs__list`

These are opportunities to improve the experience of reading tabular or list data using 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-*]` 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

●Image elements have `[alt]` attributes

●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

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

○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

○`<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
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	/bfs/static/jinkela/mstation-h5-new/2.mstation.986ddeb408... line 21980, col 44

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

100

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.

○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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid