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.

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
hihonorcloud.com/static/fonts/element-icons.535877f5.woff	300 ms

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:60.111 source:map[column:59772 line:332 type:source-location url:https://hihonorcloud.com/static/js/chunk-vendors.2510211110.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:4.043 source:map[column:45776 line:331 type:source-location url:https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js urlProvider:network]] map[reflowTime:56.068 source:map[column:45637 line:331 type:source-location url:https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js urlProvider:network]]]

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:466.1089999694824 label:Time to first byte subpart:timeToFirstByte] map[duration:22371.597000030517 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-DIV

nodeLabel: div.el-message-box > div.el-message-box__content > div.el-message-box__container > div.el-message-box__status

path: 1,HTML,1,BODY,6,DIV,0,DIV,1,DIV,0,DIV,0,DIV

selector: div.el-message-box > div.el-message-box__content > div.el-message-box__container > div.el-message-box__status

snippet: <div class="el-message-box__status el-icon-warning">

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

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
hihonorcloud.com/static/css/portal.2510211110.css	860.7 KiB	4.2 s
hihonorcloud.com/static/css/chunk-vendors.2510211110.css	267.8 KiB	1.8 s
hihonorcloud.com/config.js	802 B

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.

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: 5.7 s 1.1 MiB

URL	Transfer Size	Est Savings
hihonorcloud.com/static/css/portal.2510211110.css	859.2 KiB	857.8 KiB
hihonorcloud.com/static/css/chunk-vendors.2510211110.css	267.1 KiB	263.9 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: 10.7 s 2.1 MiB

URL	Transfer Size	Est Savings
hihonorcloud.com/static/js/chunk-vendors.2510211110.js	1.9 MiB	1.4 MiB
hihonorcloud.com/static/js/portal.2510211110.js	1.6 MiB	751.2 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
hihonorcloud.com/static/js/portal.2510211110.js	1.7 s	1.2 s	227 ms
hihonorcloud.com/static/js/chunk-vendors.2510211110.js	782 ms	264 ms	210 ms
Unattributable	480 ms	1.8 ms	0.0 ms
hihonorcloud.com/	138 ms	0.5 ms	0.9 ms
hihonorcloud.com/static/css/portal.2510211110.css	72 ms	0.0 ms	0.0 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.5 s
Other	728 ms
Script Parsing & Compilation	439 ms
Style & Layout	349 ms
Garbage Collection	155 ms
Parse HTML & CSS	93 ms
Rendering	12 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
hihonorcloud.com/static/js/chunk-vendors.2510211110.js	1.9 MiB
hihonorcloud.com/static/js/portal.2510211110.js	1.9 MiB
hihonorcloud.com/static/css/portal.2510211110.css	860.7 KiB
hihonorcloud.com/static/css/chunk-vendors.2510211110.css	267.8 KiB
hihonorcloud.com/static/fonts/element-icons.535877f5.woff	28.0 KiB
hihonorcloud.com/	2.5 KiB
hihonorcloud.com/config.js	802 B
www.hihonor.com/etc/designs/honor-site/assets/favicon.ico	441 B

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Improve image delivery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoid long main-thread tasks 8 long tasks found

●Avoid non-composited animations 1 animated element found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 150 ms

●Server Backend Latencies 410 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○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
OK `div.el-message-box > div.el-message-box__btns > button.el-button > span`

These are opportunities to improve the legibility of your content.

Names and labels

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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.

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.

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

●`[role]` values are valid

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

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●Elements use only permitted ARIA attributes

●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

○`button`, `link`, and `menuitem` elements 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 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 a valid value for its `[lang]` attribute

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

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

○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

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
hihonorcloud.com/static/js/chunk-vendors.2510211110.js line 78, col 10076	`Error: timeout of 10000ms exceeded at e.exports (https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js:79:10077) at h.ontimeout (https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js:264:2222)`
hihonorcloud.com/static/js/chunk-vendors.2510211110.js line 78, col 10076	`Error: timeout of 10000ms exceeded at e.exports (https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js:79:10077) at h.ontimeout (https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js:264:2222)`
hihonorcloud.com/static/js/chunk-vendors.2510211110.js line 78, col 10076	`Error: timeout of 10000ms exceeded at e.exports (https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js:79:10077) at h.ontimeout (https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js:264:2222)`
hihonorcloud.com/static/js/chunk-vendors.2510211110.js line 78, col 10076	`Error: timeout of 10000ms exceeded at e.exports (https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js:79:10077) at h.ontimeout (https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js:264:2222)`
hihonorcloud.com/static/js/chunk-vendors.2510211110.js line 78, col 10076	`Error: timeout of 10000ms exceeded at e.exports (https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js:79:10077) at h.ontimeout (https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js:264:2222)`
hihonorcloud.com/static/js/chunk-vendors.2510211110.js line 78, col 10076	`Error: timeout of 10000ms exceeded at e.exports (https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js:79:10077) at h.ontimeout (https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js:264:2222)`
hihonorcloud.com/static/js/chunk-vendors.2510211110.js line 78, col 10076	`Error: timeout of 10000ms exceeded at e.exports (https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js:79:10077) at h.ontimeout (https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js:264:2222)`
hihonorcloud.com/static/js/chunk-vendors.2510211110.js line 78, col 10076	`Error: timeout of 10000ms exceeded at e.exports (https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js:79:10077) at h.ontimeout (https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js:264:2222)`
hihonorcloud.com/static/js/chunk-vendors.2510211110.js line 78, col 10076	`Error: timeout of 10000ms exceeded at e.exports (https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js:79:10077) at h.ontimeout (https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js:264:2222)`
hihonorcloud.com/static/js/chunk-vendors.2510211110.js line 78, col 10076	`Error: timeout of 10000ms exceeded at e.exports (https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js:79:10077) at h.ontimeout (https://hihonorcloud.com/static/js/chunk-vendors.2510211110.js:264:2222)`

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.

URL
hihonorcloud.com/static/js/portal.2510211110.js
hihonorcloud.com/static/js/chunk-vendors.2510211110.js

●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

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

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://hihonorcloud.com/robots.txt`

To appear in search results, crawlers need access to your app.

Content Best Practices

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

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

○Image elements have `[alt]` attributes