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

https://beta.hometown.in/

71 77 92 83

Performance Accessibility Best SEO PWA

Practices

71

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

0.4 s 3.6 s

Speed Index Total Blocking Time

2.1 s 270 ms

Largest Contentful Paint Cumulative Layout Shift

1.0 s 0.294

View Original Trace View Treemap

Show audits relevant to: All FCP TBT LCP CLS

OPPORTUNITIES

Opportunity Estimated Savings

Reduce unused JavaScript 0.4 s

about:blank 1/35
12/6/22, 12:56 PM about:blank

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 (3)

Transfer Potential
URL
Size Savings

…2.6.84/main-c6b3ba4….js (beta.hometown.in) 606.9 KiB 234.9 KiB

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

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

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

Use HTTP/2 0.28 s

HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more.

URL Protocol

…5.0/esw.min.js (service.force.com) http/1.1

…utils/common.min.js (service.force.com) http/1.1

…5.0/esw.min.css (service.force.com) http/1.1

…client/liveagent.esw.min.js (service.force.com) http/1.1

…5.0/esw.html?parent=https://beta.hometown.in/ (service.force.com) http/1.1

…5.0/eswFrame.min.js (service.force.com) http/1.1

…frame/session.esw.min.js (service.force.com) http/1.1

…frame/broadcast.esw.min.js (service.force.com) http/1.1

…frame/chasitor.esw.min.js (service.force.com) http/1.1

…client/invite.esw.min.js (service.force.com) http/1.1

…utils/inert.min.js (service.force.com) http/1.1

about:blank 2/35
12/6/22, 12:56 PM about:blank

URL Protocol

…frame/filetransfer.esw.min.js (service.force.com) http/1.1

Serve images in next-gen formats 0.19 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

…New%20desktop/shoerack1.png?
155.1 KiB 144.7 KiB
blur=30 (www.hometown.in)

…icons/web-offline-banner.jpg?
184.9 KiB 91.0 KiB
blur=30 (www.hometown.in)

…shopbycat/shopbycat01.png?
46.7 KiB 41.6 KiB
blur=30 (www.hometown.in)

…shopbycat/shopbycat06.png?
38.4 KiB 35.9 KiB
blur=30 (www.hometown.in)

…shopbycat/shopbycat03.png?
39.1 KiB 35.4 KiB
blur=30 (www.hometown.in)

…shopbycat/shopbycat02.png?
38.0 KiB 33.7 KiB
blur=30 (www.hometown.in)

…shopbycat/shopbycat09.png?
36.4 KiB 32.8 KiB
blur=30 (www.hometown.in)

…icons/astra.png?blur=30 (www.hometown.in) 34.2 KiB 30.6 KiB

…shopbycat/shopbycat11.png?
32.5 KiB 28.2 KiB
blur=30 (www.hometown.in)

…shopbycat/shopbycat08.png?
29.9 KiB 27.2 KiB
blur=30 (www.hometown.in)

…icons/bahubali-dining.png?
31.3 KiB 26.4 KiB
blur=30 (www.hometown.in)

about:blank 3/35
12/6/22, 12:56 PM about:blank

Resource Potential
URL
Size Savings

…2.6.84/10f0829….png (beta.hometown.in) 28.5 KiB 24.7 KiB

mg.gm-observing.gm-observing-
cb

…icons/mid-banner-strip-banner.jpg?
44.9 KiB 23.9 KiB
blur=30 (www.hometown.in)

…shopbycat/shopbycat12.png?
27.7 KiB 23.9 KiB
blur=30 (www.hometown.in)

…icons/front-mattres1.png?
17.1 KiB 15.2 KiB
blur=30 (www.hometown.in)

These suggestions can help your page load faster. They don't directly affect the Performance score.

DIAGNOSTICS

Image elements do not have explicit width and height

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

Show 3rd-party resources (15)

URL

img.sc-
bZQynM.kjccFX.ImageHtV1__Imag
…icons/web-offline-banner.jpg?
e-sc-1jw4t8i-0.guPrxC.gm-
w=900&dpr=1.0 (hometown.gumlet.io)
loaded.gm-observing.gm-
observing-cb

img.sc-bZQynM.kjccFX.ImageHtV1__Image-sc-1jw4t8i- …icons/web-offline-banner.jpg?
0.guPrxC.gm-loaded.gm-observing.gm-observing-cb w=900&dpr=1.0 (hometown.gumlet.io)

img.sc-
bZQynM.dsCLuW.ImageHtV1
…icons/mid-banner-strip-banner.jpg?
__Image-sc-1jw4t8i-
w=700&dpr=1.0 (hometown.gumlet.io)
0.guPrxC.gm-loaded.gm-
observing.gm-observing-cb

about:blank 4/35
12/6/22, 12:56 PM about:blank

URL

img.Img-f8zcdq-
0.bLAjbf.gm-loaded.gm-
…shopbycat/shopbycat06.png?
observing.gm-observing-cb
w=128&dpr=1.0 (hometown.gumlet.io)

img.Img-f8zcdq-
0.bLAjbf.gm-loaded.gm-
…New%20desktop/shoerack1.png?
observing.gm-observing-cb
w=128&dpr=1.0 (hometown.gumlet.io)

img.Img-f8zcdq-
0.bLAjbf.gm-loaded.gm-
…shopbycat/shopbycat03.png?
observing.gm-observing-cb
w=128&dpr=1.0 (hometown.gumlet.io)

img.Img-f8zcdq-
0.bLAjbf.gm-loaded.gm-
…shopbycat/shopbycat01.png?
observing.gm-observing-cb
w=128&dpr=1.0 (hometown.gumlet.io)

img.Img-f8zcdq-
0.bLAjbf.gm-loaded.gm-
…shopbycat/shopbycat02.png?
observing.gm-observing-cb
w=128&dpr=1.0 (hometown.gumlet.io)

img.Img-f8zcdq-
0.bLAjbf.gm-loaded.gm-
…icons/bahubali-dining.png?
observing.gm-observing-cb
w=128&dpr=1.0 (hometown.gumlet.io)

img.Img-f8zcdq-
0.bLAjbf.gm-loaded.gm-
…icons/astra.png?
observing.gm-observing-cb
w=128&dpr=1.0 (hometown.gumlet.io)

img.Img-f8zcdq-
0.bLAjbf.gm-loaded.gm-
…shopbycat/shopbycat08.png?
observing.gm-observing-cb
w=128&dpr=1.0 (hometown.gumlet.io)

about:blank 5/35
12/6/22, 12:56 PM about:blank

URL

img.Img-f8zcdq-
0.bLAjbf.gm-loaded.gm-
…shopbycat/shopbycat09.png?
observing.gm-observing-cb
w=128&dpr=1.0 (hometown.gumlet.io)

img.Img-f8zcdq-
0.bLAjbf.gm-loaded.gm-
…icons/front-mattres1.png?
observing.gm-observing-cb
w=128&dpr=1.0 (hometown.gumlet.io)

img.Img-f8zcdq-
0.bLAjbf.gm-loaded.gm-
…shopbycat/shopbycat12.png?
observing.gm-observing-cb
w=128&dpr=1.0 (hometown.gumlet.io)

img.Img-f8zcdq-
0.bLAjbf.gm-loaded.gm-
…shopbycat/shopbycat11.png?
observing.gm-observing-cb
w=128&dpr=1.0 (hometown.gumlet.io)

img.gm-observing.gm-
observing-cb
…2.6.84/10f0829….png (beta.hometown.in)

Registers an unload listener

The `unload` 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

Source

https://beta.hometown.in:196:11795

Minimize main-thread work — 6.1 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 6/35
12/6/22, 12:56 PM about:blank

Category Time Spent

Rendering 2,244 ms

Other 1,523 ms

Style & Layout 1,066 ms

Script Evaluation 1,054 ms

Script Parsing & Compilation 106 ms

Garbage Collection 35 ms

Parse HTML & CSS 34 ms

Serve static assets with an efficient cache policy — 19 resources found

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

Show 3rd-party resources (18)

Cache Transfer
URL
TTL Size

/service-worker.js (beta.hometown.in) None 6 KiB

/1/0ad55a624f?a=… (bam.nr-data.net) None 1 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

/analytics.js (www.google-analytics.com) 2h 20 KiB

/nr-1071.min.js (js-agent.newrelic.com) 2h 9 KiB

…frame/chasitor.esw.min.js (service.force.com) 1d 10 KiB

…5.0/esw.min.js (service.force.com) 1d 9 KiB

…client/liveagent.esw.min.js (service.force.com) 1d 6 KiB

…client/invite.esw.min.js (service.force.com) 1d 5 KiB

about:blank 7/35
12/6/22, 12:56 PM about:blank

Cache Transfer
URL
TTL Size

…5.0/esw.min.css (service.force.com) 1d 4 KiB

…5.0/eswFrame.min.js (service.force.com) 1d 4 KiB

…utils/inert.min.js (service.force.com) 1d 3 KiB

…utils/common.min.js (service.force.com) 1d 2 KiB

…frame/broadcast.esw.min.js (service.force.com) 1d 2 KiB

…frame/session.esw.min.js (service.force.com) 1d 2 KiB

…frame/filetransfer.esw.min.js (service.force.com) 1d 1 KiB

…2.1/gumlet.min.js (cdn.gumlet.com) 2d 5 KiB

Avoid chaining critical requests — 11 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: 16,240 ms

Initial Navigation
https://beta.hometown.in

…2.6.84/main-c6b3ba4….css (beta.hometown.in)

…2.6.84/d856c13….woff2 (beta.hometown.in) - 10 ms, 19.20 KiB

…2.6.84/f21a1fd….woff2 (beta.hometown.in) - 20 ms, 19.45 KiB

/dev-hometown808…_autosuggest.css (sandbox.unbxd.io) - 120 ms, 0.00 KiB

/dev-hometown808…_search.css (sandbox.unbxd.io) - 120 ms, 0.00 KiB

…2.6.84/main-c6b3ba4….js (beta.hometown.in) - 140 ms, 606.94 KiB

…5.0/esw.min.js (service.force.com)

…5.0/esw.min.css (service.force.com)

data:application/octet-stream;base64,AAEAAAALAIAAAwAwT1MvMg8SBh… - 0 ms, 3.31 KiB

…47.0/deployment.js (c.la1-c1-hnd.salesforceliveagent.com) - 160 ms, 0.00 KiB

/dev-hometown808…_search.css (sandbox.unbxd.io) - 50 ms, 0.00 KiB

/dev-hometown808…_autosuggest.js (sandbox.unbxd.io) - 120 ms, 0.00 KiB

/dev-hometown808…_search.js (sandbox.unbxd.io) - 120 ms, 0.00 KiB

/unbxdAnalytics.js (d21gpk1vhmjuf5.cloudfront.net) - 160 ms, 0.00 KiB

about:blank 8/35
12/6/22, 12:56 PM about:blank

Keep request counts low and transfer sizes small — 89 requests • 2,058 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 89 2,058.1 KiB

Script 41 979.8 KiB

Image 32 903.6 KiB

Document 2 63.6 KiB

Stylesheet 5 57.9 KiB

Font 2 38.6 KiB

Other 7 14.5 KiB

Media 0 0.0 KiB

Third-party 60 434.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

0.144

div.slick-slider.maincarousel_one.slick-initialized

0.091

div 0.04

about:blank 9/35
12/6/22, 12:56 PM about:blank

Element CLS Contribution

div.sc-bdVaJa.gtVQmG 0.033

div.sc-bdVaJa.gtVQmG

0.017

Avoid long main-thread tasks — 3 long tasks found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more TBT

Show 3rd-party resources (1)

URL Start Time Duration

…2.6.84/main-c6b3ba4….js (beta.hometown.in) 2,929 ms 273 ms

…2.6.84/Home-d05702a….chunk.js (beta.hometown.in) 3,639 ms 133 ms

/gtm.js?id=GTM-T5VV7MZ (www.googletagmanager.com) 1,509 ms 60 ms

Avoid non-composited animations — 23 animated elements found

Animations which are not composited can be janky and increase CLS. Learn more CLS

Element Name

div.Shimmer-nbub4o-0.iRTSbQ

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.Shimmer-nbub4o-0.iRTSbQ

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.Shimmer-nbub4o-0.iRTSbQ

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.Shimmer-nbub4o-0.iRTSbQ

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.Shimmer-nbub4o-0.iRTSbQ

about:blank 10/35
12/6/22, 12:56 PM about:blank

Element Name

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.Shimmer-nbub4o-0.iRTSbQ

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.Shimmer-nbub4o-0.iRTSbQ

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.Shimmer-nbub4o-0.iRTSbQ

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.sc-bdVaJa > div.Shimmer-nbub4o-0

<div height="168px" width="100%" class="Shimmer-nbub4o-0 iRTSbQ">

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.sc-bdVaJa.gtVQmG

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.Shimmer-nbub4o-0.iRTSbQ

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.Shimmer-nbub4o-0.iRTSbQ

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.Shimmer-nbub4o-0.iRTSbQ

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.Shimmer-nbub4o-0.iRTSbQ

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.sc-bdVaJa > div.Shimmer-nbub4o-0

<div height="168px" width="100%" class="Shimmer-nbub4o-0 iRTSbQ">

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.sc-bdVaJa.gtVQmG

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.Shimmer-nbub4o-0.iRTSbQ

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.Shimmer-nbub4o-0.iRTSbQ

about:blank 11/35
12/6/22, 12:56 PM about:blank

Element Name

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.Shimmer-nbub4o-0.iRTSbQ

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.Shimmer-nbub4o-0.iRTSbQ

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.Shimmer-nbub4o-0.iRTSbQ

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div.Shimmer-nbub4o-0.iRTSbQ

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

div > div.Shimmer-nbub4o-0

<div height="800px" width="100%" class="Shimmer-nbub4o-0 ihOSnN">

Unsupported CSS Properties: background-position-x, background-position-y SCGBK

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

PASSED AUDITS (28) Hide

Eliminate render-blocking resources — Potential savings of 60 ms

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

…2.6.84/main-c6b3ba4….css (beta.hometown.in) 53.5 KiB 120 ms

Properly size images — Potential savings of 8 KiB

Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Resource Potential
URL
Size Savings

img.sc- …icons/web-offline-banner.jpg? 51.2 KiB 7.7 KiB

bZQynM.kjcc w=900&dpr=1.0 (hometown.gumlet.io)

about:blank 12/35
12/6/22, 12:56 PM about:blank

Resource Potential
URL
Size Savings

FX.ImageHt
V1__Image-
sc-1jw4t8i-
0.guPrxC.gm-loaded.gm-
observing.gm-observing-cb

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

Transfer Potential
URL
Size Savings

…2.6.84/main-c6b3ba4….css (beta.hometown.in) 53.5 KiB 8.5 KiB

Minify JavaScript

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.

Reduce unused CSS — Potential savings of 52 KiB

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

…2.6.84/main-c6b3ba4….css (beta.hometown.in) 53.5 KiB 52.1 KiB

Efficiently encode images

about:blank 13/35
12/6/22, 12:56 PM about:blank

Optimized images load faster and consume less cellular data. Learn more.

Enable text compression

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn
more. FCP LCP

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
`preconnect` for important origins that the page will certainly request.
A `<link rel=preconnect>` was found for "https://www.google.com" 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://www.google.co.in" 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://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.
A `<link rel=preconnect>` was found for "http://static.criteo.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 "http://m.hometown.in" but was not used by the browser. Only use
`preconnect` for important origins that the page will certainly request.
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 560 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.hometown.in 560 ms

Avoid multiple page redirects

about:blank 14/35
12/6/22, 12:56 PM about:blank

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

Avoid serving legacy JavaScript to modern browsers — Potential savings of 16 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

Show 3rd-party resources (4)

Potential
URL
Savings

…2.6.84/main-c6b3ba4….js (beta.hometown.in) 0.2 KiB

@babel/plugin-transform-
…2.6.84/main-c6b3ba4….js:3:14091 (beta.hometown.in)
classes

…2.6.84/Home-d05702a….chunk.js (beta.hometown.in) 0.1 KiB

…2.6.84/Home- @babel/plugin-transform-

d05702a….chunk.js:11:17437 (beta.hometown.in) classes

Preload Largest Contentful Paint image

Preload the image used by the LCP element in order to improve your LCP time. Learn more. LCP

Avoids enormous network payloads — Total size was 2,059 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn more. LCP

about:blank 15/35
12/6/22, 12:56 PM about:blank

Show 3rd-party resources (3)

Transfer
URL
Size

…2.6.84/main-c6b3ba4….js (beta.hometown.in) 606.9 KiB

…icons/web-offline-banner.jpg?blur=30 (www.hometown.in) 185.4 KiB

…New%20desktop/shoerack1.png?blur=30 (www.hometown.in) 155.6 KiB

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

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

https://beta.hometown.in 62.4 KiB

…2.6.84/main-c6b3ba4….css (beta.hometown.in) 53.5 KiB

…icons/web-offline-banner.jpg?w=900&dpr=1.0 (hometown.gumlet.io) 51.4 KiB

…2.6.84/Home-d05702a….chunk.js (beta.hometown.in) 49.5 KiB

…shopbycat/shopbycat01.png?blur=30 (www.hometown.in) 47.1 KiB

Avoids an excessive DOM size — 779 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 `Effect` hook to improve runtime performance.

Statistic Element Value

Total DOM Elements 779

Maximum DOM Depth h2.sc-eHgmQL.dHGoPb 21

about:blank 16/35
12/6/22, 12:56 PM about:blank

Statistic Element Value

body

Maximum Child Elements 36

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.

JavaScript execution time — 1.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

Show 3rd-party resources (2)

Total CPU
URL Script Evaluation Script Parse
Time

https://beta.hometown.in 4,593 ms 128 ms 19 ms

…2.6.84/Home-d05702a….chunk.js (beta.hometown.in) 466 ms 394 ms 5 ms

Unattributable 337 ms 6 ms 0 ms

…2.6.84/main-c6b3ba4….js (beta.hometown.in) 303 ms 234 ms 44 ms

/gtm.js?id=GTM-T5VV7MZ (www.googletagmanager.com) 144 ms 127 ms 7 ms

/gtag/js?id=AW-845… (www.googletagmanager.com) 71 ms 56 ms 15 ms

All text remains visible during webfont loads

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more. FCP LCP

Minimize third-party usage — Third-party code blocked the main thread for 0 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to

about:blank 17/35
12/6/22, 12:56 PM about:blank

load third-party code after your page has primarily finished loading. Learn more. TBT

Third-Party Transfer Size Main-Thread Blocking Time

Google Tag Manager 204 KiB 2 ms

/gtm.js?id=GTM-T5VV7MZ (www.googletagmanager.com) 96 KiB 2 ms

/gtag/js?id=AW-845… (www.googletagmanager.com) 65 KiB 0 ms

/gtag/js?id=DC-12399743 (www.googletagmanager.com) 43 KiB 0 ms

Salesforce.com 50 KiB 0 ms

…frame/chasitor.esw.min.js (service.force.com) 10 KiB 0 ms

…5.0/esw.min.js (service.force.com) 9 KiB 0 ms

…client/liveagent.esw.min.js (service.force.com) 6 KiB 0 ms

…client/invite.esw.min.js (service.force.com) 5 KiB 0 ms

…5.0/esw.min.css (service.force.com) 4 KiB 0 ms

Other resources 16 KiB 0 ms

Google Analytics 20 KiB 0 ms

/analytics.js (www.google-analytics.com) 20 KiB 0 ms

Bing Ads 12 KiB 0 ms

/bat.js (bat.bing.com) 12 KiB 0 ms

New Relic 10 KiB 0 ms

/nr-1071.min.js (js-agent.newrelic.com) 9 KiB 0 ms

Salesforce Live Agent 5 KiB 0 ms

Facebook 0 KiB 0 ms

WebEngage 0 KiB 0 ms

Google/Doubleclick Ads 0 KiB 0 ms

Criteo 0 KiB 0 ms

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

about:blank 18/35
12/6/22, 12:56 PM about:blank

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

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.

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

77

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

Buttons do not 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.

Failing Elements

button.sc-gqjmRU.fXbvHW

about:blank 19/35
12/6/22, 12:56 PM about:blank

Failing Elements

Image elements do not have [alt] attributes

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt
attribute. Learn more.

Failing Elements

img.slick-arrow.slick-prev.gm-observing.gm-observing-cb

img.slick-arrow.slick-next.gm-observing.gm-observing-cb

img.slick-arrow.slick-prev.slick-disabled.gm-added.gm-observing.gm-observing-cb

img.slick-arrow.slick-next.gm-added.gm-observing.gm-observing-cb

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

about:blank 20/35
12/6/22, 12:56 PM about:blank

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.

Failing Elements

div.sc-kpOJdX.fiTyzv

div.sc-kpOJdX.fiTyzv

div.sc-kpOJdX.gjCBan

button.sc-gqjmRU.eqnFRF

These are opportunities to improve the legibility of your content.

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.

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.

about:blank 21/35
12/6/22, 12:56 PM about:blank

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.

PASSED AUDITS (16) Hide

[aria-*] attributes match their roles

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn
more.

[aria-hidden="true"] is not present on the document <body>

Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document `<body>`.
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.

about:blank 22/35
12/6/22, 12:56 PM about:blank

Form elements have associated labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. 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 `id` to ensure that they're visible to assistive technologies. Learn more.

<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

about:blank 23/35
12/6/22, 12:56 PM about:blank

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.

Heading elements appear 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.

NOT APPLICABLE (24) 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

When an input field 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 meter 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 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.

[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 24/35
12/6/22, 12:56 PM about:blank

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.

[role] values are valid

ARIA roles must have valid values in order to 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
for users who rely on screen readers. Learn more.

ARIA tooltip 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 treeitem 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.

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

about:blank 25/35
12/6/22, 12:56 PM about:blank

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.

<frame> or <iframe> elements have a title

Screen reader users rely on frame titles to describe the contents of frames. 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.

92
about:blank 26/35
12/6/22, 12:56 PM
92 about:blank

Best Practices

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

Show 3rd-party resources (16)

Source Description

An unknown error occurred when fetching the script.

/service- DOMException: Failed to execute 'importScripts' on 'WorkerGlobalScope': The

worker.js:269:0 (beta.hometo script at 'https://widgets.in.webengage.com/js/service-worker.js' failed to

wn.in) load. at https://beta.hometown.in/service-worker.js:269:1

…viewthrou…/845…?
random=…:1:0 (googleads.g. Failed to load resource: net::ERR_CONNECTION_CLOSED

doubleclick.net)

…viewthrou…/845…?
random=…:1:0 (googleads.g. Failed to load resource: net::ERR_CONNECTION_CLOSED

doubleclick.net)

…viewthrou…/845…?
random=…:1:0 (googleads.g. Failed to load resource: net::ERR_CONNECTION_CLOSED

doubleclick.net)

…conversion/845…?
random=…:1:0 (www.googlea Failed to load resource: net::ERR_CONNECTION_CLOSED

dservices.com)

…ld/ld.js:1:0 (static.criteo.net) Failed to load resource: net::ERR_CONNECTION_CLOSED

…
v2.2.0/unbxd_recs_template
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
_sdk_apac.js:1:0 (libraries.un
bxdapi.com)

Failed to load resource: net::ERR_NAME_NOT_RESOLVED

/dev-hometown808…
_autosuggest.js:1:0 (sandbo

about:blank 27/35
12/6/22, 12:56 PM about:blank

Source Description

x.unbxd.io)

/dev-hometown808…
_autosuggest.css:1:0 (sandb Failed to load resource: net::ERR_NAME_NOT_RESOLVED

ox.unbxd.io)

/dev-hometown808…
_search.js:1:0 (sandbox.unbx Failed to load resource: net::ERR_NAME_NOT_RESOLVED

d.io)

/dev-hometown808…
_search.css:1:0 (sandbox.un Failed to load resource: net::ERR_NAME_NOT_RESOLVED

bxd.io)

/unbxdAnalytics.js:1:0 (d21g
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
pk1vhmjuf5.cloudfront.net)

…
47.0/deployment.js:1:0 (c.la1
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
-c1-
hnd.salesforceliveagent.com)

/js/webengage-min-v-
6.0.js:1:0 (widgets.in.webenga Failed to load resource: net::ERR_NAME_NOT_RESOLVED

ge.com)

/dev-hometown808…
_search.css:1:0 (sandbox.un Failed to load resource: net::ERR_NAME_NOT_RESOLVED

bxd.io)

…
v2.2.0/unbxd_recs_template
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
_sdk_apac.js:1:0 (libraries.un
bxdapi.com)

/en_US/fbevents.js:1:0 (conn
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
ect.facebook.net)

https://beta.hometown.in:39
ReferenceError: liveagent is not defined at https://beta.hometown.in/:391:16
1:15

Detected JavaScript libraries

All front-end JavaScript libraries detected on the page. Learn more.

about:blank 28/35
12/6/22, 12:56 PM about:blank

Name Version

React

[email protected]; [email protected]; [email protected]; [email protected]; core-js-

[email protected]; [email protected]; [email protected]; [email protected]; [email protected];
[email protected]; [email protected]; [email protected]; [email protected]; core-js-
core-js [email protected]; [email protected]; [email protected]; [email protected]; [email protected];
[email protected]; [email protected]; [email protected]; [email protected]; core-js-
[email protected]; [email protected]; [email protected]; [email protected]; [email protected];
[email protected]; [email protected]; [email protected]; [email protected]

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

…2.6.84/main-c6b3ba4….js (beta.hometown.in)

Large JavaScript file is missing a source map

TRUST AND SAFETY

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

PASSED AUDITS (11) Hide

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.

about:blank 29/35
12/6/22, 12:56 PM about:blank

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.

Avoids front-end JavaScript libraries with known security vulnerabilities

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers.
Learn more.

Allows users to paste into password fields

Preventing password pasting undermines good security policy. Learn more.

Displays images with correct aspect ratio

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

Serves images with appropriate resolution

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. 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 `Issues` 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

about:blank 30/35
12/6/22, 12:56 PM about:blank

for more details on each issue.

NOT APPLICABLE (1) Hide

Fonts with font-display: optional are preloaded

Preload `optional` fonts so first-time visitors may use them. Learn more

83

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

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:0 (beta.hometown.in)

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

CONTENT BEST PRACTICES

Image elements do not have [alt] attributes

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt
attribute. Learn more.

Failing Elements

img.slick-arrow.slick-prev.gm-observing.gm-observing-cb

about:blank 31/35
12/6/22, 12:56 PM about:blank

Failing Elements

img.slick-arrow.slick-next.gm-observing.gm-observing-cb

img.slick-arrow.slick-prev.slick-disabled.gm-added.gm-observing.gm-observing-cb

img.slick-arrow.slick-next.gm-added.gm-observing.gm-observing-cb

Format your HTML in a way that enables crawlers to better understand your app’s content.

ADDITIONAL ITEMS TO MANUALLY CHECK (1) Hide

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.

PASSED AUDITS (10) Hide

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

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.

about:blank 32/35
12/6/22, 12:56 PM about:blank

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.

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.

Document has a valid rel=canonical

Canonical links suggest which URL to show in search results. Learn more.

Document avoids plugins

Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more.

NOT APPLICABLE (2) Hide

Document uses legible font sizes

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.

Tap targets are sized appropriately

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.

about:blank 33/35
12/6/22, 12:56 PM about:blank

PWA
These checks validate the aspects of a Progressive Web App. Learn more.

INSTALLABLE

Web app manifest or service worker do not meet the installability requirements — 1 reason

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.

Failure reason

No matching service worker detected. You may need to reload the page, or check that the scope of the service worker
for the current page encloses the scope and start URL from the manifest.

PWA OPTIMIZED

Does not register a service worker that controls page and start_url

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.

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

about:blank 34/35
12/6/22, 12:56 PM about:blank

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

ADDITIONAL ITEMS TO MANUALLY CHECK (3) Hide

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

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 Desktop with Single page load

12:54 PM GMT+5:30 Lighthouse 9.6.6
Initial page load Custom throttling Using Chromium 108.0.0.0
with devtools

Generated by Lighthouse 9.6.6 | File an issue

about:blank 35/35