Lenskart Eyeglasses Performance Audit
Lenskart Eyeglasses Performance Audit
[Link]
45 60 58 93
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.
45
Performance
Values are estimated and may vary. The performance score
is calculated directly from these metrics. See calculator.
3.1 s 19.0 s
4.5 s 1,480 ms
3.5 s 0.117
about:blank 1/39
4/19/23, 6:05 AM about:blank
OPPORTUNITIES
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 `[Link]()`. Otherwise, code-split using a
third-party library such as loadable-components.
Transfer Potential
URL
Size Savings
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
about:blank 2/39
4/19/23, 6:05 AM about:blank
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
…o/john-jacobs-jj-e10229-c6-
77.9 KiB 66.7 KiB
eyeglasses_g_2242.jpg ([Link])
[Link]-max
…o/john-jacobs-jj-e10002-c2-
img 74.7 KiB 64.5 KiB
eyeglasses_g_1973.jpg ([Link])
…i/vincent-chase-vc-e11154-c2-
67.1 KiB 57.5 KiB
eyeglasses_m_2997.jpg ([Link])
[Link]-max
…o/john-jacobs-jj-e10002-c3-
54.6 KiB 47.0 KiB
eyeglasses_j_8534.jpg ([Link])
[Link]-max
Optimized images load faster and consume less cellular data. Learn more.
Resource Potential
URL
Size Savings
…o/john-jacobs-jj-e10229-c6-
77.9 KiB 53.4 KiB
eyeglasses_g_2242.jpg ([Link])
[Link]-max
…o/john-jacobs-jj-e10002-c2-
img 74.7 KiB 52.0 KiB
eyeglasses_g_1973.jpg ([Link])
about:blank 3/39
4/19/23, 6:05 AM about:blank
Resource Potential
URL
Size Savings
…i/vincent-chase-vc-e11154-c2-
67.1 KiB 45.8 KiB
eyeglasses_m_2997.jpg ([Link])
[Link]-max
…o/john-jacobs-jj-e10002-c3-
54.6 KiB 37.1 KiB
eyeglasses_j_8534.jpg ([Link])
[Link]-max
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.
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
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
about:blank 4/39
4/19/23, 6:05 AM about:blank
Resource Potential
URL
Size Savings
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
Potential
URL
Savings
vendor.cb9147b….js:1 [Link]
@babel/plugin-
vendor.cb9147b….js:1
transform-classes
vendor.cb9147b….js:1 [Link]
vendor.cb9147b….js:1 [Link]
vendor.cb9147b….js:1 [Link]
vendor.cb9147b….js:1 [Link]
[Link]
vendor.cb9147b….js:1
h
vendor.cb9147b….js:1 [Link]
vendor.cb9147b….js:1 [Link]
vendor.cb9147b….js:1 [Link]
vendor.cb9147b….js:1 [Link]
vendor.cb9147b….js:1 [Link]
vendor.cb9147b….js:1 [Link]
vendor.cb9147b….js:1 [Link]
vendor.cb9147b….js:1 [Link]
vendor.cb9147b….js:1 [Link]
[Link]
vendor.cb9147b….js:1
dex
[Link]
vendor.cb9147b….js:1
es
vendor.cb9147b….js:1 [Link]
about:blank 5/39
4/19/23, 6:05 AM about:blank
Potential
URL
Savings
@babel/plugin-
[Link]…2.9.102&r=stable:20
transform-classes
[Link]…2.9.102&r=stable:20 [Link]
[Link]…2.9.102&r=stable:20 [Link]
[Link]
[Link]…2.9.102&r=stable:20
es
[Link]…2.9.102&r=stable:20 [Link]
[Link]…2.9.102&r=stable:20 [Link]
[Link]/wi/[Link] [Link]
/static/[Link]?
8.2 KiB
campaign_code=80bb9f1208 ([Link])
[Link]/stati…n_code=80bb9f1208:2 [Link]
[Link]/stati…n_code=80bb9f1208:2 [Link]
[Link]/stati…n_code=80bb9f1208:2 [Link]
[Link]/stati…n_code=80bb9f1208:2 [Link]
@babel/plugin-
main.ba4b0d6….js:1
transform-classes
main.ba4b0d6….js:1 [Link]
@babel/plugin-
auth.12df987….js:1
transform-classes
[Link]
auth.12df987….js:1
ring
@babel/plugin-
redis-mapping.a7dda7e….js:1
transform-classes
about:blank 6/39
4/19/23, 6:05 AM about:blank
Potential
URL
Savings
@babel/plugin-
SWUpdateBanner.98f4c42….js:1
transform-classes
…in/Cart~ar-frames~auth~order-exchange~payment~retry-
0.1 KiB
payment….js ([Link])
@babel/plugin-
Cart~ar-frames~auth~…[Link]
transform-classes
@babel/plugin-
redis-mapping~shortl…[Link]
transform-classes
…in/Cart~auth~order-exchange~payment~retry-
0.0 KiB
payment~shippingN….js ([Link])
@babel/plugin-
Cart~auth~order-exch…[Link]
transform-classes
@babel/plugin-
[Link]…/[Link]
transform-classes
@babel/plugin-
[Link]…n_US/[Link]
transform-classes
These suggestions can help your page load faster. They don't directly affect the Performance score.
DIAGNOSTICS
Reduce the impact of third-party code — Third-party code blocked the main thread for 300 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
/gtag/js?id=G-
79 KiB 93 ms
FXRW59G0X3&l=dataLayer&cx=c ([Link])
about:blank 7/39
4/19/23, 6:05 AM about:blank
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn more CLS
about:blank 8/39
4/19/23, 6:05 AM about:blank
URL
im
g.w
idt
…o/john-jacobs-jj-e10002-c3-eyeglasses_j_8534.jpg ([Link])
h-
ma
x
im
g.w
idt
…i/vincent-chase-vc-e11154-c2-eyeglasses_m_2997.jpg ([Link])
h-
ma
x
im
g.w
idt
…o/john-jacobs-jj-e10229-c6-eyeglasses_g_2242.jpg ([Link])
h-
ma
x
img#fat
herabv
filter …plp/PLP%20Campaign%20-%20App%20(2).jpg ([Link])
…images/[Link] ([Link])
mg.width100
…images/[Link] ([Link])
mg
about:blank 9/39
4/19/23, 6:05 AM about:blank
URL
…images/phone_number.svg ([Link])
mg.width80
…img/[Link] ([Link])
[Link]-load-image
…DesignStudioIcons/[Link] ([Link])
mg
…Icon-Filter-new/Icon-Filter-new-01bf668….svg ([Link])
mg
…Icon-sort/Icon-sort-dbd357a….svg ([Link])
mg
…Star/Star-bc9e948….svg ([Link])
mg
i …Star/Star-bc9e948….svg ([Link])
mg
about:blank 10/39
4/19/23, 6:05 AM about:blank
URL
…Star/Star-bc9e948….svg ([Link])
mg
A long cache lifetime can speed up repeat visits to your page. Learn more.
Cache Transfer
URL
TTL Size
about:blank 11/39
4/19/23, 6:05 AM about:blank
Cache Transfer
URL
TTL Size
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps
with this. Learn more TBT
Other 1,654 ms
Rendering 236 ms
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 12/39
4/19/23, 6:05 AM about:blank
/gtag/js?id=G-
167 ms 153 ms 10 ms
FXRW59G0X3&l=dataLayer&cx=c ([Link])
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
Initial Navigation
/eyeglasses/[Link]?utm_source=… ([Link])
…fontello/fontello.c4b69cd….css ([Link])
…in/main.c4b69cd….css ([Link])
about:blank 13/39
4/19/23, 6:05 AM about:blank
Keep request counts low and transfer sizes small — 132 requests • 2,354 KiB
To set budgets for the quantity and size of page resources, add a [Link] file. Learn more.
Script 42 1,390.2 KiB
Font 12 406.3 KiB
Image 41 318.9 KiB
Document 2 116.5 KiB
Stylesheet 2 100.1 KiB
Other 33 22.2 KiB
Media 0 0.0 KiB
Third-party 74 534.1 KiB
This is the largest contentful element painted within the viewport. Learn More LCP
about:blank 14/39
4/19/23, 6:05 AM about:blank
Element
[Link]-max
These DOM elements contribute most to the CLS of the page. CLS
[Link]-b0
0.102
[Link]-card-wrapper
0.01
(+tax)
<span>
0.001
[Link]-15
0.001
div
0.001
about:blank 15/39
4/19/23, 6:05 AM about:blank
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more TBT
Animations which are not composited can be janky and increase CLS. Learn more CLS
about:blank 16/39
4/19/23, 6:05 AM about:blank
Element Name
[Link]-pale_grey.show-filter-sort-btns
show-filter-sort-
Unsupported CSS Property: bottom
btns
[Link]-
[Link]-icon
More information about the performance of your application. These numbers don't directly affect the Performance score.
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to
interactive. Learn more.
Resource Potential
URL
Size Savings
Minify CSS
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.
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.
about:blank 17/39
4/19/23, 6:05 AM about:blank
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn
more. FCP LCP
Warnings: 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
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.
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn
more. FCP LCP
Use HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more.
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 large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
TBT
Preload the image used by the LCP element in order to improve your LCP time. Learn more. LCP
Potential
URL
Savings
…o/john-jacobs-jj-e10002-c3- 0 ms
eyeglasses_j_8534.jpg ([Link])
about:blank 18/39
4/19/23, 6:05 AM about:blank
Potential
URL
Savings
[Link]-max
Large network payloads cost users real money and are highly correlated with long load times. Learn more. LCP
Transfer
URL
Size
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 `[Link]` and skip effects only until certain dependencies
have changed if you are using the `Effect` hook to improve runtime performance.
about:blank 19/39
4/19/23, 6:05 AM about:blank
₹
Maximum DOM Depth 17
<span>
body
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.
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more. FCP LCP
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more.
TBT
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Learn more.
Element
[Link]-max
about:blank 20/39
4/19/23, 6:05 AM about:blank
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn
more.
Avoids [Link]()
For users on slow connections, external scripts dynamically injected via `[Link]()` can delay page load by tens of
seconds. Learn more.
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
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
60
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.
ARIA
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn
more.
Failing Elements
[Link]-color_white.top-border
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those
required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.
about:blank 21/39
4/19/23, 6:05 AM about:blank
Failing Elements
[Link]-submenu-accordion
[Link]-submenu-accordion
[Link]-submenu-accordion
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.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt
attribute. Learn more.
Failing Elements
img#fatherabvfilter
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.
about:blank 22/39
4/19/23, 6:05 AM about:blank
Failing Elements
[Link]-rel
[Link]-r5
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of
assistive technology, like a screen reader.
BEST PRACTICES
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is 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.
Failing Elements
meta
CONTRAST
Low-contrast text is difficult or impossible for many users to read. Learn more.
Failing Elements
[Link]-t10
about:blank 23/39
4/19/23, 6:05 AM about:blank
Failing Elements
[Link]-color_link_blue.[Link]-32
[Link]-pale_grey
[Link]-pale_grey
span
[Link]-card-wrapper
(+tax)
<span>
[Link]-card-wrapper
about:blank 24/39
4/19/23, 6:05 AM about:blank
Failing Elements
Lists do not 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.
Failing Elements
[Link]-b0
[Link]-pale_grey.[Link]-wrapper
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more.
Custom interactive controls are keyboard focusable and display a focus indicator. Learn more.
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive
elements. Learn more.
about:blank 25/39
4/19/23, 6:05 AM about:blank
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn more.
A user can tab into and out of any control or region without accidentally trapping their focus. Learn more.
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more.
DOM order matches the visual order, improving navigation for assistive technology. Learn more.
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.
Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document `<body>`.
Learn more.
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more.
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more.
about:blank 26/39
4/19/23, 6:05 AM about:blank
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.
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.
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.
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.
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.
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn
more.
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.
about:blank 27/39
4/19/23, 6:05 AM about:blank
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.
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.
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.
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.
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions.
Learn more.
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.
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.
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.
about:blank 28/39
4/19/23, 6:05 AM about:blank
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.
All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn more.
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn
more.
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.
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
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.
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.
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. 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.
about:blank 29/39
4/19/23, 6:05 AM about:blank
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.
Screen readers cannot translate non-text content. Adding alternate text to `<object>` elements helps screen readers convey
meaning to users. Learn more.
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.
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.
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn
more.
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more.
58
Best Practices
USER EXPERIENCE
Image display dimensions should match natural aspect ratio. Learn more.
about:blank 30/39
4/19/23, 6:05 AM about:blank
[Link]-load- …
18 x 19 (0.95) 23 x 19 (1.21)
image img/[Link] ([Link])
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn
more.
…images/whatsapp-
48 x 48 48 x 48 96 x 96
[Link] ([Link])
img
…
img/[Link] ([Link]. 23 x 19 23 x 19 46 x 38
com)
[Link]-load-image
GENERAL
Deprecated APIs will eventually be removed from the browser. Learn more.
The `Expect-CT` header is deprecated and will be removed. Chrome requires Certificate promotions.h
Transparency for all publicly trusted certificates issued after April 30, 2018. tml:0
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser
concerns. Learn more
about:blank 31/39
4/19/23, 6:05 AM about:blank
Source Description
A bad HTTP response code (404) was received when fetching the script.
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
for more details on each issue.
Issue type
Cookie
/pagead/regclk?auid=… ([Link])
/pagead/landing?gclid=… ([Link])
/ads/ga-audiences?t=… ([Link])
…1p-user-list/998…?random=… ([Link])
…1p-user-list/998…?random=… ([Link])
…1p-user-list/339…?random=… ([Link])
/ads/ga-audiences?t=… ([Link])
…1p-user-list/339…?random=… ([Link])
…1p-user-list/998…?random=… ([Link])
/ads/ga-audiences?v=… ([Link])
…1p-user-list/998…?random=… ([Link])
/g/collect?v=… ([Link])
/[Link]?a=… ([Link])
/g/collect?v=… ([Link])
…conversion/998…?random=… ([Link])
…1p-conversion/998…?random=… ([Link])
…1p-conversion/998…?random=… ([Link])
Name Version
React
about:blank 32/39
4/19/23, 6:05 AM about:blank
Name Version
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.
…in/vendor.cb9147b….js ([Link])
…in/main.ba4b0d6….js ([Link])
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn more
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.
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.
about:blank 33/39
4/19/23, 6:05 AM about:blank
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.
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers.
Learn more.
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more.
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.
Preload `optional` fonts so first-time visitors may use them. Learn more
93
SEO
These checks ensure that your page is following basic search engine
optimization advice. There are many additional factors Lighthouse does not
score here that may affect your search ranking, including performance on
Core Web Vitals. Learn more.
about:blank 34/39
4/19/23, 6:05 AM about:blank
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt
attribute. Learn more.
Failing Elements
img#fatherabvfilter
Format your HTML in a way that enables crawlers to better understand your app’s content.
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.
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
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.
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more.
about:blank 35/39
4/19/23, 6:05 AM about:blank
Descriptive link text helps search engines understand your content. Learn more.
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
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more.
[Link] is valid
If your [Link] file is malformed, crawlers may not be able to understand how you want your website to be crawled or
indexed. Learn more.
hreflang links tell search engines what version of a page they should list in search results for a given language or region.
Learn more.
Canonical links suggest which URL to show in search results. Learn more.
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.
% of Page
Source Selector Font Size
Text
about:blank 36/39
4/19/23, 6:05 AM about:blank
% of Page
Source Selector Font Size
Text
Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more.
Tap targets are sized appropriately — 100% 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.
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.
about:blank 37/39
4/19/23, 6:05 AM about:blank
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.
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn
more.
The browser address bar can be themed to match your site. Learn more.
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.
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
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.
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device.
Learn more.
To reach the most number of users, sites should work across every major browser. Learn more.
about:blank 38/39
4/19/23, 6:05 AM about:blank
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.
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 Apr 19, 2023, 6:04 Emulated Moto G4 with Single page load
AM GMT+5:30 Lighthouse 9.6.8
Initial page load Slow 4G throttling Using Chromium [Link] with
devtools
about:blank 39/39