Skip to content
https://kashipixel.in

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.

93

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

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
KashiPixel Logo header.h-16 > div.flex > div.w-8 > img.w-full
i.ibb.co/NgRbH7dV/logo-icon.webp54.1 KiB54.1 KiB
KashiPixel Logo header.h-16 > div.flex > div.w-8 > img.w-full
i.ibb.co/NgRbH7dV/logo-icon.webp54.1 KiB54.1 KiB
KashiPixel Logo header.h-16 > div.flex > div.w-8 > img.w-full
i.ibb.co/NgRbH7dV/logo-icon.webp54.1 KiB54.1 KiB
E-Commerce Boutique div.grid > div.bg-white > div.relative > img.w-full
images.unsplash.com/photo-1441986300917-64674bd600d8?w=600&q=80&auto=format40.3 KiB25.0 KiB
Artisan Café div.grid > div.bg-white > div.relative > img.w-full
images.unsplash.com/photo-1501339847302-ac426a4a7cbb?w=600&q=80&auto=format25.4 KiB11.3 KiB
Vanguard Consulting div.grid > div.bg-white > div.relative > img.w-full
images.unsplash.com/photo-1552664730-d307ca884978?w=600&q=80&auto=format20.1 KiB8.8 KiB
SaaS Startup Hub div.grid > div.bg-white > div.relative > img.w-full
images.unsplash.com/photo-1460925895917-afdab827c52f?w=600&q=80&auto=format21.6 KiB8.7 KiB
Wellness Clinic div.grid > div.bg-white > div.relative > img.w-full
images.unsplash.com/photo-1576091160399-112ba8d25d1d?w=600&q=80&auto=format16.0 KiB7.0 KiB
Priya Sharma div.grid > div.bg-white > div.flex > img.w-10
/photo-1494790108377-be9c29b29330?w=100&q=80&auto=format&...5.6 KiB5.3 KiB
Arjun Mehra div.grid > div.bg-white > div.flex > img.w-10
/photo-1507003211169-0a1dd7228f2d?w=100&q=80&auto=format&...5.4 KiB5.1 KiB
Modern cafe and coffee shop showcase preview div.bg-white > div.grid > div.h-10 > img.w-full
images.unsplash.com/photo-1501339847302-ac426a4a7cbb?w=120&q=605.7 KiB4.8 KiB
Technology and code editor workspace preview div.bg-white > div.grid > div.h-10 > img.w-full
images.unsplash.com/photo-1555066931-4365d14bab8c?w=120&q=605.3 KiB4.5 KiB
Fitness and wellness portfolio photo preview div.bg-white > div.grid > div.h-10 > img.w-full
images.unsplash.com/photo-1517838277536-f5f99be501cd?w=120&q=605.2 KiB4.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: 180 ms 309.3 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 8.9 KiB
URLTransfer SizeEst Savings
kashipixel.in/assets/vendor-react-YmsrcwtB.js84.4 KiB8.9 KiB

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

●Time to Interactive 1.6 s
●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
●Max Potential First Input Delay 50 ms
●Minify CSS
●Reduce unused CSS
●Avoids enormous network payloads Total size was 1,214 KiB
●JavaScript execution time 0.2 s
●Minimizes main-thread work 0.6 s
●Avoid long main-thread tasks 2 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 50 ms
●Server Backend Latencies 130 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 130 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
93

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
BUILDER 🚀 header.h-16 > div.flex > button.px-3 > span
START BUILDING FREE div.grid > div.lg:col-span-6 > div.flex > button.px-6
ACCENT COLOR div.flex > div.w-40 > div > p.text-[7px]
SEO SCORE div.flex > div.w-40 > div > p.text-[7px]
98% div > div.bg-emerald-50 > div.flex > span.text-[8px]
ACTIVE BLOCK div.flex > div.w-40 > div > p.text-[7px]
HERO div.w-40 > div > div.space-y-1 > div.px-2
FEATURES div.w-40 > div > div.space-y-1 > div.px-2
TESTIMONIALS div.w-40 > div > div.space-y-1 > div.px-2
CTA div.w-40 > div > div.space-y-1 > div.px-2
$4.50 div > div.space-y-1 > div.flex > span.font-mono
$3.75 div > div.space-y-1 > div.flex > span.font-mono
LIVE EDIT SYNC div.flex > div.flex-1 > div.bg-white > span.inline-flex
01 div.max-w-7xl > div.grid > div.bg-white > div.absolute
02 div.max-w-7xl > div.grid > div.bg-white > div.absolute
03 div.max-w-7xl > div.grid > div.bg-white > div.absolute
04 div.max-w-7xl > div.grid > div.bg-white > div.absolute
PROMPT INPUT div.grid > div.bg-white > div.bg-slate-50 > div.text-[7px]
• Gemini AI div.bg-white > div.bg-slate-50 > div.flex > span.text-[7px]
96/100 div.bg-white > div.bg-emerald-50 > div.flex > span.text-[11px]
LIVE div.bg-white > div.bg-sky-50 > div.flex > span.text-[8px]
Uptime 99.9% • Response 0.4s div.bg-white > div.bg-sky-50 > div.flex > span.text-[8px]
MOBILE div.bg-white > div.flex > div.flex > span.text-[8px]
USER STORIES section.bg-[#FAF9F6] > div.max-w-7xl > div.text-center > div.inline-flex
© 2026 KashiPixel Dev Studio. Founded by Gurudeep Verma. footer.bg-black > div.border-t > div.max-w-7xl > span
Privacy div.border-t > div.max-w-7xl > div.flex > button.hover:text-slate-300
Terms div.border-t > div.max-w-7xl > div.flex > button.hover:text-slate-300
Cookie Policy div.border-t > div.max-w-7xl > div.flex > button.hover:text-slate-300
Refund Policy div.border-t > div.max-w-7xl > div.flex > button.hover:text-slate-300
Powered by Neobrutalist Design Systems. footer.bg-black > div.border-t > div.max-w-7xl > span

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
BOUTIQUE CAFÉ div > div.h-16 > div.space-y-1 > h4.text-[8px]
E-COMMERCE BOUTIQUE div.bg-white > div.p-5 > div.space-y-1 > h4.font-black
QUICK LINKS footer.bg-black > div.max-w-7xl > div.space-y-5 > h4.font-black

These are opportunities to improve keyboard navigation in your application.

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
1 WHATSAPP US body > div#root > div.fixed > button.relative
○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
●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.
●Document has a main landmark.
○`[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.
○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

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

●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
●Mitigate DOM-based XSS with Trusted Types
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Ensure proper origin isolation with COOP
○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
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○robots.txt is valid

Send Feedback