Mobile 375 × 812

Desktop 1440 × 900

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.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
1 image-in-link without alt text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
1 image-only link(s) without alt text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](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.comThis badge auto-updates with your latest scan result.
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.
9 barrier(s) likely increasing bounce by ~31%.
Page takes 6.8s to load
+12% bounceUsers abandon at ~3s — you're 4.3s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
No HSTS header
+1% bounceReturning 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% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
Viewport disables user zoom
+2% bounceVisitors 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
No Open Graph tags
+2% bounceLinks 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% bounceNo 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% bounceUnder 300 words — visitors bounce looking for substance, search engines rank competitors first
Fix: Add a substantive FAQ, product detail, or case-study section
No skip-to-content link
+1% bounceKeyboard 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% bounceClicks 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.
€383 investment → €4,172/month returns + EUR 20,500,000 risk avoided
€383
4h · 5 findings
€4,172 /mo
~€50,061 / year
EUR 20,500,000
if kept compliant
€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.
4.5 developer hours at €85/hr
Based on European Union rates (€85/hr)
Start here for the best return on investment
€1,708,334 / month at risk
~€20,500,005 / year if left unfixed
€20,500,000
+32 more
€0.41 /mo
5515.3 MB/mo × 0.074 EUR/GB
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.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
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
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
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
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| /font/css?family=MiSans:300,450,500,650:Chinese_Simplify,... | 114.9 KiB | 3.8 s |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time 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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /font/css?family=MiSans:300,450,500,650:Chinese_Simplify,... | 114.7 KiB | 114.7 KiB |
| home.miui.com/_next/static/css/75b70099a3cc6a49.css | 20.2 KiB | 18.5 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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| cdn.cnbj1.fds.api.mi-img.com/common/jweixin-1.6.0.js | 5.1 KiB | 2.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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
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
| URL | Transfer Size | Est Savings |
|---|---|---|
| home.miui.com/_next/static/chunks/pages/_app-dedfdfe4da840c5e.js | 62.7 KiB | 45.8 KiB |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
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.
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.
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.
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.
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.
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. | hm.baidu.com/hm.js?48d720a449f859af28f0c2975455d83a line 1, col 274 |
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.
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.
Performance issues directly impact user engagement and conversion rates.
To appear in search results, crawlers need access to your app.
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.
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.
Industry-standard audits powered by Google Lighthouse. — Desktop
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
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| /font/css?family=MiSans:300,450,500,650:Chinese_Simplify,... | 165.0 KiB | 362 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time 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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /font/css?family=MiSans:300,450,500,650:Chinese_Simplify,... | 164.8 KiB | 164.8 KiB |
| home.miui.com/_next/static/css/75b70099a3cc6a49.css | 20.2 KiB | 16.6 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
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| cdn.cnbj1.fds.api.mi-img.com/common/jweixin-1.6.0.js | 5.1 KiB | 2.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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
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
| URL | Transfer Size | Est Savings |
|---|---|---|
| home.miui.com/_next/static/chunks/pages/_app-dedfdfe4da840c5e.js | 62.7 KiB | 45.8 KiB |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
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.
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.
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.
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.
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.
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. | hm.baidu.com/hm.js?48d720a449f859af28f0c2975455d83a line 1, col 274 |
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Failed to load resource: the server responded with a status of 403 () | |
home.miui.com/_next/static/chunks/22-5eba672c80cdf4ec.js line 5, col 40830 | ti |
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.
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.
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.
Send Feedback