Skip to content
Audit Complete

Results for https://miui.com

Visit site
Spain Spain · Madrid Completed: Apr 16, 2026 17:17 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
D67

Site Health

Score: 67 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Several missing protections leave your users and data exposed.

Major barriers for users with disabilities — up to 15% of your audience.

Solid SEO basics — a few optimizations could boost rankings.

Good server performance with room for optimization.

Several regulatory requirements are not yet met.

Missing metadata means poor previews on social media and search.

Reasonable footprint with room for optimization.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

React sites average 73
-6 below average
Tailwind CSS sites average 75
-8 below average
Better than 1% of Tailwind CSS sites See full Tailwind CSS benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
4

1 image-in-link without alt text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Alt Text Quality
5

1 image-only link(s) without alt text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fmiui.com)](https://beavercheck.com/results/98613f3f-9324-45ad-b159-3b8d8de1c86e)
<a href="https://beavercheck.com/results/98613f3f-9324-45ad-b159-3b8d8de1c86e"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fmiui.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fmiui.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site has several issues that may be affecting user experience and business outcomes. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.
C
Could reach Estimate based on resolving critical issues

Conversion Barriers

2 critical 7 warning

9 barrier(s) likely increasing bounce by ~31%.

Speed (1)

Page takes 6.8s to load

+12% bounce

Users abandon at ~3s — you're 4.3s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (1)

Viewport disables user zoom

+2% bounce

Visitors with low vision can't read the page — and some jurisdictions treat this as a legal risk

Fix: Remove user-scalable=no; drop maximum-scale if it's below 2

Content (3)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (2)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

17 broken link(s) on the page

+5% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€383 investment → €4,172/month returns + EUR 20,500,000 risk avoided

Payback period: < 1 month First-year ROI: +12988%

Investment

€383

4h · 5 findings

Monthly returns

€4,172 /mo

~€50,061 / year

  • Conversions recovered €4,171
  • Bandwidth savings €0.41

Regulatory risk avoided

EUR 20,500,000

if kept compliant

  • GDPR EUR 20,000,000
  • EAA EUR 500,000

Payback period

0 12mo 24mo

€128 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

€383

4.5 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins
€128 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
/hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€1,708,334 / month at risk

~€20,500,005 / year if left unfixed

Compliance Risk

€20,500,000

GDPREAA
  • Privacy Policy not detected
    GDPR: EUR 10,000 – EUR 20,000,000
  • Skip navigation link is missing (WCAG 2.4.1)
    EAA: EUR 1,000 – EUR 500,000
  • Multiple H1 headings (33 found)
    EAA: EUR 1,000 – EUR 500,000

+32 more

Bandwidth Waste

€0.41 /mo

5515.3 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~552 KB per page load
    Saves €0.41/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

58
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
75
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
81
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

6.62 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

6.77 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.019

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

9.33 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

6.79 s

Detailed Report

Audit breakdown by category with detailed findings.

58

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

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:1150.706 label:Time to first byte subpart:timeToFirstByte] map[duration:3683.776 label:Resource load delay subpart:resourceLoadDelay] map[duration:117.672 label:Resource load duration subpart:resourceLoadDuration] map[duration:10.513 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: div.desktop:flex > div.tablet:w-[337px] > div > img
path: 1,HTML,1,BODY,0,DIV,0,MAIN,2,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,IMG
selector: div.desktop:flex > div.tablet:w-[337px] > div > img
snippet: <img src="https://cia.sec.miui.com/miui-14-homepage/phone.png?imageMogr2/thumbnail/5…" decoding="async" style="display: block; position: absolute; top: 0px; height: 100%; left: 0px;">

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.desktop:flex > div.tablet:w-[337px] > div > img
path: 1,HTML,1,BODY,0,DIV,0,MAIN,2,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,IMG
selector: div.desktop:flex > div.tablet:w-[337px] > div > img
snippet: <img src="https://cia.sec.miui.com/miui-14-homepage/phone.png?imageMogr2/thumbnail/5…" decoding="async" style="display: block; position: absolute; top: 0px; height: 100%; left: 0px;">

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.

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.

RequestCache TTLTransfer Size
cdn-file.hyperos.mi.com/mi-font-service/misans/450/cs.cfe08b0ba15098b3.22.woff2561651.0 s36.4 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/cs.bb73305ff7580e53.18.woff2561651.0 s36.2 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.ea3ec840cac76f1b.19.woff21229126.0 s37.6 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.c446acd779e5d2fe.17.woff21476133.0 s35.0 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/cs.8ee276e30de7c0fd.11.woff21641162.0 s34.4 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/cs.7ecaae6cd566bb8e.17.woff22406393.0 s35.2 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/cs.ae598ee92e49ae65.14.woff22406393.0 s35.1 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/cs.ecdf31e0d775693f.15.woff22062978.0 s34.6 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/cs.4ff84f9234f03a2b.7.woff21147590.0 s33.3 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/cs.4637e6312480205e.13.woff22492667.0 s34.5 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/cs.301b77c9b2d5cbb6.12.woff22492665.0 s34.3 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/cs.e2f46f4ad5ed6851.8.woff21581948.0 s33.2 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/cs.5ce26b64a1674f60.10.woff21891261.0 s33.5 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/650/cs.9d94f8221d93f686.1.woff2535778.0 s26.4 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/cs.246e8ea5197d9c54.6.woff2807971.0 s31.9 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/cs.e37f98eab1bffea9.1.woff2540116.0 s26.3 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/cs.4c99c20b51689926.9.woff22459679.0 s32.9 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/cs.5538fe618f9d7a60.5.woff22301181.0 s30.9 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.d5d63c06c4ee8ca8.3.woff2623333.0 s29.2 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/650/cs.9b3f0ca0431a350d.4.woff22062978.0 s29.9 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/cs.4173509397f8aa3a.2.woff2757178.0 s28.5 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/cs.b3063c48c56d5c40.4.woff22065877.0 s29.6 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/cs.1656bbfbf2b66170.3.woff21792848.0 s29.3 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.ee21b24834a16e24.1.woff2704436.0 s26.4 KiB
ssl-cdn.static.browser.mi-img.com/mistat-data/onetrack/onetrack.js10800.0 s3.4 KiB
cdn.cnbj1.fds.api.mi-img.com/common/jweixin-1.6.0.js86400.0 s5.6 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.4310947b63d7f2af.0.woff21384724.0 s21.8 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/cs.5dd139a4b434052f.0.woff22241102.0 s21.7 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/lt.af0b32b4f18a2804.0.woff2525751.0 s12.7 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/650/lt.13bc2edf157bd61c.0.woff22082855.0 s12.9 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/lt.7dcf87c3c9fcc1be.0.woff21629192.0 s12.3 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/lt.f095168230b5b92b.3.woff22314622.0 s9.0 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/450/lt.901de8df15597807.5.woff2500917.0 s5.2 KiB
cdn.cnbj1.fds.api.mi-img.com/common/jsonp.min.js86400.0 s1.5 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/650/lt.4f0a405949debe75.5.woff22574928.0 s5.3 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.9 s
URLTime Spent
miui.com/1.9 s
home.miui.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

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: 600 ms 133.2 KiB

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 reasonFailure 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 2.4 KiB
URLTransfer SizeEst Savings
cdn.cnbj1.fds.api.mi-img.com/common/jweixin-1.6.0.js5.1 KiB2.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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 45.8 KiB
URLTransfer SizeEst Savings
home.miui.com/_next/static/chunks/pages/_app-dedfdfe4da840c5e.js62.7 KiB45.8 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
Forced reflow
Improve image delivery
Modern HTTP
Optimize viewport for mobile
Max Potential First Input Delay 30 ms
Minify CSS
Avoids enormous network payloads Total size was 1,795 KiB
User Timing marks and measures 7 user timings
JavaScript execution time 0.5 s
Minimizes main-thread work 1.7 s
Avoid long main-thread tasks 4 long tasks found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 210 ms
Server Backend Latencies 2,490 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 20 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
Avoid non-composited animations
75

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
发布时间 div.safe-area > div.overflow-hidden > div > p.text-[#0D84FF]
发布时间 div.safe-area > div.overflow-hidden > div > p.text-[#0D84FF]
前往了解小米澎湃OS div.pointer-events-none > div.fixed > a.bg-[#3482FF] > div.mr-[6px]
继续了解 div.h-140 > div.w-full > div > div.mb-[10px]
参与调研 a > div.flex > div.ml-[18px] > div.mt-4
声明与说明 本页面中部分功能和服务可能因系统版本、手机型号不同存在差异,请以实际为准。 本页面所展示的内容和功能,不能保证能够提供永久服务,可能会因版权、商务… main > div.text-black > div.safe-area > div.text-[12px]
本页面中部分功能和服务可能因系统版本、手机型号不同存在差异,请以实际为准。 div.safe-area > div.text-[12px] > ul.ml-24 > li
本页面所展示的内容和功能,不能保证能够提供永久服务,可能会因版权、商务或技术条件的变化而调整,请以产品实际内容和功能为准。 div.safe-area > div.text-[12px] > ul.ml-24 > li
本页涉及的测试数据均来自小米实验室,均采用相同平台且配置相近设备,多次测试中数据可能存在小范围波动。 div.safe-area > div.text-[12px] > ul.ml-24 > li
新浪微博  |   官方微信  |  隐私政策  |  预置应用查询  |   简体中文 Copyright©2022 MIUI 京ICP备10046444号… main > div.text-black > div.safe-area > div.text-[12px]
新浪微博  |   官方微信  |  隐私政策  |  预置应用查询  |   简体中文 div.text-black > div.safe-area > div.text-[12px] > div
新浪微博 div.safe-area > div.text-[12px] > div > a.hover:underline
官方微信 div.text-[12px] > div > div.inline-block > div.relative
隐私政策 div.safe-area > div.text-[12px] > div > a.hover:underline
预置应用查询 div.safe-area > div.text-[12px] > div > a.hover:underline
简体中文 div.safe-area > div.text-[12px] > div > div.relative
京ICP备10046444号 div.text-black > div.safe-area > div.text-[12px] > a.hover:underline
 京公网安备 11010802037409号 div.text-black > div.safe-area > div.text-[12px] > a.hover:underline

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
2010年8月16日 div.safe-area > div.overflow-hidden > div > h3.text-h3
2010年10月29日 div.safe-area > div.overflow-hidden > div > h3.text-h3
2011年3月25日 div.safe-area > div.overflow-hidden > div > h3.text-h3
2012年1月19日 div.safe-area > div.overflow-hidden > div > h3.text-h3
2013年3月1日 div.safe-area > div.overflow-hidden > div > h3.text-h3
2014年8月16日 div.safe-area > div.overflow-hidden > div > h3.text-h3
2015年8月13日 div.safe-area > div.overflow-hidden > div > h3.text-h3
2016年5月10日 div.safe-area > div.overflow-hidden > div > h3.text-h3
2017年7月26日 div.safe-area > div.overflow-hidden > div > h3.text-h3
2018年5月31日 div.safe-area > div.overflow-hidden > div > h3.text-h3
2019年9月24日 div.safe-area > div.overflow-hidden > div > h3.text-h3
2020年4月27日 div.safe-area > div.overflow-hidden > div > h3.text-h3
2021年12月28日 div.safe-area > div.overflow-hidden > div > h3.text-h3
2022年12月11日 div.safe-area > div.overflow-hidden > div > h3.text-h3

These are opportunities to improve keyboard navigation in your application.

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.desktop:flex > div.tablet:w-[337px] > div > img div.desktop:flex > div.tablet:w-[337px] > div > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > h1.text-center > div.mb-[34px] > img div.overflow-hidden > h1.text-center > div.mb-[34px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > h1.text-center > div.mb-[34px] > img div.overflow-hidden > h1.text-center > div.mb-[34px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > h1.text-center > div.mb-[34px] > img div.overflow-hidden > h1.text-center > div.mb-[34px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > h1.text-center > div.mb-[34px] > img div.overflow-hidden > h1.text-center > div.mb-[34px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > h1.text-center > div.mb-[34px] > img div.overflow-hidden > h1.text-center > div.mb-[34px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > h1.text-center > div.mb-[34px] > img div.overflow-hidden > h1.text-center > div.mb-[34px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > h1.text-center > div.mb-[34px] > img div.overflow-hidden > h1.text-center > div.mb-[34px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > h1.text-center > div.mb-[34px] > img div.overflow-hidden > h1.text-center > div.mb-[34px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.fixed > a.bg-[#3482FF] > div.w-24 > img div.fixed > a.bg-[#3482FF] > div.w-24 > 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

Performance issues directly impact user engagement and conversion rates.

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
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.
Document has a main landmark.
Deprecated ARIA roles were not used
All heading elements contain content.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
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
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
Buttons have an accessible name
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.
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>`.
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.
81

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 / WarningSource
Unload event listeners are deprecated and will be removed.
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
83

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

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.desktop:flex > div.tablet:w-[337px] > div > img div.desktop:flex > div.tablet:w-[337px] > div > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > h1.text-center > div.mb-[34px] > img div.overflow-hidden > h1.text-center > div.mb-[34px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > h1.text-center > div.mb-[34px] > img div.overflow-hidden > h1.text-center > div.mb-[34px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > h1.text-center > div.mb-[34px] > img div.overflow-hidden > h1.text-center > div.mb-[34px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > h1.text-center > div.mb-[34px] > img div.overflow-hidden > h1.text-center > div.mb-[34px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > h1.text-center > div.mb-[34px] > img div.overflow-hidden > h1.text-center > div.mb-[34px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > h1.text-center > div.mb-[34px] > img div.overflow-hidden > h1.text-center > div.mb-[34px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > h1.text-center > div.mb-[34px] > img div.overflow-hidden > h1.text-center > div.mb-[34px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.overflow-hidden > h1.text-center > div.mb-[34px] > img div.overflow-hidden > h1.text-center > div.mb-[34px] > img
div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img div.overflow-hidden > div.mb-[33px] > div.h-[330px] > img
div.fixed > a.bg-[#3482FF] > div.w-24 > img div.fixed > a.bg-[#3482FF] > div.w-24 > 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
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

65
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
75
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
91
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.95 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

3.58 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.004

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

3.39 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

3.60 s

Detailed Report

Audit breakdown by category with detailed findings.

65

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

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

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.

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.

RequestCache TTLTransfer Size
cdn-file.hyperos.mi.com/mi-font-service/misans/400/cs.4173509397f8aa3a.2.woff2284176.0 s28.5 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.a84a90c19085b873.13.woff2489946.0 s34.7 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/600/cs.9d94f8221d93f686.1.woff2436040.0 s26.4 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/400/cs.246e8ea5197d9c54.6.woff2527950.0 s31.9 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.ea3ec840cac76f1b.19.woff21229105.0 s37.6 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/400/cs.aa06af0b430544a7.19.woff21231037.0 s37.5 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.8d4c2a096da7bd57.22.woff21131189.0 s36.3 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/600/cs.9b3f0ca0431a350d.4.woff2549817.0 s29.9 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.2d5e56f678ec44c0.18.woff22175964.0 s36.4 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.d6dcb01d8b56e74f.14.woff21650203.0 s35.3 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.c446acd779e5d2fe.17.woff21476112.0 s35.0 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/400/cs.7ecaae6cd566bb8e.17.woff21660278.0 s35.2 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.1e3fc1ac25caa055.16.woff21892460.0 s35.0 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.a3a1b249407f2a59.12.woff21484673.0 s34.4 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.368bba26dceab3f2.11.woff21481416.0 s34.4 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.a501143ec516ef89.8.woff2717258.0 s33.3 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.40dce8f14d27ae90.7.woff2844383.0 s33.4 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/400/cs.5ce26b64a1674f60.10.woff21047459.0 s33.5 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/300/cs.77537e483d531493.10.woff21110172.0 s33.5 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.7144a637759d3dd4.9.woff2681949.0 s33.0 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.11e6c18717a05b34.15.woff22441687.0 s34.7 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.9b238b24128e09d9.6.woff2695408.0 s32.1 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.501ea541ca5909ab.10.woff22299844.0 s33.6 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/400/cs.4c99c20b51689926.9.woff22493835.0 s32.9 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/300/cs.6140b72ecd3e7837.6.woff22307077.0 s31.9 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/400/cs.5538fe618f9d7a60.5.woff22266945.0 s30.9 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/400/cs.1656bbfbf2b66170.3.woff2702762.0 s29.3 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.d5d63c06c4ee8ca8.3.woff2623312.0 s29.2 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.21c946adc24fa32b.4.woff21253372.0 s29.8 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.cacebd01a7296815.5.woff22361028.0 s30.9 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/300/cs.46cf77f2dc17a254.5.woff22575256.0 s30.9 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.507aeb5f5cc9de3a.2.woff2692584.0 s28.5 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/400/cs.b3063c48c56d5c40.4.woff22271754.0 s29.6 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/300/cs.83d0a571a19e1fff.2.woff21193581.0 s28.5 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/300/cs.3259a3ddfc364c1c.4.woff22501284.0 s29.6 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.ee21b24834a16e24.1.woff2704415.0 s26.4 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/400/cs.e37f98eab1bffea9.1.woff21578968.0 s26.3 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/300/cs.5e0577a5e9687015.1.woff22262274.0 s26.4 KiB
ssl-cdn.static.browser.mi-img.com/mistat-data/onetrack/onetrack.js10800.0 s3.4 KiB
cdn.cnbj1.fds.api.mi-img.com/common/jweixin-1.6.0.js86400.0 s5.6 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/400/cs.5dd139a4b434052f.0.woff21121245.0 s21.7 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/cs.4310947b63d7f2af.0.woff21325911.0 s21.8 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/300/cs.0c6ffc96a626ab7c.0.woff22216491.0 s21.7 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/lt.af0b32b4f18a2804.0.woff2525808.0 s12.7 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/700/lt.78ff5fee56275328.0.woff2587781.0 s12.9 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/400/lt.7dcf87c3c9fcc1be.0.woff22356037.0 s12.3 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/lt.37a6c7d91c8498b1.3.woff2602954.0 s9.7 KiB
cdn.cnbj1.fds.api.mi-img.com/common/jsonp.min.js86400.0 s1.4 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/500/lt.b16e5debfe3729dc.5.woff21132303.0 s5.3 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/700/lt.2b2cd3bc8c621559.5.woff2706300.0 s5.2 KiB
cdn-file.hyperos.mi.com/mi-font-service/misans/400/lt.901de8df15597807.5.woff21652034.0 s5.2 KiB

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.

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:3643.5469990234374 label:Time to first byte subpart:timeToFirstByte] map[duration:578.3070009765624 label:Resource load delay subpart:resourceLoadDelay] map[duration:113.165 label:Resource load duration subpart:resourceLoadDuration] map[duration:163.478 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: div.desktop:flex > div.tablet:w-[337px] > div > img
path: 1,HTML,1,BODY,0,DIV,0,MAIN,2,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,IMG
selector: div.desktop:flex > div.tablet:w-[337px] > div > img
snippet: <img src="https://cia.sec.miui.com/miui-14-homepage/phone.png?imageMogr2/thumbnail/4…" decoding="async" style="display: block; position: absolute; top: 0px; height: 100%; left: 0px;">

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.desktop:flex > div.tablet:w-[337px] > div > img
path: 1,HTML,1,BODY,0,DIV,0,MAIN,2,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,IMG
selector: div.desktop:flex > div.tablet:w-[337px] > div > img
snippet: <img src="https://cia.sec.miui.com/miui-14-homepage/phone.png?imageMogr2/thumbnail/4…" decoding="async" style="display: block; position: absolute; top: 0px; height: 100%; left: 0px;">

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.

URLTransfer SizeDuration
/font/css?family=MiSans:300,450,500,650:Chinese_Simplify,...165.0 KiB362 ms

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.3 s
URLTime Spent
miui.com/1.3 s
home.miui.com/0.0 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 2.0 s
URLTime Spent
home.miui.com/2.1 s

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: 120 ms 181.4 KiB

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 reasonFailure 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 2.4 KiB
URLTransfer SizeEst Savings
cdn.cnbj1.fds.api.mi-img.com/common/jweixin-1.6.0.js5.1 KiB2.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

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 45.8 KiB
URLTransfer SizeEst Savings
home.miui.com/_next/static/chunks/pages/_app-dedfdfe4da840c5e.js62.7 KiB45.8 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
Forced reflow
Improve image delivery
Modern HTTP
Optimize viewport for mobile
Max Potential First Input Delay 30 ms
Minify CSS
Avoids enormous network payloads Total size was 2,113 KiB
User Timing marks and measures 7 user timings
JavaScript execution time 0.1 s
Minimizes main-thread work 0.5 s
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 240 ms
Server Backend Latencies 1,060 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid large layout shifts 2 layout shifts found
INP breakdown
Avoid long main-thread tasks
Avoid non-composited animations
75

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
发布时间 div.safe-area > div.flex > div > p.text-caption
发布时间 div.safe-area > div.flex > div > p.text-caption
发布时间 div.safe-area > div.flex > div > p.text-caption
发布时间 div.safe-area > div.flex > div > p.text-caption
发布时间 div.safe-area > div.flex > div > p.text-caption
发布时间 div.safe-area > div.flex > div > p.text-caption
发布时间 div.safe-area > div.flex > div > p.text-caption
发布时间 div.safe-area > div.flex > div > p.text-caption
发布时间 div.safe-area > div.flex > div > p.text-caption
发布时间 div.safe-area > div.flex > div > p.text-caption
发布时间 div.safe-area > div.flex > div > p.text-caption
发布时间 div.safe-area > div.flex > div > p.text-caption
发布时间 div.safe-area > div.flex > div > p.text-caption
发布时间 div.safe-area > div.flex > div > p.text-caption
前往了解小米澎湃OS div.pointer-events-none > div.fixed > a.bg-[#3482FF] > div.mr-[6px]
参与调研 a > div.flex > div.ml-[18px] > div.mt-4
声明与说明 本页面中部分功能和服务可能因系统版本、手机型号不同存在差异,请以实际为准。 本页面所展示的内容和功能,不能保证能够提供永久服务,可能会因版权、商务… main > div.text-black > div.safe-area > div.text-[12px]
本页面中部分功能和服务可能因系统版本、手机型号不同存在差异,请以实际为准。 div.safe-area > div.text-[12px] > ul.ml-24 > li
本页面所展示的内容和功能,不能保证能够提供永久服务,可能会因版权、商务或技术条件的变化而调整,请以产品实际内容和功能为准。 div.safe-area > div.text-[12px] > ul.ml-24 > li
本页涉及的测试数据均来自小米实验室,均采用相同平台且配置相近设备,多次测试中数据可能存在小范围波动。 div.safe-area > div.text-[12px] > ul.ml-24 > li
新浪微博  |   官方微信  |  隐私政策  |  预置应用查询  |   简体中文 Copyright©2022 MIUI 京ICP备10046444号… main > div.text-black > div.safe-area > div.text-[12px]
新浪微博  |   官方微信  |  隐私政策  |  预置应用查询  |   简体中文 div.text-black > div.safe-area > div.text-[12px] > div
新浪微博 div.safe-area > div.text-[12px] > div > a.hover:underline
官方微信 div.text-[12px] > div > div.inline-block > div.relative
隐私政策 div.safe-area > div.text-[12px] > div > a.hover:underline
预置应用查询 div.safe-area > div.text-[12px] > div > a.hover:underline
简体中文 div.safe-area > div.text-[12px] > div > div.relative
京ICP备10046444号 div.text-black > div.safe-area > div.text-[12px] > a.hover:underline
 京公网安备 11010802037409号 div.text-black > div.safe-area > div.text-[12px] > a.hover:underline

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
2010年8月16日 div.safe-area > div.flex > div > h3.text-h3
2010年10月29日 div.safe-area > div.flex > div > h3.text-h3
2011年3月25日 div.safe-area > div.flex > div > h3.text-h3
2012年1月19日 div.safe-area > div.flex > div > h3.text-h3
2013年3月1日 div.safe-area > div.flex > div > h3.text-h3
2014年8月16日 div.safe-area > div.flex > div > h3.text-h3
2015年8月13日 div.safe-area > div.flex > div > h3.text-h3
2016年5月10日 div.safe-area > div.flex > div > h3.text-h3
2017年7月26日 div.safe-area > div.flex > div > h3.text-h3
2018年5月31日 div.safe-area > div.flex > div > h3.text-h3
2019年9月24日 div.safe-area > div.flex > div > h3.text-h3
2020年4月27日 div.safe-area > div.flex > div > h3.text-h3
2021年12月28日 div.safe-area > div.flex > div > h3.text-h3
2022年12月11日 div.safe-area > div.flex > div > h3.text-h3

These are opportunities to improve keyboard navigation in your application.

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
span.w-full > span.inline-block > div.hidden > img span.w-full > span.inline-block > div.hidden > img
span.w-full > span.inline-block > div.hidden > img span.w-full > span.inline-block > div.hidden > img
span.w-full > span.inline-block > div.hidden > img span.w-full > span.inline-block > div.hidden > img
span.w-full > span.inline-block > div.hidden > img span.w-full > span.inline-block > div.hidden > img
div.absolute > div.self-center > div > img div.absolute > div.self-center > div > img
div.desktop:flex > div.tablet:w-[337px] > div > img div.desktop:flex > div.tablet:w-[337px] > div > img
div.flex > div.w-[487px] > div > img div.flex > div.w-[487px] > div > img
div.flex > div.w-[450px] > div > img div.flex > div.w-[450px] > div > img
div.flex > div.w-[465px] > div > img div.flex > div.w-[465px] > div > img
div.flex > div.w-[423px] > div > img div.flex > div.w-[423px] > div > img
div.flex > div.w-[442px] > div > img div.flex > div.w-[442px] > div > img
div.flex > div.w-[420px] > div > img div.flex > div.w-[420px] > div > img
div.flex > div.w-[530px] > div > img div.flex > div.w-[530px] > div > img
div > h1.text-h1 > div.mb-[34px] > img div > h1.text-h1 > div.mb-[34px] > img
div.flex > div.w-[446px] > div > img div.flex > div.w-[446px] > div > img
div > h1.text-h1 > div.mb-[34px] > img div > h1.text-h1 > div.mb-[34px] > img
div.flex > div.w-[417px] > div > img div.flex > div.w-[417px] > div > img
div > h1.text-h1 > div.mb-[34px] > img div > h1.text-h1 > div.mb-[34px] > img
div.flex > div.w-[422px] > div > img div.flex > div.w-[422px] > div > img
div > h1.text-h1 > div.mb-[34px] > img div > h1.text-h1 > div.mb-[34px] > img
div.flex > div.w-[430px] > div > img div.flex > div.w-[430px] > div > img
div > h1.text-h1 > div.mb-[34px] > img div > h1.text-h1 > div.mb-[34px] > img
div.flex > div.w-[406px] > div > img div.flex > div.w-[406px] > div > img
div > h1.text-h1 > div.mb-[34px] > img div > h1.text-h1 > div.mb-[34px] > img
div.flex > div.w-[415px] > div > img div.flex > div.w-[415px] > div > img
div > h1.text-h1 > div.mb-[34px] > img div > h1.text-h1 > div.mb-[34px] > img
div.flex > div.w-[405px] > div > img div.flex > div.w-[405px] > div > img
div > h1.text-h1 > div.mb-[34px] > img div > h1.text-h1 > div.mb-[34px] > img
div.fixed > a.bg-[#3482FF] > div.w-24 > img div.fixed > a.bg-[#3482FF] > div.w-24 > 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

Performance issues directly impact user engagement and conversion rates.

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
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.
Document has a main landmark.
Deprecated ARIA roles were not used
All heading elements contain content.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
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
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
Buttons have an accessible name
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.
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>`.
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.
77

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 / WarningSource
Unload event listeners are deprecated and will be removed.

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.

SourceDescription
Failed to load resource: the server responded with a status of 403 ()
ti
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 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
91

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
span.w-full > span.inline-block > div.hidden > img span.w-full > span.inline-block > div.hidden > img
span.w-full > span.inline-block > div.hidden > img span.w-full > span.inline-block > div.hidden > img
span.w-full > span.inline-block > div.hidden > img span.w-full > span.inline-block > div.hidden > img
span.w-full > span.inline-block > div.hidden > img span.w-full > span.inline-block > div.hidden > img
div.absolute > div.self-center > div > img div.absolute > div.self-center > div > img
div.desktop:flex > div.tablet:w-[337px] > div > img div.desktop:flex > div.tablet:w-[337px] > div > img
div.flex > div.w-[487px] > div > img div.flex > div.w-[487px] > div > img
div.flex > div.w-[450px] > div > img div.flex > div.w-[450px] > div > img
div.flex > div.w-[465px] > div > img div.flex > div.w-[465px] > div > img
div.flex > div.w-[423px] > div > img div.flex > div.w-[423px] > div > img
div.flex > div.w-[442px] > div > img div.flex > div.w-[442px] > div > img
div.flex > div.w-[420px] > div > img div.flex > div.w-[420px] > div > img
div.flex > div.w-[530px] > div > img div.flex > div.w-[530px] > div > img
div > h1.text-h1 > div.mb-[34px] > img div > h1.text-h1 > div.mb-[34px] > img
div.flex > div.w-[446px] > div > img div.flex > div.w-[446px] > div > img
div > h1.text-h1 > div.mb-[34px] > img div > h1.text-h1 > div.mb-[34px] > img
div.flex > div.w-[417px] > div > img div.flex > div.w-[417px] > div > img
div > h1.text-h1 > div.mb-[34px] > img div > h1.text-h1 > div.mb-[34px] > img
div.flex > div.w-[422px] > div > img div.flex > div.w-[422px] > div > img
div > h1.text-h1 > div.mb-[34px] > img div > h1.text-h1 > div.mb-[34px] > img
div.flex > div.w-[430px] > div > img div.flex > div.w-[430px] > div > img
div > h1.text-h1 > div.mb-[34px] > img div > h1.text-h1 > div.mb-[34px] > img
div.flex > div.w-[406px] > div > img div.flex > div.w-[406px] > div > img
div > h1.text-h1 > div.mb-[34px] > img div > h1.text-h1 > div.mb-[34px] > img
div.flex > div.w-[415px] > div > img div.flex > div.w-[415px] > div > img
div > h1.text-h1 > div.mb-[34px] > img div > h1.text-h1 > div.mb-[34px] > img
div.flex > div.w-[405px] > div > img div.flex > div.w-[405px] > div > img
div > h1.text-h1 > div.mb-[34px] > img div > h1.text-h1 > div.mb-[34px] > img
div.fixed > a.bg-[#3482FF] > div.w-24 > img div.fixed > a.bg-[#3482FF] > div.w-24 > 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
Document has a valid `hreflang`
robots.txt is valid
Document has a valid `rel=canonical`

Send Feedback