Skip to content
Audit Complete

Results for https://www.flipkart.com

Visit site
Spain Spain · Madrid Completed: Apr 12, 2026 14:09 UTC

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
D68

Site Health

Score: 68 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

1

Content-Security-Policy header is missing

Security › Security Headers
2

HSTS header is missing

Security › Security Headers
3

No Content-Security-Policy header found

Security › Content Security Policy
4

1 button(s) with no accessible text

Accessibility › Link & Button Quality
5

14 image(s) missing alt attribute

Accessibility › Alt Text Quality
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.flipkart.com)](https://beavercheck.com/results/8563b959-d227-4e4f-ac60-ca088912c2d2)
<a href="https://beavercheck.com/results/8563b959-d227-4e4f-ac60-ca088912c2d2"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.flipkart.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.flipkart.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

54
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
77
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

2.29 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

3.47 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

2.08 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

6.95 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

19.33 s

Detailed Report

Audit breakdown by category with detailed findings.

54

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

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.

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

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
Image a._3n8fna1co > div.OfydJ4 > picture > img
rukminim2.flixcart.com/fk-p-flap/940/460/image/0180d1656664e410.png?q=6037.9 KiB19.0 KiB
Image a._3n8fna1co > div.OfydJ4 > picture > img
rukminim2.flixcart.com/fk-p-flap/940/460/image/f204396198572d43.png?q=6034.4 KiB17.2 KiB
Image a._3n8fna1co > div.OfydJ4 > picture > img
rukminim2.flixcart.com/fk-p-flap/940/460/image/843730c8248c0c71.png?q=6032.1 KiB16.0 KiB
Image a._3n8fna1co > div.OfydJ4 > picture > img
rukminim2.flixcart.com/fk-p-flap/940/460/image/660e7816971e8b27.png?q=6031.5 KiB15.7 KiB
Image a._3n8fna1co > div.OfydJ4 > picture > img
rukminim2.flixcart.com/fk-p-flap/940/460/image/3a317de9c04b51d2.png?q=6031.5 KiB15.7 KiB
Image a._3n8fna1co > div.OfydJ4 > picture > img
rukminim2.flixcart.com/fk-p-flap/940/460/image/b0fe37e069d3d88b.png?q=6024.9 KiB12.4 KiB
Image div > div._3n8fna1co > div > img
/image/280/374/xif0q/speaker/mobile-tablet-speaker/l/u/h/...15.5 KiB5.4 KiB

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

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

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.

Diagnostics

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

CategoryTime Spent
Script Evaluation5.2 s
Other2.3 s
Style & Layout1.0 s
Script Parsing & Compilation913 ms
Rendering519 ms
Parse HTML & CSS121 ms
Garbage Collection88 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

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.

Estimated savings: 0.0 ms 25.2 KiB

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

Layout shift culprits
Document request latency
Optimize DOM size
Font display
Forced reflow
LCP breakdown
LCP request discovery
Modern HTTP
Render blocking requests
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 3 user timings
Avoid long main-thread tasks 16 long tasks found
Avoid non-composited animations 13 animated elements found
Image elements have explicit `width` and `height`
Network Requests
Network Round Trip Times 170 ms
Server Backend Latencies 370 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 240 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
77

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.

Failing Elements
Hang on, loading content div.FWmYMm > div.css-g5y9jx > div.css-g5y9jx > div.css-146c3p1

These are opportunities to improve the legibility of your content.

Names and labels

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.

Failing Elements
div._3n8fna1co > div._3n8fna1co > div._3n8fna1co > a._3n8fna1co div._3n8fna1co > div._3n8fna1co > div._3n8fna1co > a._3n8fna1co

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Failing Elements
head > meta head > meta

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Failing Elements
html.useInterFont html.useInterFont

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>`
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Image elements have `[alt]` attributes
ARIA attributes are used as specified for the element's role
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
Touch targets have sufficient size and spacing.
The page contains a heading, skip link, or landmark region
Identical links have the same purpose.
`[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-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 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
Buttons have an accessible name
`<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
Heading elements appear in a sequentially-descending order
`<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.
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.
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.
96

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

SourceDescription
Failed to load resource: the server responded with a status of 401 (Unauthorized)
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()

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.

URLMap URL
www.flipkart.com/
/batman-returns/batman-returns/p/329f3907cb96d278607b538c.../batman-returns/batman-returns/p/329f3907cb96d278607b538c...
/batman-returns/batman-returns/p/329f3907cb96d278607b538c.../batman-returns/batman-returns/p/329f3907cb96d278607b538c...
/batman-returns/batman-returns/p/329f3907cb96d278607b538c.../batman-returns/batman-returns/p/329f3907cb96d278607b538c...
/batman-returns/batman-returns/p/329f3907cb96d278607b538c.../batman-returns/batman-returns/p/329f3907cb96d278607b538c...
/batman-returns/batman-returns/p/329f3907cb96d278607b538c.../batman-returns/batman-returns/p/329f3907cb96d278607b538c...
/batman-returns/batman-returns/p/329f3907cb96d278607b538c.../batman-returns/batman-returns/p/329f3907cb96d278607b538c...
/batman-returns/batman-returns/p/329f3907cb96d278607b538c.../batman-returns/batman-returns/p/329f3907cb96d278607b538c...
/batman-returns/batman-returns/p/329f3907cb96d278607b538c.../batman-returns/batman-returns/p/329f3907cb96d278607b538c...
/batman-returns/batman-returns/p/329f3907cb96d278607b538c.../batman-returns/batman-returns/p/329f3907cb96d278607b538c...
/batman-returns/batman-returns/p/329f3907cb96d278607b538c.../batman-returns/batman-returns/p/329f3907cb96d278607b538c...
/batman-returns/batman-returns/p/329f3907cb96d278607b538c.../batman-returns/batman-returns/p/329f3907cb96d278607b538c...
/batman-returns/batman-returns/p/329f3907cb96d278607b538c.../batman-returns/batman-returns/p/329f3907cb96d278607b538c...
/batman-returns/batman-returns/p/329f3907cb96d278607b538c.../batman-returns/batman-returns/p/329f3907cb96d278607b538c...
/batman-returns/batman-returns/p/329f3907cb96d278607b538c.../batman-returns/batman-returns/p/329f3907cb96d278607b538c...
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 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 clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Uncrawlable Link
Location not set Select delivery location div > div > div._3n8fna1co > a._3n8fna1co

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

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
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

68
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
72
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
85
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.71 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.08 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

256 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.86 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

5.10 s

Detailed Report

Audit breakdown by category with detailed findings.

68

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

URLResource SizeEst Savings
Image a._3n8fna1co > div.OfydJ4 > picture > img
rukminim2.flixcart.com/fk-p-flap/1600/780/image/843730c8248c0c71.png?q=8078.6 KiB72.1 KiB
Image a._3n8fna1co > div.OfydJ4 > picture > img
rukminim2.flixcart.com/fk-p-flap/1600/780/image/7928dacc24aeb43d.png?q=8073.6 KiB67.5 KiB
Image a._3n8fna1co > div.OfydJ4 > picture > img
rukminim2.flixcart.com/fk-p-flap/1600/780/image/af57a526ace6ca05.png?q=8072.9 KiB66.9 KiB
Image a._3n8fna1co > div.OfydJ4 > picture > img
rukminim2.flixcart.com/fk-p-flap/1600/780/image/9ff70b533dd9b141.png?q=8069.4 KiB63.7 KiB
Image a._3n8fna1co > div.OfydJ4 > picture > img
rukminim2.flixcart.com/fk-p-flap/1600/780/image/68b8b9421f98663b.png?q=8069.2 KiB63.5 KiB
Image a._3n8fna1co > div.OfydJ4 > picture > img
rukminim2.flixcart.com/fk-p-flap/1600/780/image/59cec455ce643865.png?q=8061.7 KiB56.6 KiB
Image a._3n8fna1co > div.OfydJ4 > picture > img
rukminim2.flixcart.com/fk-p-flap/1600/780/image/622a7341b215132e.jpg?q=8055.2 KiB50.3 KiB
Image a._3n8fna1co > div.OfydJ4 > picture > img
rukminim2.flixcart.com/fk-p-flap/1600/780/image/b7f4f4e26225eb41.png?q=8044.4 KiB40.7 KiB
Image a._3n8fna1co > div.OfydJ4 > picture > img
rukminim2.flixcart.com/fk-p-flap/380/510/image/ae1dcf18c214fcda.png?q=8024.0 KiB16.7 KiB
Image a._3n8fna1co > div.OfydJ4 > picture > img
rukminim2.flixcart.com/fk-p-flap/380/510/image/5498b97bddc132ea.png?q=8022.7 KiB15.8 KiB
Image a._3n8fna1co > div.OfydJ4 > picture > img
rukminim2.flixcart.com/fk-p-flap/380/510/image/1a89bc2270a0a87f.png?q=8018.9 KiB13.2 KiB
Image a._3n8fna1co > div.OfydJ4 > picture > img
rukminim2.flixcart.com/fk-p-flap/380/510/image/d9e766e40fd0d655.png?q=8018.3 KiB12.7 KiB
Image a._3n8fna1co > div.OfydJ4 > picture > img
rukminim2.flixcart.com/fk-p-flap/380/510/image/9ea747499a8ab07b.png?q=8017.5 KiB12.2 KiB
Image div > div._3n8fna1co > div > img
/fk-p-image/140/187/cf-ce-calvin-prod6/e9b81121916dc77717...7.4 KiB4.2 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-14-IMG
nodeLabel: Image
path: 1,HTML,1,BODY,0,DIV,19,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,2,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,PICTURE,2,IMG
selector: div._3n8fna1co > div.OfydJ4 > picture > img
snippet: <img src="https://rukminim2.flixcart.com/www/1600/530/promos/07/04/2026/8cb5542b-944…" alt="Image" class="" style="filter: none; opacity: 1;" aria-busy="false" data-highres-loaded="false" loading="lazy" srcset="https://rukminim2.flixcart.com/www/480/160/promos/07/04/2026/8cb5542b-9448…" fetchpriority="auto">

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.

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.

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

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

TTI

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.

Diagnostics

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

CategoryTime Spent
Script Evaluation985 ms
Other571 ms
Script Parsing & Compilation283 ms
Style & Layout242 ms
Rendering121 ms
Parse HTML & CSS71 ms
Garbage Collection23 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable

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.

Estimated savings: 0.0 ms 27.6 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

URL
Payment methods div.VND23C > div > div.EGBsCF > img
/batman-returns/batman-returns/p/images/payment-method-69...

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

Layout shift culprits
Document request latency
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 3 user timings
JavaScript execution time 1.1 s
Avoid long main-thread tasks 5 long tasks found
Avoid non-composited animations 10 animated elements found
Network Requests
Network Round Trip Times 180 ms
Server Backend Latencies 360 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 280 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
72

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.

Failing Elements
By continuing, you agree to Flipkart's Terms of Use and Privacy Policy. div.oTmHSp > div > form > div._dH7Ng
Terms of Use div > form > div._dH7Ng > a.PJ7HGt
Privacy Policy div > form > div._dH7Ng > a.PJ7HGt
Request OTP div > form > div.UgcHCN > button.WHahJn
New to Flipkart? Create an account div > form > div.l__hPu > a.FWBvOe

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Failing Elements
Terms of Use div > form > div._dH7Ng > a.PJ7HGt
Privacy Policy div > form > div._dH7Ng > a.PJ7HGt

These are opportunities to improve the legibility of your content.

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.

Failing Elements
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Failing Elements
div > form > div.sGuo7w > input.xkp9Hl div > form > div.sGuo7w > input.xkp9Hl

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.

Failing Elements
div._3n8fna1co > div._3n8fna1co > div._3n8fna1co > a._3n8fna1co div._3n8fna1co > div._3n8fna1co > div._3n8fna1co > a._3n8fna1co
div._3n8fna1co > div._3n8fna1co > div._3n8fna1co > a._3n8fna1co div._3n8fna1co > div._3n8fna1co > div._3n8fna1co > a._3n8fna1co
div._3n8fna1co > div._3n8fna1co > div._3n8fna1co > a._3n8fna1co div._3n8fna1co > div._3n8fna1co > div._3n8fna1co > a._3n8fna1co

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

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.

Failing Elements
Login div.CXZSEo > div.LhEIN3 > div.wszdrO > a.K05FV0
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
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
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
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
`[accesskey]` values are unique
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
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
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.
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.
`[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
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.
96

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

SourceDescription
Access to fetch at 'https://static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/all.svg' from origin 'https://www.flipkart.com' has been blocked by CORS policy: Request header field x-user-agent is not allowed by Access-Control-Allow-Headers in preflight response.
Access to fetch at 'https://static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/auto-acc.svg' from origin 'https://www.flipkart.com' has been blocked by CORS policy: Request header field x-user-agent is not allowed by Access-Control-Allow-Headers in preflight response.
Access to fetch at 'https://static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/auto-new.svg' from origin 'https://www.flipkart.com' has been blocked by CORS policy: Request header field x-user-agent is not allowed by Access-Control-Allow-Headers in preflight response.
Access to fetch at 'https://static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/beauty.svg' from origin 'https://www.flipkart.com' has been blocked by CORS policy: Request header field x-user-agent is not allowed by Access-Control-Allow-Headers in preflight response.
Access to fetch at 'https://static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/books.svg' from origin 'https://www.flipkart.com' has been blocked by CORS policy: Request header field x-user-agent is not allowed by Access-Control-Allow-Headers in preflight response.
Access to fetch at 'https://static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/electronics.svg' from origin 'https://www.flipkart.com' has been blocked by CORS policy: Request header field x-user-agent is not allowed by Access-Control-Allow-Headers in preflight response.
Access to fetch at 'https://static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/fashion.svg' from origin 'https://www.flipkart.com' has been blocked by CORS policy: Request header field x-user-agent is not allowed by Access-Control-Allow-Headers in preflight response.
Access to fetch at 'https://static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/food.svg' from origin 'https://www.flipkart.com' has been blocked by CORS policy: Request header field x-user-agent is not allowed by Access-Control-Allow-Headers in preflight response.
Access to fetch at 'https://static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/furniture.svg' from origin 'https://www.flipkart.com' has been blocked by CORS policy: Request header field x-user-agent is not allowed by Access-Control-Allow-Headers in preflight response.
Access to fetch at 'https://static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/home-final.svg' from origin 'https://www.flipkart.com' has been blocked by CORS policy: Request header field x-user-agent is not allowed by Access-Control-Allow-Headers in preflight response.
Access to fetch at 'https://static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/mobiles.svg' from origin 'https://www.flipkart.com' has been blocked by CORS policy: Request header field x-user-agent is not allowed by Access-Control-Allow-Headers in preflight response.
Access to fetch at 'https://static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/sport.svg' from origin 'https://www.flipkart.com' has been blocked by CORS policy: Request header field x-user-agent is not allowed by Access-Control-Allow-Headers in preflight response.
Access to fetch at 'https://static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/toy.svg' from origin 'https://www.flipkart.com' has been blocked by CORS policy: Request header field x-user-agent is not allowed by Access-Control-Allow-Headers in preflight response.
Access to fetch at 'https://static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/tv.svg' from origin 'https://www.flipkart.com' has been blocked by CORS policy: Request header field x-user-agent is not allowed by Access-Control-Allow-Headers in preflight response.
Access to fetch at 'https://static-assets-web.flixcart.com/www/linchpin/batman-returns/codes.json' from origin 'https://www.flipkart.com' has been blocked by CORS policy: Request header field x-user-agent is not allowed by Access-Control-Allow-Headers in preflight response.
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Failed to load resource: the server responded with a status of 406 ()
Failed to load resource: the server responded with a status of 406 ()
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 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 clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
85

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

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Uncrawlable Link
Location not set Select delivery location div > div > div._3n8fna1co > a._3n8fna1co

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.

Failing Elements
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img
div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img div.css-g5y9jx > div.css-g5y9jx > div.css-g5y9jx > img

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

Send Feedback