11/17/23, 11:21 AM about:blank

https://www.google.com/search?q=c+programing+notes+disha+computer+institute+pdf&rlz=1C1VDKB_enIN1050IN105…

83 91 76

Performance Accessibility Best SEO PWA

Practices

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

First Contentful Paint Largest Contentful Paint

1.5 s 2.8 s
First Contentful Paint marks the time at which the first Largest Contentful Paint marks the time at which the
text or image is painted. Learn more about the First largest text or image is painted. Learn more about the
Contentful Paint metric. Largest Contentful Paint metric

Total Blocking Time Cumulative Layout Shift

2,710 ms 0
Sum of all time periods between FCP and Time to Cumulative Layout Shift measures the movement of
Interactive, when task length exceeded 50ms, visible elements within the viewport. Learn more
expressed in milliseconds. Learn more about the Total about the Cumulative Layout Shift metric.
Blocking Time metric.

Speed Index

Error!
Chrome didn't collect any screenshots during the
page load. Please make sure there is content visible
on the page, and then try re-running Lighthouse.
(SPEEDINDEX_OF_ZERO)

about:blank 1/35
11/17/23, 11:21 AM about:blank

View Treemap

Show audits relevant to: All FCP LCP TBT CLS

OPPORTUNITIES

Opportunity Estimated Savings

Reduce unused JavaScript 4.54s

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

Show 3rd-party resources (1)

Transfer Potential
URL
Size Savings

Other Google APIs/SDKs Utility 1st Party 1,110.8 KiB 795.9 KiB

…rs=ACT90oGEp…/m=sb_wiz,aa,abd,sywh,syxq,syxr,syxu,syxt,syxv,sy…
513.5 KiB 434.0 KiB
(www.google.com)

…rs=ACT90oGEp…/m=sy4yg,vTw9Fc,syza,syzb,syzc,syzd,DPreE,WlNQGd,…
193.8 KiB 169.7 KiB
(www.google.com)

…ee=cEt90b:ws9Tlc;qddgKe:x4FYXe,d7YSfd;yxTchf:KUM7Z;dtl0hd:lLQW…
309.2 KiB 139.5 KiB
(www.google.com)

…ee=AfeaP:TkrAjf;BMxAGc:E5bFse;BgS6mb:fidj5d;BjwMce:cXX2Wb;CxXA…
94.3 KiB 52.7 KiB
(www.google.com)

Google CDN Cdn 65.4 KiB 46.3 KiB

…ed=1/rs=AA2YrTsZc… (www.gstatic.com) 65.4 KiB 46.3 KiB

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

DIAGNOSTICS

Does not use 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
about adopting passive event listeners.

Source

Other Google APIs/SDKs Utility 1st Party

about:blank 2/35
11/17/23, 11:21 AM about:blank

Source

…ee=cEt90b:ws9Tlc;qddgKe:x4FYXe,d7YSfd;yxTchf:KUM7Z;dtl0hd:lLQW…:413:246 (www.google.com)

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 how to set image
dimensions CLS

URL

Other Google APIs/SDKs Utility 1st Party

img.gb_n

/ogw/AKPQZvxJW…=s64-c-mo (lh3.googleusercontent.com)

Avoid an excessive DOM size — 2,041 elements

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to
avoid an excessive DOM size. TBT

Statistic Element Value

Total DOM Elements 2,041

Maximum DOM Depth span 31

body.srp

Maximum Child Elements 39

Minimize main-thread work — 6.5 s

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

Category Time Spent

Script Evaluation 3,936 ms

about:blank 3/35
11/17/23, 11:21 AM about:blank

Category Time Spent

Other 1,115 ms

Style & Layout 651 ms

Script Parsing & Compilation 428 ms

Parse HTML & CSS 168 ms

Garbage Collection 161 ms

Rendering 57 ms

Reduce JavaScript execution time — 4.3 s

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

Show 3rd-party resources (1)

Total CPU Script Script

URL
Time Evaluation Parse

Other Google APIs/SDKs Utility 1st Party 5,153 ms 3,379 ms 374 ms

…
ee=cEt90b:ws9Tlc;qddgKe:x4FYXe,d7YSfd;yxTchf:KUM7Z;dtl0hd:lLQ 1,760 ms 1,245 ms 52 ms
W… (www.google.com)

…
rs=ACT90oGEp…/m=sb_wiz,aa,abd,sywh,syxq,syxr,syxu,syxt,syxv,sy 1,130 ms 883 ms 132 ms
… (www.google.com)

/search?q=… (www.google.com) 594 ms 80 ms 38 ms

…
ee=AfeaP:TkrAjf;BMxAGc:E5bFse;BgS6mb:fidj5d;BjwMce:cXX2Wb;C 560 ms 457 ms 64 ms
xXA… (www.google.com)

…rs=ACT90oGEp…/m=sy12q,sy12r,sy12s,pfdHGb?
465 ms 442 ms 1 ms
xjs=s3 (www.google.com)

/search?q=… (www.google.com) 292 ms 61 ms 2 ms

…
rs=ACT90oGEp…/m=sy4yg,vTw9Fc,syza,syzb,syzc,syzd,DPreE,WlN 257 ms 131 ms 83 ms
QGd,… (www.google.com)

about:blank 4/35
11/17/23, 11:21 AM about:blank

Total CPU Script Script

URL
Time Evaluation Parse

…
rs=ACT90oGEp…/m=sywo,eX5ure,sy389,msmzHf,sy3ub,GU4Gab,sy 95 ms 81 ms 2 ms
3uc,Xw… (www.google.com)

Unattributable 975 ms 329 ms 0 ms

Unattributable 975 ms 329 ms 0 ms

Google CDN Cdn 325 ms 186 ms 51 ms

…ed=1/rs=AA2YrTsZc… (www.gstatic.com) 325 ms 186 ms 51 ms

Avoid chaining critical requests — 3 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 how to avoid chaining critical requests. FCP LCP

Maximum critical path latency: 959.528 ms

Initial Navigation
/search?q=… (www.google.com)

…v14/4UaGrENHs….woff2 (fonts.gstatic.com) - 119.572 ms, 14.35 KiB

…v14/4UabrENHs….woff2 (fonts.gstatic.com) - 109.089 ms, 14.89 KiB

…ct=zgms/rs=AA2YrTvxO… (www.gstatic.com) - 105.196 ms, 1.66 KiB

User Timing marks and measures — 14 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user
experiences. Learn more about User Timing marks.

Name Type Start Time Duration

fcbyXe Measure 1,036.75 ms 40.25 ms

kDcP9b Measure 1,040.32 ms 35.68 ms

fcbyXe Measure 1,254.58 ms 13.12 ms

kDcP9b Measure 1,258.02 ms 9.08 ms

fcbyXe Measure 2,333.93 ms 38.87 ms

about:blank 5/35
11/17/23, 11:21 AM about:blank

Name Type Start Time Duration

kDcP9b Measure 2,341.18 ms 31.02 ms

SearchAFTStart Mark 242.00 ms

trigger:SearchAFTEnd Mark 772.00 ms

triggerRender_0 Mark 1,036.75 ms

O7jPNb Mark 1,040.32 ms

triggerRender_1 Mark 1,254.58 ms

O7jPNb Mark 1,258.02 ms

triggerRender_2 Mark 2,333.93 ms

O7jPNb Mark 2,341.18 ms

Largest Contentful Paint element — 2,750 ms

This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
LCP

Element

div.VwiC3b.yDYNvb.W8l4ac.lEBKkf

Phase % of LCP Timing

TTFB 16% 450 ms

Load Delay 0% 0 ms

Load Time 0% 0 ms

Render Delay 84% 2,300 ms

Avoid long main-thread tasks — 19 long tasks found

about:blank 6/35
11/17/23, 11:21 AM about:blank

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long
main-thread tasks TBT

Show 3rd-party resources (1)

URL Start Time Duration

Other Google APIs/SDKs Utility 1st Party 3,112 ms

…ee=AfeaP:TkrAjf;BMxAGc:E5bFse;BgS6mb:fidj5d;BjwMce:cXX2Wb;CxXA…
6,937 ms 562 ms
(www.google.com)

…rs=ACT90oGEp…/m=sb_wiz,aa,abd,sywh,syxq,syxr,syxu,syxt,syxv,sy…
10,399 ms 559 ms
(www.google.com)

…rs=ACT90oGEp…/m=sy12q,sy12r,sy12s,pfdHGb?xjs=s3 (www.google.com) 14,203 ms 465 ms

…ee=cEt90b:ws9Tlc;qddgKe:x4FYXe,d7YSfd;yxTchf:KUM7Z;dtl0hd:lLQW…
4,695 ms 442 ms
(www.google.com)

…ee=cEt90b:ws9Tlc;qddgKe:x4FYXe,d7YSfd;yxTchf:KUM7Z;dtl0hd:lLQW…
5,516 ms 156 ms
(www.google.com)

…ee=cEt90b:ws9Tlc;qddgKe:x4FYXe,d7YSfd;yxTchf:KUM7Z;dtl0hd:lLQW…
5,383 ms 133 ms
(www.google.com)

…rs=ACT90oGEp…/m=sy4yg,vTw9Fc,syza,syzb,syzc,syzd,DPreE,WlNQGd,…
12,662 ms 129 ms
(www.google.com)

…ee=cEt90b:ws9Tlc;qddgKe:x4FYXe,d7YSfd;yxTchf:KUM7Z;dtl0hd:lLQW…
11,227 ms 108 ms
(www.google.com)

/search?q=… (www.google.com) 1,571 ms 96 ms

…rs=ACT90oGEp…/m=sywo,eX5ure,sy389,msmzHf,sy3ub,GU4Gab,sy3uc,Xw…
13,060 ms 96 ms
(www.google.com)

…ee=cEt90b:ws9Tlc;qddgKe:x4FYXe,d7YSfd;yxTchf:KUM7Z;dtl0hd:lLQW…
5,672 ms 77 ms
(www.google.com)

/search?q=… (www.google.com) 1,696 ms 75 ms

…ee=cEt90b:ws9Tlc;qddgKe:x4FYXe,d7YSfd;yxTchf:KUM7Z;dtl0hd:lLQW…
5,273 ms 55 ms
(www.google.com)

…ee=cEt90b:ws9Tlc;qddgKe:x4FYXe,d7YSfd;yxTchf:KUM7Z;dtl0hd:lLQW…
5,328 ms 55 ms
(www.google.com)

/search?q=… (www.google.com) 1,771 ms 53 ms

about:blank 7/35
11/17/23, 11:21 AM about:blank

URL Start Time Duration

/search?q=… (www.google.com) 1,824 ms 51 ms

Unattributable 427 ms

Unattributable 1,875 ms 291 ms

Unattributable 5,137 ms 136 ms

Google CDN Cdn 326 ms

…ed=1/rs=AA2YrTsZc… (www.gstatic.com) 3,489 ms 326 ms

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

PASSED AUDITS (29) Hide

Eliminate render-blocking resources

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical
JS/styles. Learn how to eliminate render-blocking resources. FCP LCP

Properly size images

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

Defer offscreen images

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to
interactive. Learn how to defer offscreen images.

Minify CSS

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS. FCP LCP

Minify JavaScript

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript. FCP LCP

Reduce unused CSS

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by
network activity. Learn how to reduce unused CSS. FCP LCP

about:blank 8/35
11/17/23, 11:21 AM about:blank

Efficiently encode images

Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.

Serve images in next-gen formats

Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads
and less data consumption. Learn more about modern image formats.

Enable text compression

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

Preconnect to required origins

Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins.
Learn how to preconnect to required origins. FCP LCP

Initial server response time was short — Root document took 240 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the
Time to First Byte metric. FCP LCP

URL Time Spent

Other Google APIs/SDKs Utility 1st Party 240 ms

/search?q=… (www.google.com) 240 ms

Avoid multiple page redirects

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

Preload key requests

Consider using <link rel=preload> to prioritize fetching resources that are currently requested later in page load. Learn
how to preload key requests. FCP LCP

Use HTTP/2

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

Use video formats for animated content

about:blank 9/35
11/17/23, 11:21 AM about:blank

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 about efficient video formats 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

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 how
to use modern JavaScript TBT

Preload Largest Contentful Paint image

If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more
about preloading LCP elements. LCP

Avoids enormous network payloads — Total size was 1,452 KiB

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

Show 3rd-party resources (3)

Transfer
URL
Size

Other Google APIs/SDKs Utility 1st Party 1,328.2 KiB

…rs=ACT90oGEp…/m=sb_wiz,aa,abd,sywh,syxq,syxr,syxu,syxt,syxv,sy… (www.google.com) 513.5 KiB

…ee=cEt90b:ws9Tlc;qddgKe:x4FYXe,d7YSfd;yxTchf:KUM7Z;dtl0hd:lLQW… (www.google.com) 309.2 KiB

…rs=ACT90oGEp…/m=sy4yg,vTw9Fc,syza,syzb,syzc,syzd,DPreE,WlNQGd,… (www.google.com) 193.8 KiB

…am=GgACAAIEA… (www.google.com) 123.0 KiB

…ee=AfeaP:TkrAjf;BMxAGc:E5bFse;BgS6mb:fidj5d;BjwMce:cXX2Wb;CxXA… (www.google.com) 94.3 KiB

/search?q=… (www.google.com) 88.8 KiB

…rs=ACT90oGEp…/m=sywo,eX5ure,sy389,msmzHf,sy3ub,GU4Gab,sy3uc,Xw… (www.google.com) 5.7 KiB

Google CDN Cdn 65.4 KiB

about:blank 10/35
11/17/23, 11:21 AM about:blank

Transfer
URL
Size

…ed=1/rs=AA2YrTsZc… (www.gstatic.com) 65.4 KiB

Google Fonts Cdn 29.2 KiB

…v14/4UabrENHs….woff2 (fonts.gstatic.com) 14.9 KiB

…v14/4UaGrENHs….woff2 (fonts.gstatic.com) 14.4 KiB

Uses efficient cache policy on static assets — 1 resource found

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

Cache Transfer
URL
TTL Size

Other Google APIs/SDKs Utility 1st Party 1 KiB

/ogw/AKPQZvxJW…=s64-c-mo (lh3.googleusercontent.com) 1d 1 KiB

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 about font-
display. FCP LCP

Minimize third-party usage — Third-party code blocked the main thread for 150 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 how to minimize third-party impact. TBT

Third-Party Transfer Size Main-Thread Blocking Time

Google CDN Cdn 67 KiB 148 ms

…ed=1/rs=AA2YrTsZc… (www.gstatic.com) 65 KiB 148 ms

Google Fonts Cdn 30 KiB 0 ms

…v14/4UabrENHs….woff2 (fonts.gstatic.com) 15 KiB 0 ms

…v14/4UaGrENHs….woff2 (fonts.gstatic.com) 14 KiB 0 ms

AMP Content 1 KiB 0 ms

about:blank 11/35
11/17/23, 11:21 AM about:blank

Third-Party Transfer Size Main-Thread Blocking Time

Google/Doubleclick Ads Ad 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 how to
defer third-parties with a facade. TBT

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 about optimal lazy loading. LCP

Avoid large layout shifts

These DOM elements contribute most to the CLS of the page. Learn how to improve CLS CLS

Avoids document.write()

For users on slow connections, external scripts dynamically injected via document.write() can delay page load by tens of
seconds. Learn how to avoid document.write().

Avoid non-composited animations

Animations which are not composited can be janky and increase CLS. Learn how to avoid non-composited animations 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 about using the viewport meta tag. TBT

Page didn't prevent back/forward cache restoration

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache)
can speed up these return navigations. Learn more about the bfcache

83

Accessibility

about:blank 12/35
11/17/23, 11:21 AM about:blank

These checks highlight opportunities to improve the accessibility of your

web app. Automatic detection can only detect a subset of issues and does
not guarantee the accessibility of your web app, so manual testing is also
encouraged.

ARIA

[role]s are not 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 about ARIA roles and required parent element.

Failing Elements

div.qR29te

div.qR29te

div.qR29te

div.qR29te

div.qR29te

div.qR29te

about:blank 13/35
11/17/23, 11:21 AM about:blank

Failing Elements

div.qR29te

div.qR29te

div.qR29te

div.qR29te

div.qR29te

div.qR29te

button, link, and menuitem elements do not 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 how to make command elements more accessible.

Failing Elements

span.J1IHKc.z1asCe.A2gxLb

about:blank 14/35
11/17/23, 11:21 AM about:blank

Failing Elements

a.VknLRd

ARIA input fields do not 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 about input field labels.

Failing Elements

div.a4bIc

Values assigned to role="" are not valid ARIA roles.

ARIA roles enable assistive technologies to know the role of each element on the web page. If the role values are
misspelled, not existing ARIA role values, or abstract roles, then the purpose of the element will not be communicated to
users of assistive technologies. Learn more about ARIA roles.

Failing Elements

a.cz3goc.BmP5tf

a.cz3goc.BmP5tf

a.cz3goc.BmP5tf

a.cz3goc.BmP5tf

about:blank 15/35
11/17/23, 11:21 AM about:blank

Failing Elements

a.cz3goc.BmP5tf

a.cz3goc.BmP5tf

a.cz3goc.BmP5tf

a.cz3goc.BmP5tf

a.cz3goc.BmP5tf

a.cz3goc.BmP5tf

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.

NAMES AND LABELS

Buttons do not have an accessible name

about:blank 16/35
11/17/23, 11:21 AM about:blank

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 how to make buttons more accessible.

Failing Elements

button#Q7Ulpb.FJoqsb

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.

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 about heading order.

Failing Elements

h3

These are opportunities to improve keyboard navigation in your application.

ADDITIONAL ITEMS TO MANUALLY CHECK (10) Hide

Interactive controls are keyboard focusable

Custom interactive controls are keyboard focusable and display a focus indicator. Learn how to make custom controls
focusable.

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 how to decorate interactive elements with affordance hints.

The page has a logical tab order

Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more about
logical tab ordering.

about:blank 17/35
11/17/23, 11:21 AM about:blank

Visual order on the page follows DOM order

DOM order matches the visual order, improving navigation for assistive technology. Learn more about DOM and visual
ordering.

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 how to avoid focus traps.

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 how to direct focus to new
content.

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 about landmark elements.

Offscreen content is hidden from assistive technology

Offscreen content is hidden with display: none or aria-hidden=true. Learn how to properly hide offscreen content.

Custom controls have associated labels

Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more about custom
controls and labels.

Custom controls have ARIA roles

Custom interactive controls have appropriate ARIA roles. Learn how to add roles to custom controls.

These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility
review.

PASSED AUDITS (24) Hide

[aria-*] attributes match their roles

Each ARIA role supports a specific subset of aria-* attributes. Mismatching these invalidates the aria-* attributes. Learn
how to match ARIA attributes to their roles.

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

about:blank 18/35
11/17/23, 11:21 AM about:blank

Learn how aria-hidden affects the document body.

[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 roles
and required attributes.

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 about
roles and required children elements.

[aria-*] attributes have valid values

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values
for ARIA attributes.

[aria-*] attributes are valid and not misspelled

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA
attributes.

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 about the alt attribute.

[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 about the viewport meta tag.

Elements with role="dialog" or role="alertdialog" have accessible names.

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these
elements. Learn how to make ARIA dialog elements more accessible.

[aria-hidden="true"] elements do not 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 how aria-hidden affects focusable elements.

[role] values are valid

about:blank 19/35
11/17/23, 11:21 AM about:blank

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA
roles.

Elements with the role=text attribute do not have focusable descendents.

Adding role=text around a text node split by markup enables VoiceOver to treat it as one phrase, but the element's
focusable descendents will not be announced. Learn more about the role=text attribute.

Background and foreground colors have a sufficient contrast ratio

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

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 about document titles.

[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 how to fix
duplicate ids.

<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 about the lang attribute.

<html> element has a valid value for its [lang] attribute

Specifying a valid BCP 47 language helps screen readers announce text properly. Learn how to use the lang attribute.

Elements with visible text labels have matching accessible names.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users.
Learn more about accessible names.

Form elements have associated labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about
form element labels.

Links are distinguishable without relying on color.

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for
users with low vision. Learn how to make links distinguishable.

about:blank 20/35
11/17/23, 11:21 AM about:blank

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 how to make links accessible.

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 about the tabindex attribute.

[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
how to use the lang attribute.

Image elements do not have [alt] attributes that are redundant text.

Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text
adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more
about the alt attribute.

NOT APPLICABLE (29) 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
about access keys.

ARIA meter elements have accessible names

When a meter 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 how to name meter elements.

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 how to label progressbar elements.

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 about toggle fields.

ARIA tooltip elements have accessible names

about:blank 21/35
11/17/23, 11:21 AM about:blank

When a tooltip 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 how to name tooltip elements.

ARIA treeitem elements have accessible names

When a treeitem 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 labeling treeitem elements.

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 about bypass
blocks.

<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 how to
structure definition lists correctly.

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 how to structure definition lists correctly.

ARIA IDs are unique

The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn
how to fix duplicate ARIA IDs.

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 how to use form labels.

<frame> or <iframe> elements have a title

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.

If the webpage does not specify a consistent language, then the screen reader might not announce the page's text correctly.
Learn more about the lang attribute.

Input buttons have discernible text.

Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input
button. Learn more about input buttons.

about:blank 22/35
11/17/23, 11:21 AM about:blank

<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 about input image alt text.

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
about proper list structure.

List items (<li>) are contained within <ul>, <ol> or <menu> parent elements

Screen readers require list items (<li>) to be contained within a parent <ul>, <ol> or <menu> to be announced properly.
Learn more about proper list structure.

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 about the refresh meta tag.

<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 about alt text for object elements.

Select elements have associated label elements.

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the
select element.

Skip links are focusable.

Including a skip link can help users skip to the main content to save time. Learn more about skip links.

Tables have different content in the summary attribute and <caption>.

The summary attribute should describe the table structure, while <caption> should have the onscreen title. Accurate table
mark-up helps users of screen readers. Learn more about summary and caption.

Tables use <caption> instead of cells with the [colspan] attribute to indicate a caption.

Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead
of cells with the [colspan] attribute may improve the experience for screen reader users. Learn more about captions.

about:blank 23/35
11/17/23, 11:21 AM about:blank

<td> elements in a large <table> have one or more table headers.

Screen readers have features to make navigating tables easier. Ensuring that <td> elements in a large table (3 or more
cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more
about table headers.

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 about the headers
attribute.

<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 about table headers.

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

Document has a main landmark.

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

Touch targets have sufficient size and spacing.

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the
targets. Learn more about touch targets.

91

Best Practices

USER EXPERIENCE

Serves images with low resolution

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how
to provide responsive images.

about:blank 24/35
11/17/23, 11:21 AM about:blank

Displayed Actual Expected

URL
size size size

data:image/png;base64,iVBORw0KGgoA
AAANSUhEUgAAAGgAAACOCAMAAAD 104 x 142 104 x 142 156 x 213
q3…

img#dimg_1.YQ4gaf

GENERAL

Issues were logged 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 for more
details on each issue.

Issue type

Cookie

/measurement?jaid=AJHaeXI4g…&jaidet=20009 (www.googleadservices.com)

Detected JavaScript libraries

All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.

Name Version

Boq

Wiz

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 about source maps.

URL Map URL

Other Google APIs/SDKs Utility 1st Party

about:blank 25/35
11/17/23, 11:21 AM about:blank

URL Map URL

…
rs=ACT90oGEp…/m=sy4yg,vTw9Fc,syza,syzb,syzc,syzd,DPreE,WlN
QGd,… (www.google.com)

Large JavaScript file is missing a source map

…
rs=ACT90oGEp…/m=sb_wiz,aa,abd,sywh,syxq,syxr,syxu,syxt,syxv,sy
… (www.google.com)

Large JavaScript file is missing a source map

…
ee=cEt90b:ws9Tlc;qddgKe:x4FYXe,d7YSfd;yxTchf:KUM7Z;dtl0hd:lLQ
W… (www.google.com)

Large JavaScript file is missing a source map

PASSED AUDITS (10) 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 HTTPS.

Avoids deprecated APIs

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

Allows users to paste into input fields

Preventing input pasting is a bad practice for the UX, and weakens security by blocking password managers.Learn more
about user-friendly input fields.

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 about the geolocation permission.

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 responsibly getting permission for notifications.

about:blank 26/35
11/17/23, 11:21 AM about:blank

Displays images with correct aspect ratio

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

Page has the HTML doctype

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

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 about declaring the character encoding.

Avoids unload event listeners

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 about unload event listeners

No browser errors 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 about this errors in console diagnostic audit

NOT APPLICABLE (2) Hide

Ensure CSP is effective against XSS attacks

A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use
a CSP to prevent XSS

Fonts with font-display: optional are preloaded

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

76

SEO
These checks ensure that your page is following basic search engine
optimization advice. There are many additional factors Lighthouse does not
score here that may affect your search ranking, including performance on
Core Web Vitals. Learn more about Google Search Essentials.

about:blank 27/35
11/17/23, 11:21 AM about:blank

CONTENT BEST PRACTICES

Document does not have a meta description

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta
description.

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

CRAWLING AND INDEXING

Links are not 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 how to make links crawlable

Uncrawlable Link

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

about:blank 28/35
11/17/23, 11:21 AM about:blank

Uncrawlable Link

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

about:blank 29/35
11/17/23, 11:21 AM about:blank

Uncrawlable Link

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

about:blank 30/35
11/17/23, 11:21 AM about:blank

Uncrawlable Link

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

a.JSSGf

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
about crawler directives.

about:blank 31/35
11/17/23, 11:21 AM about:blank

Blocking Directive Source

/robots.txt:2:0 (www.google.com)

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

MOBILE FRIENDLY

Tap targets are not sized appropriately — 98% appropriately sized tap targets

Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be
easy enough to tap without overlapping onto other elements. Learn more about tap targets.

Tap Target Size Overlapping Target

div.NhRr3b.ff76ob div.dnXCYb

68x40

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn how to
make pages mobile-friendly.

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 about
Structured Data.

Run these additional validators on your site to check additional SEO best practices.

PASSED AUDITS (9) 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 about using the viewport meta tag. 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 about document titles.

about:blank 32/35
11/17/23, 11:21 AM about:blank

Page has successful HTTP status code

Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more about HTTP status codes.

Links have descriptive text

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

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 about robots.txt.

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 about the alt attribute.

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

Document uses legible font sizes — 99.96% 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 about legible font sizes.

Source Selector % of Page Text Font Size

Other Google APIs/SDKs Utility 1st Party

/search?q=…:33:9463 (www.google.com) .NaCKVc 0.03% 10px

/search?q=…:35:76468 (www.google.com) .oMhMse 0.01% 8px

Unattributable

Legible text 99.96% ≥ 12px

Document avoids plugins

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

about:blank 33/35
11/17/23, 11:21 AM about:blank

NOT APPLICABLE (1) Hide

Document has a valid rel=canonical

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

PWA
These checks validate the aspects of a Progressive Web App. Learn what
makes a good Progressive Web App.

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 about manifest
installability requirements.

Failure reason

Page has no manifest <link> URL

PWA OPTIMIZED

Is not configured for a custom splash screen Failures: No manifest was fetched.

A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn
more about splash screens.

Does not set a theme color for the address bar.

Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.

The browser address bar can be themed to match your site. Learn more about theming the address bar.

Content is sized correctly for the viewport

about:blank 34/35
11/17/23, 11:21 AM about:blank

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 how to size content for the viewport.

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 about using the viewport meta tag. TBT

Manifest doesn't have a maskable icon No manifest was fetched

A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device.
Learn about maskable manifest icons.

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 about cross-browser compatibility.

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 about page transitions.

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 about providing deep links.

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 Nov 17, 2023, Emulated Moto G Power with Single page load
11:19 AM GMT+5:30 Lighthouse 11.1.0
Initial page load Slow 4G throttling Using Chromium 119.0.0.0 with
devtools

Generated by Lighthouse 11.1.0 | File an issue

about:blank 35/35