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.

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.

URL	Transfer Size	Duration
/css2?family=Inter+Tight:ital,wght@0,300;0,400;0,500;0,60...	1.7 KiB	323 ms
qevon.vercel.app/assets/index-B3oHjWmx.css	5.9 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.

	URL	Resource Size	Est Savings
Bingus home feed showing posts from nearby users `a.block > div.relative > div.relative > img.w-full`	qevon.vercel.app/work/bingus-feed.png	104.9 KiB	76.4 KiB
Grand Motel OS point of sale with an open cart and cash payment `a.block > div.relative > div.relative > img.w-full`	qevon.vercel.app/work/grandmotel-pos.webp	52.2 KiB	43.6 KiB
Model architecture: URL features feeding an LSTM and a 1D CNN in parallel, merg… `a.block > div.relative > div.relative > img.w-full`	qevon.vercel.app/work/phish-arch.webp	46.2 KiB	39.3 KiB
SentinelOps scan results showing a score of 93 out of 100, Grade A, with the ca… `a.block > div.relative > div.relative > img.w-full`	qevon.vercel.app/work/sentinelops-scan.webp	36.3 KiB	30.3 KiB

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

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: 0.0 ms 81.7 KiB

URL	Transfer Size	Est Savings
qevon.vercel.app/assets/react-vendor-CVwF7shJ.js	89.2 KiB	47.4 KiB
qevon.vercel.app/assets/index-BwntUfI_.js	70.2 KiB	34.3 KiB

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Time to Interactive 0.5 s

●Max Potential First Input Delay 30 ms

●Minify CSS

●Minify JavaScript

●Reduce unused CSS

●Avoids enormous network payloads Total size was 524 KiB

●JavaScript execution time 0.3 s

●Minimizes main-thread work 0.9 s

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 50 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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid long main-thread tasks

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

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
PROJECT DETAILS → `section.max-w-[1440px] > div > div.flex > a.text-sm`
01 `div.p-6 > div.flex > div > span.text-xs`
Software / Web / Operations `a.block > div.relative > div.p-6 > p.text-xs`
Point of sale, inventory and customers in one system — stock moves as orders do… `a.block > div.relative > div.p-6 > p.text-sm`
02 `div.p-6 > div.flex > div > span.text-xs`
Security / DevOps / Tooling `a.block > div.relative > div.p-6 > p.text-xs`
Point it at a repo. It runs 29 checks across 6 categories and scores production… `a.block > div.relative > div.p-6 > p.text-sm`
03 `div.p-6 > div.flex > div > span.text-xs`
Social / Mobile / Web `a.block > div.relative > div.p-6 > p.text-xs`
A location-based social platform — posts and connections anchored to real place… `a.block > div.relative > div.p-6 > p.text-sm`
04 `div.p-6 > div.flex > div > span.text-xs`
AI / ML / Security `a.block > div.relative > div.p-6 > p.text-xs`
A hybrid LSTM + CNN model that classifies URLs as phishing or legitimate from 9… `a.block > div.relative > div.p-6 > p.text-sm`
01 `div > a.flex > div.flex > span.text-xs`
Full-stack, systems, APIs `a.flex > div.flex > div > div.text-xs`
02 `div > a.flex > div.flex > span.text-xs`
Design, frontend, UX `a.flex > div.flex > div > div.text-xs`
03 `div > a.flex > div.flex > span.text-xs`
AWS, GCP, Kubernetes, CI/CD `a.flex > div.flex > div > div.text-xs`
04 `div > a.flex > div.flex > span.text-xs`
LLMs, pipelines, RAG `a.flex > div.flex > div > div.text-xs`
05 `div > a.flex > div.flex > span.text-xs`
DevSecOps, pen-testing, compliance `a.flex > div.flex > div > div.text-xs`
06 `div > a.flex > div.flex > span.text-xs`
Dashboards, BI, product analytics `a.flex > div.flex > div > div.text-xs`
07 `div > a.flex > div.flex > span.text-xs`
Migrations, rewrites, replatforming `a.flex > div.flex > div > div.text-xs`
EXPLORE ALL SERVICES → `div.max-w-[1440px] > div > div.mt-12 > a.inline-flex`
SentinelOps is our own production-readiness scanner. It runs 29 checks across s… `section.max-w-[1440px] > div > div.max-w-4xl > p.text-base`
SEE SENTINELOPS → `section.max-w-[1440px] > div > div.max-w-4xl > a.inline-flex`
LET'S BUILD `div.flex-shrink-0 > div > a.group > span`

These are opportunities to improve the legibility of your content.

○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

●Image elements have `[alt]` attributes

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

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

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

●Links have a discernible name

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●All heading elements contain content.

●Elements with visible text labels have matching accessible names.

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

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

○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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

○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

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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