Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:108.97 source:map[type:text value:[unattributed]]]]

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

value: no origins were preconnected

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
/rsrc.php/v5/yd/l/0,cross/I3Bnu8ALToVKkmsA6qiUsNOB_OY8k1K...	189.2 KiB	427 ms

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

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 130 ms 179.6 KiB

URL	Transfer Size	Est Savings
/rsrc.php/v5/yd/l/0,cross/I3Bnu8ALToVKkmsA6qiUsNOB_OY8k1K...	187.7 KiB	179.6 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.3 s 4.3 MiB

URL	Transfer Size	Est Savings
/rsrc.php/v4iwfC4/yj/l/en_US-j/kUWGbmOEOU5EgxASlXkeSEWoIA...	1.3 MiB	1.2 MiB
static.whatsapp.net/rsrc.php/v4i8re4/yt/l/en_US-j/xQeBZDC4Fg1.js	730.8 KiB	650.3 KiB
/rsrc.php/v4iz7c4/yQ/l/en_US-j/1WF84XxOFCz1sKbrXy2BHR5S6j...	834.9 KiB	587.4 KiB
/rsrc.php/v4iMfe4/yU/l/en_US-j/U5KosiEwdJz21XH6px9ckP0Dr5...	509.6 KiB	389.4 KiB
static.whatsapp.net/rsrc.php/v4iiwh4/yN/l/en_US-j/BSsE-fUD1tJ.js	404.4 KiB	360.3 KiB
static.whatsapp.net/rsrc.php/v4/yx/r/mm9GGRMf3SB.js	224.6 KiB	201.5 KiB
static.whatsapp.net/rsrc.php/v4iGGx4/yn/l/en_US-j/DUhYsAsD5JY.js	209.0 KiB	190.1 KiB
static.whatsapp.net/rsrc.php/v4iM2P4/yU/l/en_US-j/Yh7oVDmXa5f.js	187.0 KiB	164.5 KiB
static.whatsapp.net/rsrc.php/v4isWu4/y0/l/en_US-j/0nxw9UfdA7x.js	166.3 KiB	152.4 KiB
static.whatsapp.net/rsrc.php/v4ipy44/yy/l/en_US-j/6AGj8JMNZdZ.js	135.1 KiB	123.5 KiB
static.whatsapp.net/rsrc.php/v4iTVp4/yw/l/en_US-j/FJ0UhBRYlON.js	136.3 KiB	115.9 KiB
/rsrc.php/v4/yX/r/6XAglkoVXjF5SP815S78jCXCeRHSjJ3XszSzQ0V...	118.9 KiB	62.8 KiB
/rsrc.php/v4im2R4/yy/l/en_US-j/wzFU6ZzSqKe66SHGxAeHL9lU04...	76.7 KiB	57.5 KiB
static.whatsapp.net/rsrc.php/v4/yA/r/yNZV7jdVFoC.js	76.6 KiB	34.8 KiB
static.whatsapp.net/rsrc.php/v4/yF/r/ODeFkUjI7ok.js	79.7 KiB	33.1 KiB
/rsrc.php/v4iHys4/yu/l/en_US-j/3eAfZ4uZlGxRHMjINyTyLn86zb...	42.1 KiB	30.6 KiB

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
static.whatsapp.net/rsrc.php/v4/yA/r/yNZV7jdVFoC.js	799 ms	765 ms	5.2 ms
/rsrc.php/v4iz7c4/yQ/l/en_US-j/1WF84XxOFCz1sKbrXy2BHR5S6j...	546 ms	428 ms	76 ms
web.whatsapp.com/	276 ms	12 ms	0.2 ms
Unattributable	168 ms	46 ms	0.0 ms
/rsrc.php/v4iwfC4/yj/l/en_US-j/kUWGbmOEOU5EgxASlXkeSEWoIA...	155 ms	14 ms	141 ms
static.whatsapp.net/rsrc.php/v4i8re4/yt/l/en_US-j/xQeBZDC4Fg1.js	131 ms	42 ms	85 ms
static.whatsapp.net/rsrc.php/v4iiwh4/yN/l/en_US-j/BSsE-fUD1tJ.js	59 ms	3.4 ms	56 ms
/rsrc.php/v4iMfe4/yU/l/en_US-j/U5KosiEwdJz21XH6px9ckP0Dr5...	54 ms	7.7 ms	44 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	1.4 s
Script Parsing & Compilation	603 ms
Other	264 ms
Style & Layout	138 ms
Garbage Collection	67 ms
Parse HTML & CSS	33 ms
Rendering	29 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
The page has an unload handler in the main frame.	Actionable
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable
Back/forward cache is disabled because WebSocket has been used.	Not actionable

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/rsrc.php/v4iwfC4/yj/l/en_US-j/kUWGbmOEOU5EgxASlXkeSEWoIA...	1.3 MiB
/rsrc.php/v4iz7c4/yQ/l/en_US-j/1WF84XxOFCz1sKbrXy2BHR5S6j...	835.1 KiB
static.whatsapp.net/rsrc.php/v4i8re4/yt/l/en_US-j/xQeBZDC4Fg1.js	731.1 KiB
/rsrc.php/v4iMfe4/yU/l/en_US-j/U5KosiEwdJz21XH6px9ckP0Dr5...	509.9 KiB
static.whatsapp.net/rsrc.php/v4iiwh4/yN/l/en_US-j/BSsE-fUD1tJ.js	404.5 KiB
static.whatsapp.net/rsrc.php/v4/yx/r/mm9GGRMf3SB.js	224.8 KiB
static.whatsapp.net/rsrc.php/v4iGGx4/yn/l/en_US-j/DUhYsAsD5JY.js	209.2 KiB
static.whatsapp.net/rsrc.php/yy/r/s3KknyKHL5v.woff2	205.0 KiB
/rsrc.php/v5/yd/l/0,cross/I3Bnu8ALToVKkmsA6qiUsNOB_OY8k1K...	189.2 KiB
static.whatsapp.net/rsrc.php/v4iM2P4/yU/l/en_US-j/Yh7oVDmXa5f.js	187.1 KiB

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 57 user timings

●Avoid long main-thread tasks 11 long tasks found

●Avoid non-composited animations 3 animated elements found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 70 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 180 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○LCP request discovery

Accessibility

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

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 Scan the QR code with your phone's camera 2 Tap the link to open WhatsApp 3 … `div.x1c4vz4f > div.x1c4vz4f > div.x1c4vz4f > ol#link-device-instructions-list`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

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

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

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

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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

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

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○Heading elements appear in a sequentially-descending order

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○Links have a discernible name

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

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

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

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	static.whatsapp.net/rsrc.php/v4/yA/r/yNZV7jdVFoC.js line 247, col 368

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
static.whatsapp.net/rsrc.php/v4/yA/r/yNZV7jdVFoC.js line 84, col 566	`ErrorUtils caught an error: [storage] storage bucket persistence denied (aquire-persistent-storage-denied) Subsequent non-fatal errors won't be logged; see https://fburl.com/debugjs. [object Object]`

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

100

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.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○Image elements have `[alt]` attributes