Lighthouse Desktop

· 0 checks — Desktop 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.

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.

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:84.202 source:map[column:787 line:0 type:source-location url:https://plausible.io/js/script.tagged-events.js urlProvider:network]]]

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

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
GitHub code review by the Seer highlighting a potential bug: inconsistent error… `div.flex-grid-cell > div.justify-items-center > div.relative > img.tab-img-2`	sentry.io/_vercel/image?url=_astro%2Ftabs-b-3.DBuDJxCL.webp&w=640&q=100	64.7 KiB	48.7 KiB
Sentry trace waterfall view for an HTTP POST to /api/v1/buy-plants, showing AI-… `div.flex-grid-cell > div.justify-items-center > div.relative > img.tab-img-1`	sentry.io/_vercel/image?url=_astro%2Ftabs-a-2.BeO7Y7Ee.webp&w=640&q=100	60.4 KiB	45.4 KiB
Sentry issue detail page for a fatal read ETIMEDOUT error on a GET /api/project… `div.flex-grid-cell > div.justify-items-center > div.relative > img.tab-img-0`	sentry.io/_vercel/image?url=_astro%2Ftabs-b-1.CxQnCdrJ.webp&w=640&q=100	49.4 KiB	37.1 KiB
Sentry Session Replay showing a user session on empower-plant.com with clicks, … `div.flex-grid-cell > div.justify-items-center > div.relative > img.tab-img-0`	sentry.io/_vercel/image?url=_astro%2Ftabs-a-1.3EhRDHX9.webp&w=640&q=100	46.8 KiB	35.2 KiB
Code diff view showing new configurations added to prevent database timeout err… `div.flex-grid-cell > div.justify-items-center > div.relative > img.tab-img-1`	sentry.io/_vercel/image?url=_astro%2Ftabs-b-2.Bc7JV4Tp.webp&w=640&q=100	42.7 KiB	32.1 KiB
Sentry issue view showing an unhandled exception in src/main.py at line 279: “E… `div.flex-grid-cell > div.justify-items-center > div.relative > img.tab-img-2`	sentry.io/_vercel/image?url=_astro%2Ftabs-a-3.BH8DXd6a.webp&w=640&q=100	40.2 KiB	30.2 KiB
Illustration of a terminal-style window showing the command npm install @sentry… `div.flex > div.bg-gradient-to-r > div.rounded-[0.6625rem] > img.w-full`	sentry.io/_vercel/image?url=_astro%2Finstall-1-line.CStr0HQx.webp&w=828&q=100	26.8 KiB	15.7 KiB
div.container > div.animated-logo-grid-wrapper > div.ufo-container > img.ufo `div.container > div.animated-logo-grid-wrapper > div.ufo-container > img.ufo`	sentry.io/_astro/ufo-abduction-image.CCCweOzA.webp	11.6 KiB	10.8 KiB
Chat-style interface showing “Sentry agent connected” and a user named “codydea… `div.flex > div.bg-gradient-to-r > div.rounded-[0.6625rem] > img.w-full`	sentry.io/_vercel/image?url=_astro%2Fmcp-integration.BsYvoh98.webp&w=828&q=100	15.9 KiB	9.3 KiB
A section labeled “Root Cause” with code insight stating: “The code attempts to… `div.flex > div.bg-gradient-to-r > div.rounded-[0.6625rem] > img.w-full`	sentry.io/_vercel/image?url=_astro%2Fautomatic-rca.CGAenFBp.webp&w=828&q=100	15.4 KiB	9.0 KiB
Code snippet with a console warning message and a Sentry UI section showing a b… `div.flex > div.bg-gradient-to-r > div.rounded-[0.6625rem] > img.w-full`	sentry.io/_vercel/image?url=_astro%2Fai-code-review.zf1XFlmB.webp&w=828&q=100	12.3 KiB	7.2 KiB

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
sentry.io/_astro/_slug_.BMaqGsss.css	1.4 KiB
sentry.io/_astro/_slug_.utFj-uUR.css	25.2 KiB
sentry.io/_astro/_slug_.C88tuRea.css	4.4 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 19.5 KiB

URL	Transfer Size	Est Savings
sentry.io/_astro/_slug_.utFj-uUR.css	25.2 KiB	19.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 23.3 KiB

URL	Transfer Size	Est Savings
sentry.io/_astro/index.BSQljMam.js	47.9 KiB	23.3 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
Other	1.2 s
Script Evaluation	760 ms
Style & Layout	143 ms
Rendering	50 ms
Parse HTML & CSS	23 ms
Garbage Collection	16 ms
Script Parsing & Compilation	5.7 ms

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.container > div.animated-logo-grid-wrapper > div.ufo-container > img.ufo `div.container > div.animated-logo-grid-wrapper > div.ufo-container > img.ufo`	sentry.io/_astro/ufo-abduction-image.CCCweOzA.webp

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: 346 ms

URL	Time Spent
sentry.io/	346 ms
sentry.io/welcome/	0.0 ms

●Time to Interactive 1.4 s

●Max Potential First Input Delay 80 ms

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,923 KiB

●JavaScript execution time 0.8 s

●Avoid long main-thread tasks 1 long task found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 150 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 2 layout shifts found

○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

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
main#main-content > div.toggle-container > div.toggle-wrapper > div.toggle-track `main#main-content > div.toggle-container > div.toggle-wrapper > div.toggle-track`

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

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Next.js Angular Android iOS Flutter React Native .NET MAUI Python Node.js React… `div.getting-started-container > div.flex > div.select-wrapper > select#installation-dropdown-23`

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.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●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

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

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

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

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○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

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

○`<object>` elements have alternate text

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

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

○`[lang]` attributes have a valid value

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

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

○Uses ARIA roles only on compatible elements

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

○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

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
Left Installation Instructions Image Mobile `section.relative > div.container > div.getting-started-container > img.md:hidden`	sentry.io/_astro/getting-started-img-left.CRIbD4_5.webp	248 x 410 (0.60)	466 x 410 (1.14)

●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

●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 proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Ensure CSP is effective against XSS attacks

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

100

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.

○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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`