Beta Mobile Page Speed

12/6/22, 12:53 PM about:blank
https://beta-m.hometown.in/
48 87 67 89
Performance Accessibility Best SEO PWA

Practices
There were issues affecting this run of Lighthouse:
There may be stored data affecting loading performance in this location: IndexedDB. Audit this
page in an incognito window to prevent those resources from affecting your scores.
48
Performance
Values are estimated and may vary. The performance score
is calculated directly from these metrics. See calculator.
0–49 50–89 90–100
METRICS Expand view
First Contentful Paint Time to Interactive
1.5 s 17.5 s
Speed Index Total Blocking Time
8.6 s 3,200 ms
Largest Contentful Paint Cumulative Layout Shift
2.8 s 0.059
View Original Trace View Treemap
Show audits relevant to: All FCP TBT LCP CLS

about:blank 1/39
Show audits relevant to: All FCP TBT LCP CLS
OPPORTUNITIES
Opportunity Estimated Savings
Reduce unused JavaScript 2.67 s
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network
activity. Learn more. LCP
If you are not server-side rendering, split your JavaScript bundles with `React.lazy()`. Otherwise, code-split using a
third-party library such as loadable-components.
Show 3rd-party resources (7)
Transfer Potential
URL
Size Savings
…1.6.106/main-3bc9dfa….js (beta-m.hometown.in) 348.1 KiB 165.8 KiB
/stage-hometown808…_search_mobile.js (sandbox.unbxd.io) 78.2 KiB 50.8 KiB
/stage-hometown808…_autosuggest_mobile.js (sandbox.unbxd.io) 60.9 KiB 45.6 KiB
/js/webengage-min-v-6.0.js (widgets.in.webengage.com) 60.0 KiB 37.7 KiB
…47.0/deployment.js (c.la1-c1-hnd.salesforceliveagent.com) 42.1 KiB 29.2 KiB
/gtm.js?id=GTM-T5VV7MZ (www.googletagmanager.com) 95.7 KiB 28.8 KiB
/gtag/js?id=AW-845… (www.googletagmanager.com) 65.4 KiB 28.1 KiB
…1.6.106/Home-0186ce3….chunk.js (beta-m.hometown.in) 49.0 KiB 23.1 KiB
/gtag/js?id=DC-12399743 (www.googletagmanager.com) 43.1 KiB 22.9 KiB
Serve images in next-gen formats 1.2 s
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads
and less data consumption. Learn more.
Resource Potential
URL
Size Savings
…icons/mobile-offline-banner12.jpg?blur=30 (www.hometown.in) 83.2 KiB 40.0 KiB
…icons/mobile-online-banner.jpg?blur=30 (www.hometown.in) 77.4 KiB 37.2 KiB
about:blank 2/39
Resource Potential
URL
Size Savings
…icons/mob-mid-banner-strip-banner.jpg?blur=30 (www.hometown.in) 20.5 KiB 10.4 KiB
Eliminate render-blocking resources 0.36 s
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical
JS/styles. Learn more. FCP LCP
Transfer Potential
URL
Size Savings
…1.6.106/main-3bc9dfa….css (beta-m.hometown.in) 53.8 KiB 450 ms
Use HTTP/2 0.3 s
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more.
URL Protocol
…5.0/esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) http/1.1
…utils/common.min.js (praxisretail--produat.sandbox.my.salesforce.com) http/1.1
…5.0/esw.min.css (praxisretail--produat.sandbox.my.salesforce.com) http/1.1
…client/liveagent.esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) http/1.1
…5.0/esw.html?parent=https://beta-m.hometown.in/ (praxisretail--produat.sandbox.my.salesforce.com) http/1.1
…5.0/eswFrame.min.js (praxisretail--produat.sandbox.my.salesforce.com) http/1.1
…frame/session.esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) http/1.1
…frame/broadcast.esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) http/1.1
…frame/chasitor.esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) http/1.1
…frame/filetransfer.esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) http/1.1
…client/invite.esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) http/1.1
about:blank 3/39
URL Protocol
…utils/inert.min.js (praxisretail--produat.sandbox.my.salesforce.com) http/1.1
Reduce unused CSS 0.15 s
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by
network activity. Learn more. FCP LCP
Transfer Potential
URL
Size Savings
…1.6.106/main-3bc9dfa….css (beta-m.hometown.in) 53.8 KiB 49.5 KiB
These suggestions can help your page load faster. They don't directly affect the Performance score.
DIAGNOSTICS
Avoid enormous network payloads — Total size was 26,657 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more. LCP
Transfer
URL
Size
…1.6.106/cec195a….png?_sw-precache=cec195a… (beta-m.hometown.in) 3,101.5 KiB
…1.6.106/606b818….png?_sw-precache=606b818… (beta-m.hometown.in) 2,311.9 KiB
…1.6.106/2b73458….jpg?_sw-precache=2b73458… (beta-m.hometown.in) 726.9 KiB
…1.6.106/29e2119….png?_sw-precache=29e2119… (beta-m.hometown.in) 630.1 KiB
…1.6.106/9d2fd23….jpg?_sw-precache=9d2fd23… (beta-m.hometown.in) 491.0 KiB
…1.6.106/f9af2b2….jpg?_sw-precache=f9af2b2… (beta-m.hometown.in) 488.2 KiB
…1.6.106/148c9bb….png?_sw-precache=148c9bb… (beta-m.hometown.in) 426.8 KiB
…1.6.106/2773549….jpg?_sw-precache=2773549… (beta-m.hometown.in) 413.1 KiB
…1.6.106/5e323fc….jpg?_sw-precache=5e323fc… (beta-m.hometown.in) 409.5 KiB
about:blank 4/39
Transfer
URL
Size
…1.6.106/264a7db….jpg?_sw-precache=264a7db… (beta-m.hometown.in) 404.4 KiB
Minimize main-thread work — 16.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps
with this. Learn more TBT
Category Time Spent
Script Evaluation 4,535 ms
Other 3,940 ms
Rendering 3,845 ms
Style & Layout 3,060 ms
Script Parsing & Compilation 313 ms
Parse HTML & CSS 168 ms
Garbage Collection 140 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more. FCP LCP
Potential
URL
Savings
/fonts/37953885-0443-4c72-a693-9152a9f5a901.woff2 (m.hometown.in) 470 ms
/fonts/89294146-207c-4803-91fe-338f0d0094bd.woff2 (m.hometown.in) 480 ms
/fonts/7ce0a2f5-eb00-46aa-919c-5b3f3667646c.woff2 (m.hometown.in) 470 ms
/fonts/315bbeb9-a30f-4f38-91ae-d6cfbbf89437.ttf (m.hometown.in) 480 ms
/fonts/2922d55c-8df4-4066-b7b0-eec2d1524330.ttf (m.hometown.in) 450 ms
about:blank 5/39
Potential
URL
Savings
/fonts/8ebb9b04-d12d-488e-aa96-0bb6e6777336.ttf (m.hometown.in) 650 ms
Reduce the impact of third-party code — Third-party code blocked the main thread for 370 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to
load third-party code after your page has primarily finished loading. Learn more. TBT
Transfer Main-Thread Blocking

Third-Party
Size Time
Google Tag Manager 204 KiB 284 ms
/gtag/js?id=AW-845… (www.googletagmanager.com) 65 KiB 278 ms
/gtm.js?id=GTM-T5VV7MZ (www.googletagmanager.com) 96 KiB 6 ms
/gtag/js?id=DC-12399743 (www.googletagmanager.com) 43 KiB 0 ms
Google Analytics 21 KiB 45 ms
/analytics.js (www.google-analytics.com) 20 KiB 45 ms
WebEngage 83 KiB 43 ms
/js/webengage-min-v-6.0.js (widgets.in.webengage.com) 60 KiB 43 ms
/in~~15ba205b0/bfe93877-0e84-4355-83e3-
21 KiB 0 ms
a3f2fdeede85.png (afiles.in.webengage.com)
Salesforce.com 72 KiB 0 ms
…frame/chasitor.esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) 11 KiB 0 ms
…5.0/esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) 9 KiB 0 ms
…5.0/esw.min.js (service.force.com) 9 KiB 0 ms
…client/liveagent.esw.min.js (praxisretail--
7 KiB 0 ms
produat.sandbox.my.salesforce.com)
…client/invite.esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) 5 KiB 0 ms
Other resources 31 KiB 0 ms
Salesforce Live Agent 48 KiB 0 ms
…47.0/deployment.js (c.la1-c1-hnd.salesforceliveagent.com) 42 KiB 0 ms
Other resources 5 KiB 0 ms
Bing Ads 13 KiB 0 ms
/bat.js (bat.bing.com) 12 KiB 0 ms
about:blank 6/39
Transfer Main-Thread Blocking

Third-Party
Size Time
Cloudflare CDN 11 KiB 0 ms
…14.7.0/nouislider.min.js (cdnjs.cloudflare.com) 8 KiB 0 ms
Amazon Web Services 2 KiB 0 ms
Other Google APIs/SDKs 0 KiB 0 ms
Google/Doubleclick Ads 0 KiB 0 ms
Facebook 0 KiB 0 ms
Serve static assets with an efficient cache policy — 29 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Cache Transfer
URL
TTL Size
/sw.js (beta-m.hometown.in) None 14 KiB
/embed.js (d21gpk1vhmjuf5.cloudfront.net) None 6 KiB
/static/crossdevice.min.js?campaign_code=f578644d44 (www.artfut.com) 20 m 8 KiB
/static/tracking.min.js?campaign_code=f578644d44 (www.artfut.com) 20 m 7 KiB
/static/tagtag.min.js?campaign_code=f578644d44 (www.artfut.com) 20 m 2 KiB
/stage-hometown808…_search_mobile.js (sandbox.unbxd.io) 1h 78 KiB
/stage-hometown808…_autosuggest_mobile.js (sandbox.unbxd.io) 1h 61 KiB
/unbxdAnalytics.js (d21gpk1vhmjuf5.cloudfront.net) 1h 11 KiB
/stage-hometown808…_search_mobile.css (sandbox.unbxd.io) 1h 7 KiB
/stage-hometown808…_autosuggest_mobile.css (sandbox.unbxd.io) 1h 2 KiB
…ua/ec.js (www.google-analytics.com) 1h 1 KiB
/analytics.js (www.google-analytics.com) 2h 20 KiB
about:blank 7/39
Cache Transfer
URL
TTL Size
/js/webengage-min-v-6.0.js (widgets.in.webengage.com) 4h 60 KiB
…frame/chasitor.esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) 1d 11 KiB
…5.0/esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) 1d 9 KiB
…5.0/esw.min.js (service.force.com) 1d 9 KiB
…client/liveagent.esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) 1d 7 KiB
…client/invite.esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) 1d 5 KiB
…5.0/esw.min.css (praxisretail--produat.sandbox.my.salesforce.com) 1d 5 KiB
…5.0/eswFrame.min.js (praxisretail--produat.sandbox.my.salesforce.com) 1d 5 KiB
…utils/inert.min.js (praxisretail--produat.sandbox.my.salesforce.com) 1d 3 KiB
…utils/common.min.js (praxisretail--produat.sandbox.my.salesforce.com) 1d 3 KiB
…frame/broadcast.esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) 1d 3 KiB
…frame/session.esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) 1d 3 KiB
…frame/filetransfer.esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) 1d 1 KiB
…2.1/gumlet.min.js (cdn.gumlet.com) 2d 5 KiB
/in~~15ba205b0/bfe93877-0e84-4355-83e3-a3f2fdeede85.png (afiles.in.webengage.com) 7d 21 KiB
…v2.2.0/unbxd_recs_template_sdk_apac.js (libraries.unbxdapi.com) 30 d 10 KiB
/unbxdAnalyticsConfig.js (d21gpk1vhmjuf5.cloudfront.net) 30 d 1 KiB
Reduce JavaScript execution time — 4.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps
with this. Learn more. TBT
about:blank 8/39
Total CPU Script Script

URL
Time Evaluation Parse
https://beta-m.hometown.in 9,092 ms 190 ms 40 ms
…1.6.106/Home-0186ce3….chunk.js (beta-m.hometown.in) 1,802 ms 1,627 ms 11 ms
Unattributable 1,597 ms 13 ms 0 ms
…1.6.106/main-3bc9dfa….js (beta-m.hometown.in) 763 ms 597 ms 92 ms
/gtag/js?id=AW-845… (www.googletagmanager.com) 518 ms 474 ms 17 ms
/stage-hometown808…_search_mobile.js (sandbox.unbxd.io) 459 ms 423 ms 27 ms
/js/webengage-min-v-6.0.js (widgets.in.webengage.com) 426 ms 332 ms 20 ms
…2.1/gumlet.min.js (cdn.gumlet.com) 367 ms 165 ms 7 ms
/gtm.js?id=GTM-T5VV7MZ (www.googletagmanager.com) 212 ms 178 ms 27 ms
/stage-hometown808…_autosuggest_mobile.js (sandbox.unbxd.io) 134 ms 66 ms 12 ms
/analytics.js (www.google-analytics.com) 115 ms 99 ms 5 ms
/static/crossdevice.min.js?
93 ms 87 ms 4 ms
campaign_code=f578644d44 (www.artfut.com)
…5.0/esw.min.js (praxisretail--produat.my.salesforce.com) 75 ms 66 ms 5 ms
/unbxdAnalytics.js (d21gpk1vhmjuf5.cloudfront.net) 66 ms 60 ms 4 ms
…ua/ec.js (www.google-analytics.com) 54 ms 51 ms 1 ms
Avoid an excessive DOM size — 1,317 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
TBT
Consider using a "windowing" library like `react-window` to minimize the number of DOM nodes created if you are
rendering many repeated elements on the page. Learn more. Also, minimize unnecessary re-renders using
`shouldComponentUpdate`, `PureComponent`, or `React.memo` and skip effects only until certain dependencies
have changed if you are using the Èffect` hook to improve runtime performance.
about:blank 9/39
Statistic Element Value
Total DOM Elements 1,317
Maximum DOM Depth a 18
body
Maximum Child Elements 44
Avoid chaining critical requests — 5 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of
chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page
load. Learn more. FCP LCP
Maximum critical path latency: 740 ms
Initial Navigation
https://beta-m.hometown.in
…1.6.106/main-3bc9dfa….css (beta-m.hometown.in)
…1.6.106/f21a1fd….woff2 (beta-m.hometown.in) - 140 ms, 19.46 KiB
…1.6.106/055551b….woff2 (beta-m.hometown.in) - 140 ms, 17.60 KiB
…1.6.106/d856c13….woff2 (beta-m.hometown.in) - 140 ms, 19.21 KiB
data:application/font-woff;base64,d09GRk9UVE8AAAVkAAsAAAAAB1wAA… - 140 ms, 1.35 KiB
…47.0/deployment.js (c.la1-c1-hnd.salesforceliveagent.com) - 180 ms, 42.11 KiB
Keep request counts low and transfer sizes small — 356 requests • 26,656 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Resource Type Requests Transfer Size
Total 356 26,655.7 KiB
Other 256 25,068.8 KiB
Script 45 1,014.8 KiB
Image 39 391.7 KiB
Stylesheet 4 68.1 KiB
about:blank 10/39
Resource Type Requests Transfer Size
Font 9 56.3 KiB
Document 3 56.0 KiB
Media 0 0.0 KiB
Third-party 80 810.1 KiB
Avoid large layout shifts — 5 elements found
These DOM elements contribute most to the CLS of the page. CLS
Element CLS Contribution
div.slick-slider.mainSlider.slick-initialized
0.026
section.Section-sc-1q695t-0.iCLgXS
0.015
div.slick-list
0.007
div._3a4d6R32LJICp0gTifpHeQ.Div-ln5jk2-0.cYnhEW
0.005
div._3u2pykcmhjI6po7ZJ9CbGV
0.004
about:blank 11/39
Avoid long main-thread tasks — 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more TBT
URL Start Time Duration
…1.6.106/main-3bc9dfa….js (beta-m.hometown.in) 10,921 ms 889 ms
/stage-hometown808…_search_mobile.js (sandbox.unbxd.io) 13,396 ms 402 ms
https://beta-m.hometown.in 1,397 ms 299 ms
/gtag/js?id=AW-845… (www.googletagmanager.com) 16,251 ms 278 ms
…1.6.106/Home-0186ce3….chunk.js (beta-m.hometown.in) 10,246 ms 210 ms
Unattributable 1,976 ms 171 ms
/gtag/js?id=AW-845… (www.googletagmanager.com) 16,092 ms 159 ms
…2.1/gumlet.min.js (cdn.gumlet.com) 3,092 ms 127 ms
/stage-hometown808…_autosuggest_mobile.js (sandbox.unbxd.io) 15,646 ms 124 ms
…in~~15ba205b0/v4.js?r=27838519 (s3.ap-south-1.amazonaws.com) 15,195 ms 118 ms
/analytics.js (www.google-analytics.com) 18,643 ms 104 ms
Unattributable 2,147 ms 92 ms
about:blank 12/39
URL Start Time Duration
Avoid non-composited animations — 18 animated elements found
Animations which are not composited can be janky and increase CLS. Learn more CLS
Element Name
div.Shimmer-c0glng-0.dMTPJJ
Unsupported CSS Properties: background-position-x, background-position-y SCGBK
about:blank 13/39
Element Name
More information about the performance of your application. These numbers don't directly affect the Performance score.
PASSED AUDITS (23) Hide
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to
interactive. Learn more.
Minify CSS — Potential savings of 9 KiB
Minifying CSS files can reduce network payload sizes. Learn more. FCP LCP
If your build system minifies CSS files automatically, ensure that you are deploying the production build of your
application. You can check this with the React Developer Tools extension. Learn more.
about:blank 14/39
Transfer Potential
URL
Size Savings
…1.6.106/main-3bc9dfa….css (beta-m.hometown.in) 53.8 KiB 8.6 KiB
Minify JavaScript — Potential savings of 2 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more. FCP LCP
If your build system minifies JS files automatically, ensure that you are deploying the production build of your
application. You can check this with the React Developer Tools extension. Learn more.
Transfer Potential
URL
Size Savings
/embed.js (d21gpk1vhmjuf5.cloudfront.net) 6.0 KiB 2.1 KiB
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.
Enable text compression — Potential savings of 34 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn
more. FCP LCP
Transfer Potential
URL
Size Savings
…47.0/deployment.js (c.la1-c1-hnd.salesforceliveagent.com) 41.7 KiB 30.3 KiB
/embed.js (d21gpk1vhmjuf5.cloudfront.net) 5.5 KiB 4.0 KiB
Preconnect to required origins
Warnings:
A `<link rel=preconnect>` was found for "https://bid.g.doubleclick.net" but was not used by the browser. Only use
`preconnect` for important origins that the page will certainly request.
A `<link rel=preconnect>` was found for "https://api.hometown.in" but was not used by the browser. Only use
A `<link rel=preconnect>` was found for "https://d.la1-c1-hnd.salesforceliveagent.com" but was not used by the
browser. Only use `preconnect` for important origins that the page will certainly request.
about:blank 15/39
A `<link rel=preconnect>` was found for "https://static.criteo.net" but was not used by the browser. Only use
A `<link rel=preconnect>` was found for "http://static.criteo.net" but was not used by the browser. Only use
A `<link rel=preconnect>` was found for "http://m.hometown.in" but was not used by the browser. Only use
More than 2 `<link rel=preconnect>` connections were found. These should be used sparingly and only to the
most important origins.
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins.
Learn more. FCP LCP
Initial server response time was short — Root document took 270 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more. FCP
LCP
If you are server-side rendering any React components, consider using `renderToPipeableStream()` or
`renderToStaticNodeStream()` to allow the client to receive and hydrate different parts of the markup instead of all
at once. Learn more.
URL Time Spent
https://beta-m.hometown.in 270 ms
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more. FCP LCP
If you are using React Router, minimize usage of the `<Redirect>` component for route navigations.
Preload key requests
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn
more. FCP LCP
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and
PNG/WebP for static images instead of GIF to save network bytes. Learn more LCP
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
TBT
about:blank 16/39
Avoid serving legacy JavaScript to modern browsers — Potential savings of 33 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for
modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature
detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn
More TBT
URL Potential Savings
…1.6.106/main-3bc9dfa….js (beta-m.hometown.in) 0.2 KiB
main-3bc9dfa….js:1 @babel/plugin-transform-classes
…1.6.106/Home-0186ce3….chunk.js (beta-m.hometown.in) 0.1 KiB
Home-0186ce3….chunk.js:1 @babel/plugin-transform-classes
Preload Largest Contentful Paint image
Preload the image used by the LCP element in order to improve your LCP time. Learn more. LCP
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user
experiences. Learn more.
Use the React DevTools Profiler, which makes use of the Profiler API, to measure the rendering performance of
your components. Learn more.
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more.
TBT
Largest Contentful Paint element — 0 elements found
This is the largest contentful element painted within the viewport. Learn More LCP
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Learn more.
Uses passive listeners to improve scrolling performance
about:blank 17/39
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn
more.
Avoids document.write()
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of
seconds. Learn more.
Image elements have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn more CLS
Has a <meta name="viewport"> tag with width or initial-scale
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay
to user input. Learn more. TBT
Avoids unload event listeners
The ùnload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache.
Use `pagehide` or `visibilitychange` events instead. Learn more
87
Accessibility
These checks highlight opportunities to improve the accessibility of your
web app. Only a subset of accessibility issues can be automatically
detected so manual testing is also encouraged.
NAMES AND LABELS
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
Failing Elements
input.Input-tbll8j-0.djSSHH
about:blank 18/39
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.
ARIA
[aria-hidden="true"] elements contain focusable descendents
Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to
users of assistive technologies like screen readers. Learn more.
Failing Elements
div.slick-slide
div.slick-slide.slick-active.slick-current
div.slick-slide
div.slick-slide.slick-cloned
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive
technology, like a screen reader.
CONTRAST
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
about:blank 19/39
Failing Elements
label._1wtBl3xRjdyTpmGVA5Kl1e.Label-sc-1anmpe5-0.jDjwOu
button.Buttons__Button-sc-1t83isl-0.gKAaxu
These are opportunities to improve the legibility of your content.
NAVIGATION
Heading elements are not in a sequentially-descending order
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.
Failing Elements
h4.HeadingH4__Heading-sc-1ie9tmn-0.jAaUMx
These are opportunities to improve keyboard navigation in your application.
ADDITIONAL ITEMS TO MANUALLY CHECK (10) Hide
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more.
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn more.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive
elements. Learn more.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn more.
about:blank 20/39
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn more.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn more.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn more.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology.
Learn more.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility
review.
[aria-*] attributes match their roles
Each ARIA `role` supports a specific subset of ària-*` attributes. Mismatching these invalidates the ària-*` attributes. Learn
more.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when ària-hidden="true"` is set on the document `<body>`.
Learn more.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more.
about:blank 21/39
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who
rely on screen readers. Learn more.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt
attribute. Learn more.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less
than 5.
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.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a
page is relevant to their search. Learn more.
[id] attributes on active, focusable elements are unique
All focusable elements must have a unique ìd` to ensure that they're visible to assistive technologies. Learn more.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
about:blank 22/39
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user
chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not
announce the page's text correctly. Learn more.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.
Links have a discernible name
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 more.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn
more.
List items (<li>) are contained within <ul> or <ol> parent elements
Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn
more.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating
experiences for users who rely on assistive technologies. Learn more.
NOT APPLICABLE (21) Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn
more.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable
for users who rely on screen readers. Learn more.
ARIA input fields have accessible names
about:blank 23/39
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable
ARIA meter elements have accessible names
ARIA progressbar elements have accessible names
When a `progressbar` element doesn't have an accessible name, screen readers announce it with a generic name, making
it unusable for users who rely on screen readers. Learn more.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions.
Learn more.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable
ARIA tooltip elements have accessible names
ARIA treeitem elements have accessible names
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.
Definition list items are wrapped in <dl> elements
Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can
about:blank 24/39
properly announce them. Learn more.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn
more.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use
either the first, the last, or all of the labels. Learn more.
<input type="image"> elements have [alt] text
When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand
the purpose of the button. Learn more.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may
create a frustrating or confusing experience. Learn more.
<object> elements have alternate text
Screen readers cannot translate non-text content. Adding alternate text to `<object>` elements helps screen readers convey
meaning to users. Learn more.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring `<td>` cells using the `[headers]` attribute only
refer to other cells in the same table may improve the experience for screen reader users. Learn more.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells
may improve the experience for screen reader users. Learn more.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn
more.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more.
about:blank 25/39
67
Best Practices
TRUST AND SAFETY
Includes front-end JavaScript libraries with known security vulnerabilities — 13 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers.
Learn more.
Library Version Vulnerability Count Highest Severity
jQuery@1.11.3 4 Medium
Handlebars@3.0.1 9 High
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn more
Description Directive Severity
No CSP found in enforcement mode High
USER EXPERIENCE
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
Aspect Aspect
URL Ratio Ratio
(Displayed) (Actual)
img.gm-loaded.gm-observing.gm- …icons/mobile-offline-banner12.jpg? 360 x 220 767 x 450

observing-cb w=360&dpr=3.0 (hometown.gumlet.io) (1.64) (1.70)
about:blank 26/39
Aspect Aspect
URL Ratio Ratio
(Displayed) (Actual)
img.gm-added.gm-loaded.gm- …icons/mobile-offline-banner12.jpg? 360 x 220 767 x 450

observing.gm-observing-cb w=360&dpr=3.0 (hometown.gumlet.io) (1.64) (1.70)
img.gm-added.gm-loaded.gm- …icons/mobile-online-banner.jpg? 360 x 220 767 x 450

img.gm-loaded.gm-observing.gm- …icons/mobile-offline-banner12.jpg? 360 x 220 767 x 450

observing-cb w=360&dpr=3.0 (hometown.gumlet.io) (1.64) (1.70)
img.gm-added.gm-loaded.gm- …icons/mobile-offline-banner12.jpg? 360 x 220 767 x 450

img.gm-added.gm-loaded.gm- …icons/mobile-online-banner.jpg? 360 x 220 767 x 450

img.
gm-
load …icons/mob-mid-banner-strip-banner.jpg? 288 x 52 767 x 120
ed.g w=300&dpr=3.0 (hometown.gumlet.io) (5.54) (6.39)
m-
observing.gm-observing-cb
img
.Im
g-
…icons/Mattress-image.jpg? 90 x 80 82 x 82
sc-
w=100&dpr=3.0 (hometown.gumlet.io) (1.13) (1.00)
1a
u8jwx-0.ggDumt.gm-loaded.gm-
observing.gm-observing-cb
img.Img-sc-1au8jwx-0.jsiiMK.gm- data:image/jpeg;base64,/9j/4AAQSkZJRgAB 153 x 34 176 x 32

observing.gm-observing-cb AQAASABIAAD/4QBMRXhpZgAA… (4.50) (5.50)
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn
more.
Displayed Actual Expected

URL
size size size
data:image/png;base64,iVBORw0KGgoA 34 x 34 48 x 48 68 x 68
AAANSUhEUgAAADAAAAAwCAYAAABX
about:blank 27/39
Displayed Actual Expected

URL
size size size
A…
img.Img-sc-1au8jwx-
0.NLyCj.gm-observing.gm-
observing-cb
GENERAL
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser
concerns. Learn more
Source Description
beta- Access to font at 'https://m.hometown.in/fonts/2922d55c-8df4-4066-b7b0-eec2d1524330.ttf'
m.hometown.in/ from origin 'https://beta-m.hometown.in' has been blocked by CORS policy: No 'Access-
:1 Control-Allow-Origin' header is present on the requested resource.
beta- Access to font at 'https://m.hometown.in/fonts/315bbeb9-a30f-4f38-91ae-d6cfbbf89437.ttf'
beta- Access to font at 'https://m.hometown.in/fonts/37953885-0443-4c72-a693-9152a9f5a901.woff2'
beta- Access to font at 'https://m.hometown.in/fonts/7ce0a2f5-eb00-46aa-919c-5b3f3667646c.woff2'
beta- Access to font at 'https://m.hometown.in/fonts/89294146-207c-4803-91fe-338f0d0094bd.woff2'
beta- Access to font at 'https://m.hometown.in/fonts/8ebb9b04-d12d-488e-aa96-0bb6e6777336.ttf'
googleads.g.do Failed to load resource: net::ERR_CONNECTION_CLOSED
ublecl…
about:blank 28/39
Source Description
nfig&rfmt=3&fm
t=4:1
googleads.g.do
ublecl…
Failed to load resource: net::ERR_CONNECTION_CLOSED
aw=0&rfmt=3&f
mt=4:1
googleads.g.do
ublecl…
aw=0&rfmt=3&f
mt=4:1
www.googleads
ervices…
aw=0&rfmt=3&f
mt=4:1
m.hometown.in/
fonts/…
Failed to load resource: net::ERR_FAILED
152a9f5a901.w
off2:1
m.hometown.in/
fonts/…
38f0d0094bd.w
off2:1
m.hometown.in/
fonts/…
b3f3667646c.w
off2:1
m.hometown.in/
fonts/…-
eec2d1524330.
ttf:1
m.hometown.in/
fonts/…-
d6cfbbf89437.tt
f:1
m.hometown.in/
fonts/…-0bb6e6 Failed to load resource: net::ERR_FAILED
777336.ttf:1
about:blank 29/39
Source Description
connect.facebo
ok.net/en_US/f Failed to load resource: net::ERR_NAME_NOT_RESOLVED
bevents.js:1
d21gpk1vhmjuf
5.cloud… ReferenceError: jQuery is not defined at
nt.net/embed.js: https://d21gpk1vhmjuf5.cloudfront.net/embed.js:160:4
160
beta- Refused to execute script from
m.hometown.in/ 'https://cdnjs.cloudflare.com/ajax/libs/noUiSlider/14.7.0/nouislider.css' because its MIME
:1 type ('text/css') is not executable, and strict MIME type checking is enabled.
beta- Refused to execute script from
m.hometown.in/ 'https://cdnjs.cloudflare.com/ajax/libs/noUiSlider/14.7.0/nouislider.css' because its MIME
:1 type ('text/css') is not executable, and strict MIME type checking is enabled.
TypeError: Cannot redefine property: inert at Function.defineProperty (<anonymous>) at
praxisretail-- https://praxisretail--
produa… produat.my.salesforce.com/embeddedservice/5.0/utils/inert.min.js:16:307 at
ils/inert.min.js:1 https://praxisretail--produat.my.salesforce.com/embeddedservice/5.0/utils/inert.min.js:1:132
6 at https://praxisretail--
produat.my.salesforce.com/embeddedservice/5.0/utils/inert.min.js:1:137
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more.
Name Version
jQuery 1.11.3
about:blank 30/39
Name Version
React
Handlebars 3.0.1
core-js core-js-pure@2.6.12; core-js-global@2.6.12
Missing source maps for large first-party JavaScript
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.
URL Map URL
…1.6.106/main-3bc9dfa….js (beta-m.hometown.in)
Large JavaScript file is missing a source map
… …
v2.2.0/unbxd_recs_template_sdk_apac.js (libraries.unbx v2.2.0/unbxd_recs_template_sdk_apac.js.map (libraries.un
dapi.com) bxdapi.com)
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content,
where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents
intruders from tampering with or passively listening in on the communications between your app and your users, and is a
prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user
action instead. Learn more.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to
user gestures instead. Learn more.
about:blank 31/39
Allows users to paste into password fields
Preventing password pasting undermines good security policy. Learn more.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more.
Properly defines charset
A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the
Content-Type HTTP response header. Learn more.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more.
No issues in the Issues panel in Chrome Devtools
Issues logged to the Ìssues` panel in Chrome Devtools indicate unresolved problems. They can come from network
request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools
for more details on each issue.
NOT APPLICABLE (1) Hide
Fonts with font-display: optional are preloaded
Preload òptional` fonts so first-time visitors may use them. Learn more
89
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.
CRAWLING AND INDEXING
Page is blocked from indexing
about:blank 32/39
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more.
Blocking Directive Source
/robots.txt:4
To appear in search results, crawlers need access to your app.
MOBILE FRIENDLY
Tap targets are not sized appropriately — 49% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be
easy enough to tap without overlapping onto other elements. Learn more.
Tap Target Size Overlapping Target
button a
20x20
button a
20x20
button a
20x20
button a
20x20
button a
20x20
about:blank 33/39
button a
20x20
button a
20x20
button a
20x20
button button
20x20
button button
20x20
button button
20x20
button button
20x20
button button
20x20
about:blank 34/39
button button
20x20
button button
20x20
a 23x14 a
a 23x14 a
a 42x14 a
a 42x14 a
a 118x14 a
a 62x14 a
a 73x14 a
a 23x23 a
a 23x23 a
a 23x23 a
a 23x23 a
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more.
Run these additional validators on your site to check additional SEO best practices.
about:blank 35/39
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a
page is relevant to their search. Learn more.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn more.
Links are crawlable
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 More
robots.txt is valid
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.
Image elements have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt
attribute. Learn more.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region.
Learn more.
about:blank 36/39
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more.
Document uses legible font sizes — 99.58% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to
have >60% of page text ≥12px. Learn more.
Source Selector % of Page Text Font Size
main-3bc9dfa….css:1956 .slick-dots li button 0.35% 6px
dynamic .jDjwOu 0.07% 8px
Legible text 99.58% ≥ 12px
Document avoids plugins
Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more.
PWA
These checks validate the aspects of a Progressive Web App. Learn more.
INSTALLABLE
Web app manifest and service worker meet the installability requirements
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to
homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively
prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.
PWA OPTIMIZED
Registers a service worker that controls page and start_url
about:blank 37/39
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline,
add to homescreen, and push notifications. Learn more.
Configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn
more.
Sets a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more.
Content is sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile
screens. Learn more.
Does not provide a valid apple-touch-icon
For ideal appearance on iOS when users add a progressive web app to the home screen, define an àpple-touch-icon`. It
must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device.
Learn more.
Site works cross-browser
To reach the most number of users, sites should work across every major browser. Learn more.
Page transitions don't feel like they block on the network
Transitions should feel snappy as you tap around, even on a slow network. This experience is key to a user's perception of
performance. Learn more.
Each page has a URL
about:blank 38/39
Ensure individual pages are deep linkable via URL and that URLs are unique for the purpose of shareability on social
media. Learn more.
These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect
your score but it's important that you verify them manually.
Captured at Dec 6, 2022, Emulated Moto G4 with Single page load

12:49 PM GMT+5:30 Lighthouse 9.6.6
Initial page load Slow 4G throttling Using Chromium 108.0.0.0
with devtools
Generated by Lighthouse 9.6.6 | File an issue
about:blank 39/39

Beta Mobile Page Speed

Uploaded by

Copyright:

Available Formats

Beta Mobile Page Speed

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Beta Mobile Page Speed

Uploaded by

Copyright:

Available Formats

12/6/22, 12:53 PM about:blank

Performance Accessibility Best SEO PWA

There were issues affecting this run of Lighthouse:

0–49 50–89 90–100

METRICS Expand view

First Contentful Paint Time to Interactive

Speed Index Total Blocking Time

Largest Contentful Paint Cumulative Layout Shift

View Original Trace View Treemap

Show audits relevant to: All FCP TBT LCP CLS

Opportunity Estimated Savings

Reduce unused JavaScript 2.67 s

Show 3rd-party resources (7)

…1.6.106/main-3bc9dfa….js (beta-m.hometown.in) 348.1 KiB 165.8 KiB

/stage-hometown808…_search_mobile.js (sandbox.unbxd.io) 78.2 KiB 50.8 KiB

/stage-hometown808…_autosuggest_mobile.js (sandbox.unbxd.io) 60.9 KiB 45.6 KiB

/js/webengage-min-v-6.0.js (widgets.in.webengage.com) 60.0 KiB 37.7 KiB

…47.0/deployment.js (c.la1-c1-hnd.salesforceliveagent.com) 42.1 KiB 29.2 KiB

/gtm.js?id=GTM-T5VV7MZ (www.googletagmanager.com) 95.7 KiB 28.8 KiB

/gtag/js?id=AW-845… (www.googletagmanager.com) 65.4 KiB 28.1 KiB

…1.6.106/Home-0186ce3….chunk.js (beta-m.hometown.in) 49.0 KiB 23.1 KiB

/gtag/js?id=DC-12399743 (www.googletagmanager.com) 43.1 KiB 22.9 KiB

Serve images in next-gen formats 1.2 s

…icons/mobile-offline-banner12.jpg?blur=30 (www.hometown.in) 83.2 KiB 40.0 KiB

…icons/mobile-online-banner.jpg?blur=30 (www.hometown.in) 77.4 KiB 37.2 KiB

…icons/mob-mid-banner-strip-banner.jpg?blur=30 (www.hometown.in) 20.5 KiB 10.4 KiB

Eliminate render-blocking resources 0.36 s

…1.6.106/main-3bc9dfa….css (beta-m.hometown.in) 53.8 KiB 450 ms

Use HTTP/2 0.3 s

…5.0/esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) http/1.1

…utils/common.min.js (praxisretail--produat.sandbox.my.salesforce.com) http/1.1

…5.0/esw.min.css (praxisretail--produat.sandbox.my.salesforce.com) http/1.1

…client/liveagent.esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) http/1.1

…5.0/esw.html?parent=https://beta-m.hometown.in/ (praxisretail--produat.sandbox.my.salesforce.com) http/1.1

…5.0/eswFrame.min.js (praxisretail--produat.sandbox.my.salesforce.com) http/1.1

…frame/session.esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) http/1.1

…frame/broadcast.esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) http/1.1

…frame/chasitor.esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) http/1.1

…frame/filetransfer.esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) http/1.1

…client/invite.esw.min.js (praxisretail--produat.sandbox.my.salesforce.com) http/1.1

…utils/inert.min.js (praxisretail--produat.sandbox.my.salesforce.com) http/1.1

Reduce unused CSS 0.15 s

…1.6.106/main-3bc9dfa….css (beta-m.hometown.in) 53.8 KiB 49.5 KiB

Avoid enormous network payloads — Total size was 26,657 KiB

…1.6.106/cec195a….png?_sw-precache=cec195a… (beta-m.hometown.in) 3,101.5 KiB

…1.6.106/606b818….png?_sw-precache=606b818… (beta-m.hometown.in) 2,311.9 KiB

…1.6.106/2b73458….jpg?_sw-precache=2b73458… (beta-m.hometown.in) 726.9 KiB

…1.6.106/29e2119….png?_sw-precache=29e2119… (beta-m.hometown.in) 630.1 KiB

…1.6.106/9d2fd23….jpg?_sw-precache=9d2fd23… (beta-m.hometown.in) 491.0 KiB

…1.6.106/f9af2b2….jpg?_sw-precache=f9af2b2… (beta-m.hometown.in) 488.2 KiB

…1.6.106/148c9bb….png?_sw-precache=148c9bb… (beta-m.hometown.in) 426.8 KiB

…1.6.106/2773549….jpg?_sw-precache=2773549… (beta-m.hometown.in) 413.1 KiB

…1.6.106/5e323fc….jpg?_sw-precache=5e323fc… (beta-m.hometown.in) 409.5 KiB

…1.6.106/264a7db….jpg?_sw-precache=264a7db… (beta-m.hometown.in) 404.4 KiB

Minimize main-thread work — 16.0 s

Category Time Spent

Script Evaluation 4,535 ms

Style & Layout 3,060 ms

Script Parsing & Compilation 313 ms