Skip to content
https://unsplash.com

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.

91

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.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:39.709 source:map[type:text value:[unattributed]]]]

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: Person working on laptop at wooden table with breakfast.
path: 1,HTML,1,BODY,2,DIV,0,DIV,0,DIV,1,DIV,1,DIV,5,DIV,2,DIV,0,DIV,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,FIGURE,0,DIV,0,DIV,0,A,0,IMG
selector: div.container-WSKyvi > div.container-gr86hO > a.photoInfoLink-mG0SPO > img.responsiveImg-czQTaZ
snippet: <img alt="Person working on laptop at wooden table with breakfast." sizes="(min-width: 1359px) 416px, (min-width: 992px) calc((100vw - 96px) / 3), (m…" srcset="https://images.unsplash.com/photo-1773332598289-ed0444ad1d6f?w=100&amp;auto=fo…" src="https://images.unsplash.com/photo-1773332598289-ed0444ad1d6f?w=500&amp;auto=fo…" itemprop="thumbnailUrl" data-perf="eager-loaded-img" style="background-image: url(&quot;data:image/bmp;base64,Qk32BAAAAAAAADYAAAAoAAAACAAAAAg…&quot;);" class="responsiveImg-czQTaZ" data-testid="asset-grid-masonry-img" width="1830" height="2740">

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

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.speedcurve.com/js/lux.es2020.js?id=1404933453600.0 s10.6 KiB

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
Unique yellow cube houses viewed from below div.container-WSKyvi > div.container-gr86hO > a.photoInfoLink-mG0SPO > img.responsiveImg-czQTaZ
/photo-1776179343076-236a5893ec3e?w=500&auto=format&fit=c...69.1 KiB30.7 KiB
Delicate white wildflowers bloom in a dry, grassy field. div.container-WSKyvi > div.container-gr86hO > a.photoInfoLink-mG0SPO > img.responsiveImg-czQTaZ
/photo-1775649207612-5908ff864a69?w=500&auto=format&fit=c...41.3 KiB15.3 KiB
Person working on laptop at wooden table with breakfast. div.container-WSKyvi > div.container-gr86hO > a.photoInfoLink-mG0SPO > img.responsiveImg-czQTaZ
/photo-1773332598289-ed0444ad1d6f?w=500&auto=format&fit=c...34.6 KiB12.8 KiB

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

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 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 197.2 KiB
URLTransfer SizeEst Savings
unsplash.com/a/en-US/main.f6a26741.js138.7 KiB84.9 KiB
unsplash.com/a/en-US/6990.1c294f34.js129.0 KiB61.2 KiB
unsplash.com/a/en-US/4142.9b883bb0.js118.4 KiB51.2 KiB

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

●Time to Interactive 2.2 s
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●LCP breakdown
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 2,087 KiB
●User Timing marks and measures 3 user timings
●JavaScript execution time 0.9 s
●Minimizes main-thread work 1.5 s
●Avoid long main-thread tasks 3 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 10 ms
●Server Backend Latencies 20 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 20 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
90

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.

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
section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image1-nLl6fh section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image1-nLl6fh
section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image2-DDKbqx section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image2-DDKbqx
section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image3-FwtwiQ section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image3-FwtwiQ
section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image4-U_BHob section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image4-U_BHob
section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image5-f5xhoi section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image5-f5xhoi
section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image6-Z964gj section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image6-Z964gj

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
Go to Microsoft Copilot's profile div.actionsBottom-BnTMN5 > div.userLinkContainer-ZWhFxH > span#base-ui-_r_g_ > a.link-dYuCfx
div.overlayForeground-qabjQ0 > div.actionsTop-v4lYiD > div > a.link-GVbnGZ div.overlayForeground-qabjQ0 > div.actionsTop-v4lYiD > div > a.link-GVbnGZ
div.overlayForeground-qabjQ0 > div.actionsTop-v4lYiD > div > a.link-GVbnGZ div.overlayForeground-qabjQ0 > div.actionsTop-v4lYiD > div > a.link-GVbnGZ
div.overlayForeground-qabjQ0 > div.actionsTop-v4lYiD > div > a.link-GVbnGZ div.overlayForeground-qabjQ0 > div.actionsTop-v4lYiD > div > a.link-GVbnGZ
Go to Land O'Lakes, Inc.'s profile div.actionsBottom-BnTMN5 > div.userLinkContainer-ZWhFxH > span#base-ui-_r_2i_ > a.link-dYuCfx
div.overlayForeground-qabjQ0 > div.actionsTop-v4lYiD > div > a.link-GVbnGZ div.overlayForeground-qabjQ0 > div.actionsTop-v4lYiD > div > a.link-GVbnGZ
div.overlayForeground-qabjQ0 > div.actionsTop-v4lYiD > div > a.link-GVbnGZ div.overlayForeground-qabjQ0 > div.actionsTop-v4lYiD > div > a.link-GVbnGZ
Go to Microsoft Copilot's profile div.actionsBottom-BnTMN5 > div.userLinkContainer-ZWhFxH > span#base-ui-_r_56_ > a.link-dYuCfx
Go to Land O'Lakes, Inc.'s profile div.actionsBottom-BnTMN5 > div.userLinkContainer-ZWhFxH > span#base-ui-_r_5m_ > a.link-dYuCfx

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.

○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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Form elements have associated labels
●`[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
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
○`[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
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○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
○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.
○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.
○`<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.
○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.
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 DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
92

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
section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image1-nLl6fh section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image1-nLl6fh
section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image2-DDKbqx section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image2-DDKbqx
section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image3-FwtwiQ section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image3-FwtwiQ
section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image4-U_BHob section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image4-U_BHob
section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image5-f5xhoi section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image5-f5xhoi
section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image6-Z964gj section.innerContainer-rIi_AO > div.visuals-Ho5W4X > div.images-zRode0 > img.image6-Z964gj

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
●robots.txt is valid
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback