Lighthouse Mobile

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

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/auto-new.svg	864000.0 s	1.1 KiB
static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/toy.svg	864000.0 s	1002 B
static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/fashion.svg	864000.0 s	889 B
static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/furniture.svg	864000.0 s	841 B
static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/sport.svg	864000.0 s	802 B
static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/food.svg	864000.0 s	763 B
static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/auto-acc.svg	864000.0 s	723 B
static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/mobiles.svg	864000.0 s	722 B
static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/books.svg	864000.0 s	683 B
static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/beauty.svg	864000.0 s	653 B
static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/tv.svg	864000.0 s	650 B
static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/home-final.svg	864000.0 s	642 B
static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/all.svg	864000.0 s	630 B
static-assets-web.flixcart.com/apex-static/images/svgs/L1Nav/electronics.svg	864000.0 s	617 B

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
Image `a._3n8fna1co > div.OfydJ4 > picture > img`	rukminim2.flixcart.com/fk-p-flap/940/460/image/0180d1656664e410.png?q=60	37.9 KiB	19.0 KiB
Image `a._3n8fna1co > div.OfydJ4 > picture > img`	rukminim2.flixcart.com/fk-p-flap/940/460/image/f204396198572d43.png?q=60	34.4 KiB	17.2 KiB
Image `a._3n8fna1co > div.OfydJ4 > picture > img`	rukminim2.flixcart.com/fk-p-flap/940/460/image/843730c8248c0c71.png?q=60	32.1 KiB	16.0 KiB
Image `a._3n8fna1co > div.OfydJ4 > picture > img`	rukminim2.flixcart.com/fk-p-flap/940/460/image/660e7816971e8b27.png?q=60	31.5 KiB	15.7 KiB
Image `a._3n8fna1co > div.OfydJ4 > picture > img`	rukminim2.flixcart.com/fk-p-flap/940/460/image/3a317de9c04b51d2.png?q=60	31.5 KiB	15.7 KiB
Image `a._3n8fna1co > div.OfydJ4 > picture > img`	rukminim2.flixcart.com/fk-p-flap/940/460/image/b0fe37e069d3d88b.png?q=60	24.9 KiB	12.4 KiB
Image `div > div._3n8fna1co > div > img`	/image/280/374/xif0q/speaker/mobile-tablet-speaker/l/u/h/...	15.5 KiB	5.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	4.1 s	3.8 s	79 ms
www.flipkart.com/	2.4 s	596 ms	139 ms
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	1.5 s	240 ms	34 ms
Unattributable	846 ms	48 ms	0.0 ms
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	318 ms	4.6 ms	313 ms
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	295 ms	245 ms	32 ms
js-agent.newrelic.com/page_view_event-aggregate.06482edd-1.236.0.min.js	123 ms	106 ms	1.0 ms
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	87 ms	3.7 ms	83 ms
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	81 ms	7.2 ms	73 ms
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	61 ms	1.3 ms	59 ms

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	5.2 s
Other	2.3 s
Style & Layout	1.0 s
Script Parsing & Compilation	913 ms
Rendering	519 ms
Parse HTML & CSS	121 ms
Garbage Collection	88 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 25.2 KiB

URL	Transfer Size	Est Savings
.nc3hzK{background-color:#2874f0;color:#eaeaea;display:table;font-size:16px;height:52px; … } …	26.2 KiB	25.2 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 1.3 MiB

URL	Transfer Size	Est Savings
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	840.6 KiB	503.4 KiB
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	207.0 KiB	206.3 KiB
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	176.5 KiB	175.9 KiB
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	126.4 KiB	86.7 KiB
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	185.8 KiB	76.9 KiB
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	100.9 KiB	74.8 KiB
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	118.5 KiB	67.6 KiB
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	67.0 KiB	66.0 KiB
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	85.3 KiB	40.1 KiB
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	28.5 KiB	28.2 KiB
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	26.6 KiB	20.8 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	844.1 KiB
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	209.9 KiB
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	186.0 KiB
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	176.8 KiB
www.flipkart.com/	163.7 KiB
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	126.7 KiB
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	118.8 KiB
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	101.2 KiB
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	85.6 KiB
/batman-returns/batman-returns/p/329f3907cb96d278607b538c...	67.3 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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
2.rome.api.flipkart.com/2/notification/unreadCount?count=10&before=	`Failed to load resource: the server responded with a status of 401 (Unauthorized)`
sonic.fdp.api.flipkart.com/4/data/collector/business	`Failed to load resource: the server responded with a status of 406 ()`
sonic.fdp.api.flipkart.com/4/data/collector/business	`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.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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`