Skip to content
https://zomato.com

Lighthouse Mobile

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

58

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.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-VIDEO
nodeLabel: div.relative > div.relative > div.relative > video.object-cover
path: 1,HTML,1,BODY,3,DIV,0,ASTRO-ISLAND,38,DIV,0,DIV,0,DIV,0,DIV,1,VIDEO
selector: div.relative > div.relative > div.relative > video.object-cover
snippet: <video src="https://b.zmtcdn.com/data/file_assets/2627bbed9d6c068e50d2aadcca11ddbb1743…" class="object-cover transition-opacity duration-400 overflow-clip pointer-events-…" autoplay="" loop="" playsinline="" loading="lazy" style="overflow-clip-margin: content-box;">

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
value: no origins were preconnected
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.

URLTransfer SizeDuration
www.zomato.com/z-homepage/_astro/index.BVDT1VkZ.css12.5 KiB150 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.

URLResource SizeEst Savings
eternal logo div.rounded-t-3xl > div.flex > div.mt-4 > img.h-auto
b.zmtcdn.com/data/o2_assets/e6b11be581b91b410684fa16287f565c1738647242.png91.3 KiB65.8 KiB
eternal logo div.sticky > div.flex > div.flex > img.aspect-[112/28]
b.zmtcdn.com/data/o2_assets/45f24a780ec544a02267ccd0da16ce231767592736.png11.2 KiB11.2 KiB
div.w-full > div.flex > div.w-full > img div.w-full > div.flex > div.w-full > img
b.zmtcdn.com/data/o2_assets/6e27c9acde6045c272a28e6eb275727e1742455789.png6.7 KiB6.4 KiB
div.w-full > div.flex > div.w-full > img div.w-full > div.flex > div.w-full > img
b.zmtcdn.com/data/o2_assets/5e7aab0f183b36fc12c29279f0cb55181742462245.png5.4 KiB5.1 KiB
Zomato logo div.relative > div.relative > div.relative > img.object-cover
b.zmtcdn.com/web_assets/8313a97515fcb0447d2d77c276532a511583262271.png5.6 KiB5.1 KiB
div.w-full > div.flex > div.w-full > img div.w-full > div.flex > div.w-full > img
b.zmtcdn.com/data/o2_assets/d0f1639403f80f8f2c19e0d538222e661742455804.png4.8 KiB4.6 KiB
App Download Logo div.flex > a.z-50 > div.w-auto > img.h-12
b.zmtcdn.com/data/o2_assets/df6464de32f4a09262cee301f65aaa661739351256.png4.6 KiB4.0 KiB

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.2 s
URLTime Spent
zomato.com/1.2 s
www.zomato.com/0.0 ms

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

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: 300 ms 88.3 KiB

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.

CategoryTime Spent
Other2.5 s
Script Evaluation1.5 s
Style & Layout661 ms
Rendering218 ms
Garbage Collection98 ms
Parse HTML & CSS57 ms
Script Parsing & Compilation9.9 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 reasonFailure type
The page has an unload handler in the main frame.Actionable
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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
eternal logo div.rounded-t-3xl > div.flex > div.mt-4 > img.h-auto
b.zmtcdn.com/data/o2_assets/e6b11be581b91b410684fa16287f565c1738647242.png
div.w-full > div.flex > div.w-full > img div.w-full > div.flex > div.w-full > img
b.zmtcdn.com/data/o2_assets/82f145180cd6f920a8a8617dda366a0a1742455963.png
div.w-full > div.flex > div.w-full > img div.w-full > div.flex > div.w-full > img
b.zmtcdn.com/data/o2_assets/d0f1639403f80f8f2c19e0d538222e661742455804.png
div.w-full > div.flex > div.w-full > img div.w-full > div.flex > div.w-full > img
b.zmtcdn.com/data/o2_assets/5e973dd10c387878009c66d625ae541a1746550690.png
div.w-full > div.flex > div.w-full > img div.w-full > div.flex > div.w-full > img
b.zmtcdn.com/data/o2_assets/cc1caf220c91be38dd94cce12b416fcd1746550226.png
div.w-full > div.flex > div.w-full > img div.w-full > div.flex > div.w-full > img
b.zmtcdn.com/data/o2_assets/5e7aab0f183b36fc12c29279f0cb55181742462245.png
div.w-full > div.flex > div.w-full > img div.w-full > div.flex > div.w-full > img
b.zmtcdn.com/data/o2_assets/813952c961fd13588cb71867d84ea7dc1742455815.png
div.w-full > div.flex > div.w-full > img div.w-full > div.flex > div.w-full > img
b.zmtcdn.com/data/o2_assets/06d090307e02772693ac06123b53459b1742455939.png
div.w-full > div.flex > div.w-full > img div.w-full > div.flex > div.w-full > img
b.zmtcdn.com/data/o2_assets/6e27c9acde6045c272a28e6eb275727e1742455789.png
div.w-full > div.flex > div.w-full > img div.w-full > div.flex > div.w-full > img
b.zmtcdn.com/data/o2_assets/867f86a10503998e437963bb37c451591742455764.png
App Download Logo div.mb-10 > a.z-50 > div.w-auto > img.h-12
b.zmtcdn.com/data/o2_assets/aad864bd17860b27634fe621001c32db1739350431.png
App Download Logo div.flex > a.z-50 > div.w-auto > img.h-12
b.zmtcdn.com/data/o2_assets/aad864bd17860b27634fe621001c32db1739350431.png
Zomato Logo div.relative > footer.px-5 > div.flex > img.h-8
b.zmtcdn.com/web_assets/8313a97515fcb0447d2d77c276532a511583262271.png
App Download Logo div.mb-10 > a.z-50 > div.w-auto > img.h-12
b.zmtcdn.com/data/o2_assets/df6464de32f4a09262cee301f65aaa661739351256.png
App Download Logo div.flex > a.z-50 > div.w-auto > img.h-12
b.zmtcdn.com/data/o2_assets/df6464de32f4a09262cee301f65aaa661739351256.png
div.w-full > div.flex > div.justify-self-center > img.max-h-10 div.w-full > div.flex > div.justify-self-center > img.max-h-10
b.zmtcdn.com/data/o2_assets/713443cc5944ce4284d7e49e75e2aacf1742466222.png
div.w-full > div.flex > div.justify-self-center > img.max-h-10 div.w-full > div.flex > div.justify-self-center > img.max-h-10
b.zmtcdn.com/data/o2_assets/d19ec60986487a77bcb026e5efc3325f1742908200.png
div.w-full > div.flex > div.justify-self-center > img.max-h-10 div.w-full > div.flex > div.justify-self-center > img.max-h-10
b.zmtcdn.com/data/o2_assets/e7533c4081d6140da37b9f430cb7b8051743006192.png

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

●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●JavaScript execution time 1.2 s
●Avoid long main-thread tasks 16 long tasks found
●Avoid non-composited animations 6 animated elements found
●Network Requests
●Network Round Trip Times 150 ms
●Server Backend Latencies 160 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 220 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○User Timing marks and measures
74

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.

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
Eternal div.py-6 > div.grid > div.order-1 > h4.mb-[10px]

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.fixed > div.sticky > div.flex > img.size-10 div.fixed > div.sticky > div.flex > img.size-10
astro-island > div.sticky > div.relative > img.absolute astro-island > div.sticky > div.relative > img.absolute
astro-island > div.sticky > div.relative > img.absolute astro-island > div.sticky > div.relative > img.absolute
astro-island > div.sticky > div.relative > img.absolute astro-island > div.sticky > div.relative > img.absolute
astro-island > div.sticky > div.relative > img.absolute astro-island > div.sticky > div.relative > img.absolute
astro-island > div.sticky > div.relative > img.absolute astro-island > div.sticky > div.relative > img.absolute
astro-island > div.sticky > div.relative > img.absolute astro-island > div.sticky > div.relative > img.absolute
div.w-full > div.flex > div.justify-self-center > img.max-h-10 div.w-full > div.flex > div.justify-self-center > img.max-h-10
div.w-full > div.flex > div.justify-self-center > img.max-h-10 div.w-full > div.flex > div.justify-self-center > img.max-h-10
div.w-full > div.flex > div.justify-self-center > img.max-h-10 div.w-full > div.flex > div.justify-self-center > img.max-h-10
astro-island > div.sticky > div.relative > img.absolute astro-island > div.sticky > div.relative > img.absolute
astro-island > div.sticky > div.relative > img.absolute astro-island > div.sticky > div.relative > img.absolute
astro-island > div.sticky > div.relative > img.absolute astro-island > div.sticky > div.relative > img.absolute
div.relative > div.mt-10 > div.flex > img div.relative > div.mt-10 > div.flex > img
div.relative > div.mt-10 > div.flex > img div.relative > div.mt-10 > div.flex > img

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.grid > div.order-3 > div.inline-flex > a div.grid > div.order-3 > div.inline-flex > a
div.grid > div.order-3 > div.inline-flex > a div.grid > div.order-3 > div.inline-flex > a
div.grid > div.order-3 > div.inline-flex > a div.grid > div.order-3 > div.inline-flex > a
div.grid > div.order-3 > div.inline-flex > a div.grid > div.order-3 > div.inline-flex > a
div.grid > div.order-3 > div.inline-flex > a div.grid > div.order-3 > div.inline-flex > a

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

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 html

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-hidden="true"]` is not present on the document `<body>`
●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.
●Background and foreground colors have a sufficient contrast ratio
●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.
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○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
○Elements use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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
○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.
77

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
astro-island > div.sticky > div.relative > img.absolute astro-island > div.sticky > div.relative > img.absolute
b.zmtcdn.com/data/o2_assets/3d1b3a891e2c59fd5ae7654dd207370b1739514134.png122 x 100 (1.22)1352 x 1192 (1.13)
astro-island > div.sticky > div.relative > img.absolute astro-island > div.sticky > div.relative > img.absolute
b.zmtcdn.com/data/o2_assets/364f85b5586700f0a3f7108cedf543011739962117.png90 x 90 (1.00)286 x 295 (0.97)

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.
●Uses HTTPS
●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
●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
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Detected JavaScript libraries
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

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.

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.fixed > div.sticky > div.flex > img.size-10 div.fixed > div.sticky > div.flex > img.size-10
astro-island > div.sticky > div.relative > img.absolute astro-island > div.sticky > div.relative > img.absolute
astro-island > div.sticky > div.relative > img.absolute astro-island > div.sticky > div.relative > img.absolute
astro-island > div.sticky > div.relative > img.absolute astro-island > div.sticky > div.relative > img.absolute
astro-island > div.sticky > div.relative > img.absolute astro-island > div.sticky > div.relative > img.absolute
astro-island > div.sticky > div.relative > img.absolute astro-island > div.sticky > div.relative > img.absolute
astro-island > div.sticky > div.relative > img.absolute astro-island > div.sticky > div.relative > img.absolute
div.w-full > div.flex > div.justify-self-center > img.max-h-10 div.w-full > div.flex > div.justify-self-center > img.max-h-10
div.w-full > div.flex > div.justify-self-center > img.max-h-10 div.w-full > div.flex > div.justify-self-center > img.max-h-10
div.w-full > div.flex > div.justify-self-center > img.max-h-10 div.w-full > div.flex > div.justify-self-center > img.max-h-10
astro-island > div.sticky > div.relative > img.absolute astro-island > div.sticky > div.relative > img.absolute
astro-island > div.sticky > div.relative > img.absolute astro-island > div.sticky > div.relative > img.absolute
astro-island > div.sticky > div.relative > img.absolute astro-island > div.sticky > div.relative > img.absolute
div.relative > div.mt-10 > div.flex > img div.relative > div.mt-10 > div.flex > img
div.relative > div.mt-10 > div.flex > img div.relative > div.mt-10 > div.flex > 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
●Links are crawlable
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback