Skip to content
https://home-assistant.io

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

94

Performance

Insights

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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.grid > div.hero-demo > div.demo-frame-wrapper > img
path: 5,HTML,2,BODY,1,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,0,IMG
selector: div.grid > div.hero-demo > div.demo-frame-wrapper > img
snippet: <img src="/images/app-loading.webp">

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
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
value: No additional origins are good candidates for preconnecting

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.

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.

URLResource SizeEst Savings
Shop our merch store! Grab some swag while supporting the Open Home Foundation div.frontpage > div.grid > div.grid__item > a.material-card
www.home-assistant.io/images/frontpage/merch-store.webp176.5 KiB88.6 KiB
Home Assistant Connect ZBT-2 The easiest way to start with Zigbee or Thread is … div.frontpage > div.grid > div.grid__item > a.material-card
www.home-assistant.io/images/frontpage/zbt-2-frontpage.webp125.8 KiB37.9 KiB
Join us in Utrecht on April 8 for State of the Open Home 2026. div.frontpage > div.grid > div.grid__item > a.material-card
www.home-assistant.io/images/frontpage/sotoh-2026.webp102.9 KiB33.6 KiB
State of the Open Home 2025 Learn about our progress so far and also the roadma… div.frontpage > div.grid > div.grid__item > a.material-card
www.home-assistant.io/images/frontpage/feature-sotoh2025.jpg59.5 KiB18.8 KiB

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

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: 40 ms 21.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: 0.0 ms 29.6 KiB
URLTransfer SizeEst Savings
cdn.jsdelivr.net/npm/@docsearch/js@3/dist/umd/index.min.js35.5 KiB29.6 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
ArsTechnica.com logo div.seen-press > a > div.material-card > img
www.home-assistant.io/images/press/arstechnica.svg
Ct logo div.seen-press > a > div.material-card > img
www.home-assistant.io/images/press/ct.png
Nabu Casa logo div.sponsored-by > div.material-card > a > img
www.home-assistant.io/images/sponsors/nabu_casa.svg
Home Assistant div.footer-nav > div.company > div.title > img
www.home-assistant.io/images/footer-logo-text.svg
Tweakers.net logo div.seen-press > a > div.material-card > img
www.home-assistant.io/images/press/tweakers.png
OpenSource.com logo div.seen-press > a > div.material-card > img
www.home-assistant.io/images/press/opensource.com.svg
Linus Tech Tips logo div.seen-press > a > div.material-card > img.square
www.home-assistant.io/images/press/ltt.svg
Linux Magazine logo div.seen-press > a > div.material-card > img
www.home-assistant.io/images/press/LinuxMagazine.png
The Verge logo div.seen-press > a > div.material-card > img
www.home-assistant.io/images/press/theverge.svg
Troy Hunt logo div.seen-press > a > div.material-card > img.square
www.home-assistant.io/images/press/troyhunt.jpg
ProductHunt.com logo div.seen-press > a > div.material-card > img
www.home-assistant.io/images/press/producthunt.com.png
Linux.com logo div.seen-press > a > div.material-card > img
www.home-assistant.io/images/press/linux.com.png
Tom's Hardware logo div.seen-press > a > div.material-card > img
www.home-assistant.io/images/press/tomshardware.svg
Deploys by Netlify Badge div.socials > div.web-notice > a > img
www.home-assistant.io/images/frontpage/netlify.svg
GitHub logo div.hero-socialproof > a > div.hero-github-top-project > img
www.home-assistant.io/images/frontpage/hero-github-logo.svg
Top open source project trophy div.hero-socialproof > a > div.hero-github-top-project > img
www.home-assistant.io/images/frontpage/hero-trophy.svg

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

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: 411 ms
Time to Interactive 1.4 s
Layout shift culprits
Optimize DOM size
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Max Potential First Input Delay 20 ms
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 1,428 KiB
JavaScript execution time 0.0 s
Minimizes main-thread work 0.2 s
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 30 ms
Server Backend Latencies 140 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 30 ms
Avoid large layout shifts 4 layout shifts found
INP breakdown
User Timing marks and measures
Avoid long main-thread tasks
Avoid non-composited animations
84

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
2026.4.3 div.grid-wrapper > div.grid > div.grid__item > a.release-date
We are a non-profit and can't be sold or acquired. div.grid__item > a.material-card > div > p.lead
Home Assistant is a project by the Open Home Foundation. div.grid__item > a.material-card > div > p
Read our founder's vision for the perfect home automation div.grid > div.grid__item > a.material-card > p.lead
LEARN MORE div.grid__item > div.join-community > div.links > a
LEARN MORE div.grid__item > div.join-community > div.links > a
FORUMS div.grid__item > div.join-community > div.links > a
CHAT div.grid__item > div.join-community > div.links > a
NEWSLETTER div.grid__item > div.join-community > div.links > a
Works with over 1000 brands div.grid__item > div.feature-cards > div.card > div.card-header
EXPLORE INTEGRATIONS div.feature-cards > div.card > div.card-content > a.button
Powerful automations div.grid__item > div.feature-cards > div.card > div.card-header
EXPLORE AUTOMATIONS div.feature-cards > div.card > div.card-content > a.button
Versatile dashboards div.grid__item > div.feature-cards > div.card > div.card-header
EXPLORE DASHBOARDS div.feature-cards > div.card > div.card-content > a.button
Assist, our voice assistant div.grid__item > div.feature-cards > div.card > div.card-header
EXPLORE ASSIST div.feature-cards > div.card > div.card-content > a.button
Extend your system with apps div.grid__item > div.feature-cards > div.card > div.card-header
Explore apps for Home Assistant div.feature-cards > div.card > div.card-content > a.button
All your smart home data stays local div.grid__item > div.feature-cards > div.card > div.card-header
Companion Mobile Apps div.grid__item > div.feature-cards > div.card > div.card-header
DOWNLOAD APPS div.feature-cards > div.card > div.card-content > a.button
Home Energy Management div.grid__item > div.feature-cards > div.card > div.card-header
LEARN MORE div.feature-cards > div.card > div.card-content > a.button
Home Assistant Cast div.grid__item > div.feature-cards > div.card > div.card-header
LEARN MORE div.feature-cards > div.card > div.card-content > a.button
NFC Tags div.grid__item > div.feature-cards > div.card > div.card-header
LEARN MORE div.feature-cards > div.card > div.card-content > a.button
Open Home Foundation div.footer-nav > div.company > p > a
Nabu Casa div.footer-nav > div.company > p > a
GitHub repo div.grid__item > ul > li > a.external-link
Developers Portal div.grid__item > ul > li > a.external-link
Design Portal div.grid__item > ul > li > a.external-link
Data Science Portal div.grid__item > ul > li > a.external-link
Community Forum div.grid__item > ul > li > a.external-link
Creator Network div.grid__item > ul > li > a.external-link
Works With Home Assistant div.grid__item > ul > li > a.external-link
Our community div.grid__item > ul > li > a
Reporting issues div.grid__item > ul > li > a
Integration Alerts div.grid__item > ul > li > a.external-link
Security Alerts div.grid__item > ul > li > a
System Status div.grid__item > ul > li > a.external-link
iOS and Apple devices div.grid__item > ul > li > a.external-link
Android and Wear OS div.grid__item > ul > li > a.external-link
...and more! div.grid__item > ul > li > a.external-link
Merch store div.grid__item > ul > li > a
Home Assistant Cloud div.grid__item > ul > li > a
Privacy Notices div.grid__item > ul > li > a
Contributor License Agreement div.grid__item > ul > li > a
Terms of Service div.grid__item > ul > li > a
Code of Conduct div.grid__item > ul > li > a
Credits div.grid__item > ul > li > a
License div.grid__item > ul > li > a
Sign up for our newsletter div.footer-nav > div.socials > p > a.external-link
Works With Home Assistant div.socials > div.web-notice > p > a
email our team div.socials > div.web-notice > p > a
contact support div.socials > div.web-notice > p > a
Jekyll div.socials > div.web-notice > p > a
Oscailte theme div.socials > div.web-notice > p > a

These are opportunities to improve the legibility of your content.

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.grid > div.hero-demo > div.demo-frame-wrapper > img div.grid > div.hero-demo > div.demo-frame-wrapper > img

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.grid-wrapper > div.grid > div.grid__item > a.site-title div.grid-wrapper > div.grid > div.grid__item > a.site-title

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

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Shop our merch store! Grab some swag while supporting the Open Home Foundation div.frontpage > div.grid > div.grid__item > a.material-card
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
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
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<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
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
`[role]`s have all required `[aria-*]` attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
`[role]` values are valid
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
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
`<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.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
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.
100

Best Practices

Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No 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
85

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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.grid > div.hero-demo > div.demo-frame-wrapper > img div.grid > div.hero-demo > div.demo-frame-wrapper > 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 are crawlable
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback