Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.284366] map[node:map[boundingRect:map[bottom:4484 height:4123 left:0 right:412 top:361 width:412] lhId:page-15-DIV nodeLabel:置顶 [已完结] 哔哩哔哩 Nekopara B站网页萌化主题終わりました。 September 2, 2017 1700149 置顶 [FGO] 日… path:2,HTML,1,BODY,2,DIV,7,DIV,6,MAIN,0,DIV,0,DIV,4,DIV selector:main.app-content-body > div.hbox > div.col > div#post-panel snippet:<div class="wrapper-md" id="post-panel"> type:node] score:0.284366 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://moe.best/usr/themes/handsome/assets/fonts/fontello/fontello.woff?7176355]] map[cause:Web font extra:map[type:url value:https://moe.best/usr/themes/handsome/assets/fonts/sourcesanspro/sourcesanspro-bold.woff]] map[cause:Web font extra:map[type:url value:https://moe.best/usr/themes/handsome/assets/fonts/sourcesanspro/sourcesanspro.woff]] map[cause:Web font extra:map[type:url value:https://moe.best/usr/themes/handsome/assets/fonts/iconfont/iconfont.woff?t=1517993881078]]] type:subitems]]]

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
/ajax/libs/font-awesome/4.7.0/fonts/fontawesome-webfont.w...	205 ms
/npm/bootstrap@3.3.7/dist/fonts/glyphicons-halflings-regu...	80 ms
moe.best/usr/themes/handsome/assets/fonts/iconfont/iconfont.woff?t=1517993881078	30 ms
moe.best/usr/themes/handsome/assets/fonts/fontello/fontello.woff?7176355	25 ms
moe.best/usr/themes/handsome/assets/fonts/sourcesanspro/sourcesanspro-bold.woff	25 ms
moe.best/usr/themes/handsome/assets/fonts/sourcesanspro/sourcesanspro.woff	25 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
div > a > span.thumb-lg > img.img-full `div > a > span.thumb-lg > img.img-full`	moe.best/usr/img/avatar1.png	311.0 KiB	302.5 KiB
div.panel > div.index-post-img > a > div.item-thumb `div.panel > div.index-post-img > a > div.item-thumb`	moe.best/usr/uploads/2020/03/1061894612.png	179.8 KiB	140.7 KiB
div.panel > div.index-post-img > a > div.item-thumb `div.panel > div.index-post-img > a > div.item-thumb`	moe.best/usr/uploads/2019/11/3624569711.png	152.2 KiB	113.2 KiB
div.panel > div.index-post-img > a > div.item-thumb `div.panel > div.index-post-img > a > div.item-thumb`	moe.best/usr/uploads/2020/04/1696449540.png	147.4 KiB	108.3 KiB
div.panel > div.index-post-img > a > div.item-thumb `div.panel > div.index-post-img > a > div.item-thumb`	moe.best/usr/uploads/2019/11/2612016269.png	128.1 KiB	89.0 KiB
div.panel > div.index-post-img > a > div.item-thumb `div.panel > div.index-post-img > a > div.item-thumb`	moe.best/usr/uploads/2023/07/2045095716.png	122.8 KiB	83.7 KiB
div.panel-small > div.index-post-img-small > a > div.item-thumb-small `div.panel-small > div.index-post-img-small > a > div.item-thumb-small`	moe.best/usr/uploads/2018/08/3477842073.jpg	118.4 KiB	79.3 KiB
div.panel > div.index-post-img > a > div.item-thumb `div.panel > div.index-post-img > a > div.item-thumb`	moe.best/usr/uploads/2020/03/3190944563.png	113.5 KiB	74.5 KiB
div.panel-small > div.index-post-img-small > a > div.item-thumb-small `div.panel-small > div.index-post-img-small > a > div.item-thumb-small`	moe.best/usr/uploads/2021/12/2404136611.png	112.0 KiB	73.0 KiB
div.panel > div.index-post-img > a > div.item-thumb `div.panel > div.index-post-img > a > div.item-thumb`	moe.best/usr/uploads/2019/12/1998775108.png	102.9 KiB	63.8 KiB
div.panel > div.index-post-img > a > div.item-thumb `div.panel > div.index-post-img > a > div.item-thumb`	moe.best/usr/uploads/2022/01/3305493386.png	101.6 KiB	62.5 KiB
div.panel > div.index-post-img > a > div.item-thumb `div.panel > div.index-post-img > a > div.item-thumb`	moe.best/usr/uploads/2019/11/1383797378.png	92.4 KiB	53.4 KiB
body#body > div#alllayout > div#bg `body#body > div#alllayout > div#bg`	moe.best/usr/img/bg/bg2.jpg	196.4 KiB	51.7 KiB
div.panel-small > div.index-post-img-small > a > div.item-thumb-small `div.panel-small > div.index-post-img-small > a > div.item-thumb-small`	moe.best/usr/uploads/2018/01/2519960032.jpg	55.3 KiB	16.2 KiB
div.panel-small > div.index-post-img-small > a > div.item-thumb-small `div.panel-small > div.index-post-img-small > a > div.item-thumb-small`	moe.best/usr/uploads/2018/02/136917309.jpg	65.5 KiB	16.2 KiB

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-12-DIV

nodeLabel: body#body > div#alllayout > div#bg

path: 2,HTML,1,BODY,2,DIV,1,DIV

selector: body#body > div#alllayout > div#bg

snippet: <div id="bg">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
code.bdstatic.com/npm/jquery@2.2.4/dist/jquery.min.js	30.8 KiB	214 ms
code.bdstatic.com/npm/bootstrap@3.3.7/dist/css/bootstrap.min.css	20.3 KiB	1.2 s
cdnjs.loli.net/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css	7.4 KiB	871 ms
moe.best/usr/themes/handsome/assets/css/handsome.min.css?v=5.0.020181231301	27.6 KiB	628 ms
moe.best/usr/themes/handsome/assets/css/function.min.css?v=5.0.020181231301	7.0 KiB
moe.best/usr/themes/handsome/assets/css/font.min.css?v=5.0.020181231301	246 B
/usr/themes/handsome/assets/css/features/code/custome.min...	684 B
/usr/themes/handsome/assets/css/features/jquery.fancybox....	3.2 KiB
moe.best/usr/themes/handsome/assets/css/github.md.mod.css?v=1.4.7	1.8 KiB
moe.best/usr/themes/handsome/assets/css/handsome.css?v=1.7.0	3.4 KiB

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
zz.bdstatic.com/linksubmit/push.js	86400.0 s	552 B
moe.best/api/live/?cb=updateLiveStatus	0.0 ms	195 B
sp0.baidu.com/9_Q4simg2RQJ8t7jm9iCKT-xh_/s.gif?l=https://moe.best/	0.0 ms	116 B

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
置顶 [已完结] 哔哩哔哩 Nekopara B站网页萌化主题終わりました。 September 2, 2017 1700149 置顶 [FGO] 日… `main.app-content-body > div.hbox > div.col > div#post-panel`	0.284

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 310 ms 43.4 KiB

URL	Transfer Size	Est Savings
moe.best/usr/themes/handsome/assets/css/handsome.min.css?v=5.0.020181231301	27.5 KiB	24.9 KiB
code.bdstatic.com/npm/bootstrap@3.3.7/dist/css/bootstrap.min.css	19.8 KiB	18.5 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 160 ms 172.1 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtag/js?id=G-RCJMCHRD6E&cx=c&gtm=4e67m0	151.1 KiB	67.6 KiB
www.googletagmanager.com/gtag/js?id=UA-105785108-1	128.9 KiB	65.0 KiB
code.bdstatic.com/npm/mathjax@2.7.9/config/TeX-AMS-MML_SVG.js	71.7 KiB	39.5 KiB

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Style & Layout	1.6 s
Other	1.1 s
Script Evaluation	1.1 s
Script Parsing & Compilation	220 ms
Rendering	133 ms
Parse HTML & CSS	96 ms

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 reason	Failure type
The page has an unload handler in the main frame.	Actionable

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
moe.best/usr/img/avatar1.png	311.4 KiB
moe.best/usr/img/bg/bg2.jpg	196.7 KiB
moe.best/usr/uploads/2020/03/1061894612.png	180.0 KiB
moe.best/usr/img/kotori.png	160.5 KiB
moe.best/usr/uploads/2019/11/3624569711.png	152.5 KiB
www.googletagmanager.com/gtag/js?id=G-RCJMCHRD6E&cx=c&gtm=4e67m0	151.1 KiB
moe.best/usr/uploads/2020/04/1696449540.png	147.6 KiB
www.googletagmanager.com/gtag/js?id=UA-105785108-1	129.3 KiB
moe.best/usr/uploads/2019/11/2612016269.png	128.3 KiB
moe.best/usr/uploads/2023/07/2045095716.png	123.0 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
div > a > span.thumb-lg > img.img-full `div > a > span.thumb-lg > img.img-full`	moe.best/usr/img/avatar1.png

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

●Document request latency

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●JavaScript execution time 1.2 s

●Avoid long main-thread tasks 12 long tasks found

●Network Requests

●Network Round Trip Times 280 ms

●Server Backend Latencies 200 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

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

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
LOLI! NEKO! `body#body > div#alllayout > header#header`

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
© 2016-2026 Copyright JindaiKirin \| SiteMap `body#body > div#alllayout > footer#footer`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#alllayout > header#header > div.navbar-header > button.pull-right `div#alllayout > header#header > div.navbar-header > button.pull-right`
div#alllayout > header#header > div.navbar-header > button.pull-left `div#alllayout > header#header > div.navbar-header > button.pull-left`

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 > a > span.thumb-lg > img.img-full `div > a > span.thumb-lg > img.img-full`
ul.list-group > li.list-group-item > a.pull-left > img.img-circle `ul.list-group > li.list-group-item > a.pull-left > img.img-circle`
ul.list-group > li.list-group-item > a.pull-left > img.img-circle `ul.list-group > li.list-group-item > a.pull-left > img.img-circle`
ul.list-group > li.list-group-item > a.pull-left > img.img-circle `ul.list-group > li.list-group-item > a.pull-left > img.img-circle`
ul.list-group > li.list-group-item > a.pull-left > img.img-circle `ul.list-group > li.list-group-item > a.pull-left > img.img-circle`
ul.list-group > li.list-group-item > a.pull-left > img.img-circle `ul.list-group > li.list-group-item > a.pull-left > img.img-circle`
ul.list-group > li.list-group-item > a.pull-left > img.img-circle `ul.list-group > li.list-group-item > a.pull-left > img.img-circle`
ul.list-group > li.list-group-item > a.pull-left > img.img-circle `ul.list-group > li.list-group-item > a.pull-left > img.img-circle`
ul.list-group > li.list-group-item > a.pull-left > img.img-circle `ul.list-group > li.list-group-item > a.pull-left > img.img-circle`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#aside-user > div.dropdown > div > a `div#aside-user > div.dropdown > div > a`
div.blog-post > div.panel-small > div.index-post-img-small > a `div.blog-post > div.panel-small > div.index-post-img-small > a`
div.blog-post > div.panel-small > div.post-meta > a.ahover `div.blog-post > div.panel-small > div.post-meta > a.ahover`
div.blog-post > div.panel-small > div.index-post-img-small > a `div.blog-post > div.panel-small > div.index-post-img-small > a`
div.blog-post > div.panel-small > div.post-meta > a.ahover `div.blog-post > div.panel-small > div.post-meta > a.ahover`
div.blog-post > div.panel-small > div.index-post-img-small > a `div.blog-post > div.panel-small > div.index-post-img-small > a`
div.blog-post > div.panel-small > div.post-meta > a.ahover `div.blog-post > div.panel-small > div.post-meta > a.ahover`
div.blog-post > div.panel-small > div.index-post-img-small > a `div.blog-post > div.panel-small > div.index-post-img-small > a`
div.blog-post > div.panel-small > div.post-meta > a.ahover `div.blog-post > div.panel-small > div.post-meta > a.ahover`
div.blog-post > div.panel > div.index-post-img > a `div.blog-post > div.panel > div.index-post-img > a`
div.blog-post > div.panel > div.post-meta > a.ahover `div.blog-post > div.panel > div.post-meta > a.ahover`
div.blog-post > div.panel > div.index-post-img > a `div.blog-post > div.panel > div.index-post-img > a`
div.blog-post > div.panel > div.post-meta > a.ahover `div.blog-post > div.panel > div.post-meta > a.ahover`
div.blog-post > div.panel > div.index-post-img > a `div.blog-post > div.panel > div.index-post-img > a`
div.blog-post > div.panel > div.post-meta > a.ahover `div.blog-post > div.panel > div.post-meta > a.ahover`
div.blog-post > div.panel > div.index-post-img > a `div.blog-post > div.panel > div.index-post-img > a`
div.blog-post > div.panel > div.post-meta > a.ahover `div.blog-post > div.panel > div.post-meta > a.ahover`
div.blog-post > div.panel > div.index-post-img > a `div.blog-post > div.panel > div.index-post-img > a`
div.blog-post > div.panel > div.post-meta > a.ahover `div.blog-post > div.panel > div.post-meta > a.ahover`
div.blog-post > div.panel > div.index-post-img > a `div.blog-post > div.panel > div.index-post-img > a`
div.blog-post > div.panel > div.post-meta > a.ahover `div.blog-post > div.panel > div.post-meta > a.ahover`
div.blog-post > div.panel > div.index-post-img > a `div.blog-post > div.panel > div.index-post-img > a`
div.blog-post > div.panel > div.post-meta > a.ahover `div.blog-post > div.panel > div.post-meta > a.ahover`
div.blog-post > div.panel > div.index-post-img > a `div.blog-post > div.panel > div.index-post-img > a`
div.blog-post > div.panel > div.post-meta > a.ahover `div.blog-post > div.panel > div.post-meta > a.ahover`
div.blog-post > div.panel > div.index-post-img > a `div.blog-post > div.panel > div.index-post-img > a`
div.blog-post > div.panel > div.post-meta > a.ahover `div.blog-post > div.panel > div.post-meta > a.ahover`
div.blog-post > div.panel > div.index-post-img > a `div.blog-post > div.panel > div.index-post-img > a`
div.blog-post > div.panel > div.post-meta > a.ahover `div.blog-post > div.panel > div.post-meta > a.ahover`
nav.text-center > ol.page-navigator > li.next > a `nav.text-center > ol.page-navigator > li.next > a`
div#widget-tabs-4-random > ul.list-group > li.list-group-item > a.pull-left `div#widget-tabs-4-random > ul.list-group > li.list-group-item > a.pull-left`
div#widget-tabs-4-random > ul.list-group > li.list-group-item > a.pull-left `div#widget-tabs-4-random > ul.list-group > li.list-group-item > a.pull-left`
div#widget-tabs-4-random > ul.list-group > li.list-group-item > a.pull-left `div#widget-tabs-4-random > ul.list-group > li.list-group-item > a.pull-left`
div#widget-tabs-4-random > ul.list-group > li.list-group-item > a.pull-left `div#widget-tabs-4-random > ul.list-group > li.list-group-item > a.pull-left`
div#widget-tabs-4-random > ul.list-group > li.list-group-item > a.pull-left `div#widget-tabs-4-random > ul.list-group > li.list-group-item > a.pull-left`
section#rcm_sidebar > ul.list-group > li.list-group-item > a.pull-left `section#rcm_sidebar > ul.list-group > li.list-group-item > a.pull-left`
section#rcm_sidebar > ul.list-group > li.list-group-item > a.pull-left `section#rcm_sidebar > ul.list-group > li.list-group-item > a.pull-left`
section#rcm_sidebar > ul.list-group > li.list-group-item > a.pull-left `section#rcm_sidebar > ul.list-group > li.list-group-item > a.pull-left`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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]`s are contained by their required parent element

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

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

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

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

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	hm.baidu.com/hm.js?5925ac39257cc13416c64fac1080a24d line 1, col 274

●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

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Login `div.collapse > ul.nav > li#easyLogin > a.dropdown-toggle`
body#body > div#alllayout > div#content > a.off-screen-toggle `body#body > div#alllayout > div#content > a.off-screen-toggle`

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 > a > span.thumb-lg > img.img-full `div > a > span.thumb-lg > img.img-full`
ul.list-group > li.list-group-item > a.pull-left > img.img-circle `ul.list-group > li.list-group-item > a.pull-left > img.img-circle`
ul.list-group > li.list-group-item > a.pull-left > img.img-circle `ul.list-group > li.list-group-item > a.pull-left > img.img-circle`
ul.list-group > li.list-group-item > a.pull-left > img.img-circle `ul.list-group > li.list-group-item > a.pull-left > img.img-circle`
ul.list-group > li.list-group-item > a.pull-left > img.img-circle `ul.list-group > li.list-group-item > a.pull-left > img.img-circle`
ul.list-group > li.list-group-item > a.pull-left > img.img-circle `ul.list-group > li.list-group-item > a.pull-left > img.img-circle`
ul.list-group > li.list-group-item > a.pull-left > img.img-circle `ul.list-group > li.list-group-item > a.pull-left > img.img-circle`
ul.list-group > li.list-group-item > a.pull-left > img.img-circle `ul.list-group > li.list-group-item > a.pull-left > img.img-circle`
ul.list-group > li.list-group-item > a.pull-left > img.img-circle `ul.list-group > li.list-group-item > a.pull-left > img.img-circle`

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

●robots.txt is valid

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`