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

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
kashipixel.in/assets/index-DUO4ggvk.css	28.7 KiB	80 ms
/css2?family=Inter:wght@300;400;500;600;700&family=Playfa...	1.3 KiB	71 ms
/css2?family=Space+Grotesk:wght@300..700&family=Outfit:wg...	1.2 KiB	323 ms

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
KashiPixel Logo `header.h-16 > div.flex > div.w-8 > img.w-full`	i.ibb.co/NgRbH7dV/logo-icon.webp	54.1 KiB	54.1 KiB
KashiPixel Logo `header.h-16 > div.flex > div.w-8 > img.w-full`	i.ibb.co/NgRbH7dV/logo-icon.webp	54.1 KiB	54.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=format	40.3 KiB	25.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=format	25.4 KiB	11.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=format	20.1 KiB	8.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=format	21.6 KiB	8.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=format	16.0 KiB	7.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 KiB	5.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 KiB	5.1 KiB
div.bg-white > div.grid > div.h-10 > img.w-full `div.bg-white > div.grid > div.h-10 > img.w-full`	images.unsplash.com/photo-1501339847302-ac426a4a7cbb?w=120&q=60	5.7 KiB	4.8 KiB
div.bg-white > div.grid > div.h-10 > img.w-full `div.bg-white > div.grid > div.h-10 > img.w-full`	images.unsplash.com/photo-1555066931-4365d14bab8c?w=120&q=60	5.3 KiB	4.5 KiB
div.bg-white > div.grid > div.h-10 > img.w-full `div.bg-white > div.grid > div.h-10 > img.w-full`	images.unsplash.com/photo-1517838277536-f5f99be501cd?w=120&q=60	5.2 KiB	4.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: 220 ms 309.6 KiB

URL	Transfer Size	Est Savings
kashipixel.in/assets/index-DY6Q-9cC.js	213.1 KiB	163.2 KiB
www.googletagmanager.com/gtag/js?id=G-9J5YR38T5M	178.6 KiB	73.2 KiB
kashipixel.in/assets/vendor-supabase-qG2_WpoK.js	53.5 KiB	44.3 KiB
kashipixel.in/assets/vendor-react-efjOVRa5.js	84.4 KiB	29.0 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

URL	Transfer Size	Est Savings
kashipixel.in/assets/vendor-react-efjOVRa5.js	84.4 KiB	8.9 KiB

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

●Time to Interactive 1.7 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 70 ms

●Minify CSS

●Reduce unused CSS

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

●JavaScript execution time 0.3 s

●Minimizes main-thread work 0.8 s

●Avoid long main-thread tasks 4 long tasks found

●Avoid non-composited animations 3 animated elements found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 110 ms

●Server Backend Latencies 170 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 460 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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.

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.bg-white > div.grid > div.h-10 > img.w-full `div.bg-white > div.grid > div.h-10 > img.w-full`
div.bg-white > div.grid > div.h-10 > img.w-full `div.bg-white > div.grid > div.h-10 > img.w-full`
div.bg-white > div.grid > div.h-10 > img.w-full `div.bg-white > div.grid > div.h-10 > img.w-full`

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.

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

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

URL
kashipixel.in/assets/index-DY6Q-9cC.js

●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

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.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
1	`<!doctype html>`	`Syntax not understood`
2	`<html lang="en">`	`Syntax not understood`
3	`<head>`	`Syntax not understood`
4	`<meta charset="UTF-8" />`	`Syntax not understood`
5	`<meta name="viewport" content="width=device-width, initial-scale=1.0" />`	`Syntax not understood`
7	`<!-- Google tag (gtag.js) -->`	`Syntax not understood`
8	`<script async src="https://www.googletagmanager.com/gtag/js?id=G-9J5YR38T5M"></script>`	`Unknown directive`
9	`<script>`	`Syntax not understood`
10	`window.dataLayer = window.dataLayer \|\| [];`	`Syntax not understood`
11	`function gtag(){dataLayer.push(arguments);}`	`Syntax not understood`
12	`gtag('js', new Date());`	`Syntax not understood`
14	`gtag('config', 'G-9J5YR38T5M');`	`Syntax not understood`
15	`</script>`	`Syntax not understood`
17	`<!-- App Favicon & Icon -->`	`Syntax not understood`
18	`<link rel="icon" type="image/webp" href="https://i.ibb.co/NgRbH7dV/logo-icon.webp" />`	`Unknown directive`
19	`<link rel="shortcut icon" type="image/webp" href="https://i.ibb.co/NgRbH7dV/logo-icon.webp" />`	`Unknown directive`
20	`<link rel="apple-touch-icon" href="https://i.ibb.co/NgRbH7dV/logo-icon.webp" />`	`Unknown directive`
22	`<!-- Primary Meta Tags -->`	`Syntax not understood`
23	`<title>KashiPixel \| AI Website Builder & Premium Dev Studio</title>`	`Syntax not understood`
24	`<meta name="title" content="KashiPixel \| AI Website Builder & Premium Dev Studio" />`	`Syntax not understood`
25	`<meta name="description" content="KashiPixel is a professional-grade AI-powered website builder. Create, customize, and instantly publish high-converting portfolios, SaaS landings, and business storefronts." />`	`Syntax not understood`
26	`<meta name="keywords" content="kashipixel, website builder, ai website builder, instant web design, no-code portfolio, saas landing generator, website creator" />`	`Syntax not understood`
27	`<meta name="author" content="KashiPixel Dev" />`	`Syntax not understood`
28	`<link rel="canonical" href="https://kashipixel.in/" />`	`Unknown directive`
30	`<!-- Open Graph / Facebook -->`	`Syntax not understood`
31	`<meta property="og:type" content="website" />`	`Unknown directive`
32	`<meta property="og:url" content="https://kashipixel.in/" />`	`Unknown directive`
33	`<meta property="og:site_name" content="KashiPixel" />`	`Unknown directive`
34	`<meta property="og:title" content="KashiPixel \| AI Website Builder & Premium Dev Studio" />`	`Unknown directive`
35	`<meta property="og:description" content="KashiPixel is a professional-grade AI-powered website builder. Create, customize, and instantly publish high-converting portfolios, SaaS landings, and business storefronts." />`	`Unknown directive`
36	`<meta property="og:image" content="https://images.unsplash.com/photo-1460925895917-afdab827c52f?w=1200&q=80" />`	`Unknown directive`
38	`<!-- Twitter -->`	`Syntax not understood`
39	`<meta property="twitter:card" content="summary_large_image" />`	`Unknown directive`
40	`<meta property="twitter:url" content="https://kashipixel.in/" />`	`Unknown directive`
41	`<meta property="twitter:title" content="KashiPixel \| AI Website Builder & Premium Dev Studio" />`	`Unknown directive`
42	`<meta property="twitter:description" content="KashiPixel is a professional-grade AI-powered website builder. Create, customize, and instantly publish high-converting portfolios, SaaS landings, and business storefronts." />`	`Unknown directive`
43	`<meta property="twitter:image" content="https://images.unsplash.com/photo-1460925895917-afdab827c52f?w=1200&q=80" />`	`Unknown directive`
45	`<!-- Google Fonts Integration for Premium Typography -->`	`Syntax not understood`
46	`<link rel="preconnect" href="https://fonts.googleapis.com">`	`Unknown directive`
47	`<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>`	`Unknown directive`
48	`<link href="https://fonts.googleapis.com/css2?family=Space+Grotesk:wght@300..700&family=Outfit:wght@100..900&family=Playfair+Display:ital,wght@0,400..900;1,400..900&display=swap" rel="stylesheet" crossorigin="anonymous">`	`Unknown directive`
49	`<script type="module" crossorigin src="/assets/index-DY6Q-9cC.js"></script>`	`Syntax not understood`
50	`<link rel="modulepreload" crossorigin href="/assets/vendor-core-B3C4XOsV.js">`	`Syntax not understood`
51	`<link rel="modulepreload" crossorigin href="/assets/vendor-react-efjOVRa5.js">`	`Syntax not understood`
52	`<link rel="modulepreload" crossorigin href="/assets/vendor-supabase-qG2_WpoK.js">`	`Syntax not understood`
53	`<link rel="stylesheet" crossorigin href="/assets/index-DUO4ggvk.css">`	`Syntax not understood`
54	`</head>`	`Syntax not understood`
55	`<body>`	`Syntax not understood`
56	`<div id="root"></div>`	`Syntax not understood`
57	`</body>`	`Syntax not understood`
58	`</html>`	`Syntax not understood`

To appear in search results, crawlers need access to your app.

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
div.bg-white > div.grid > div.h-10 > img.w-full `div.bg-white > div.grid > div.h-10 > img.w-full`
div.bg-white > div.grid > div.h-10 > img.w-full `div.bg-white > div.grid > div.h-10 > img.w-full`
div.bg-white > div.grid > div.h-10 > img.w-full `div.bg-white > div.grid > div.h-10 > img.w-full`

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

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`