Lighthouse Mobile

· 0 checks — Mobile 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.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: This is an image that represents WhatsApp in large screen

path: 1,HTML,1,BODY,0,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,IMG

selector: div.x1c4vz4f > div.x1c4vz4f > div.x1c4vz4f > img.xh8yej3

snippet: <img class="xh8yej3" alt="This is an image that represents WhatsApp in large screen" src="https://static.whatsapp.net/rsrc.php/yu/r/3IkZnQ5TIHA.webp">

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/ya/l/0,cross/b8XlL3jdSUdA7PQro9bG3Rlwij8nbyz...	236.8 KiB	1.9 s

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 899 ms

URL	Time Spent
web.whatsapp.com/	899 ms
web.whatsapp.com/mobile/	0.0 ms

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: 1.2 s 217.3 KiB

URL	Transfer Size	Est Savings
/rsrc.php/v5/ya/l/0,cross/b8XlL3jdSUdA7PQro9bG3Rlwij8nbyz...	236.5 KiB	217.3 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: 3.3 s 639.7 KiB

URL	Transfer Size	Est Savings
static.whatsapp.net/rsrc.php/v4/yS/r/DXGWA68xwJZ.js	248.9 KiB	241.5 KiB
static.whatsapp.net/rsrc.php/v4iSfE4/y0/l/en_GB-j/1YNmnQSA7gy.js	141.3 KiB	124.8 KiB
static.whatsapp.net/rsrc.php/v4/yJ/r/Wl_HC4ZDPfu.js	124.1 KiB	122.9 KiB
static.whatsapp.net/rsrc.php/v4/yV/r/ce-O1eEeZ9o.js	77.7 KiB	44.8 KiB
static.whatsapp.net/rsrc.php/v4/yP/r/TmE3jnttQmq.js	83.1 KiB	43.2 KiB
static.whatsapp.net/rsrc.php/v4ijFT4/yf/l/en_GB-j/dl1FlK37LML.js	40.0 KiB	35.8 KiB
static.whatsapp.net/rsrc.php/v4/yy/r/Owo1GF5ZPg0.js	27.2 KiB	26.8 KiB

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
This is an image that represents WhatsApp in large screen `div.x1c4vz4f > div.x1c4vz4f > div.x1c4vz4f > img.xh8yej3`	static.whatsapp.net/rsrc.php/yu/r/3IkZnQ5TIHA.webp

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

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 60 ms

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,245 KiB

●User Timing marks and measures 54 user timings

●JavaScript execution time 0.4 s

●Minimizes main-thread work 0.9 s

●Avoid long main-thread tasks 4 long tasks found

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 100 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid non-composited animations

100

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.

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

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

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○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

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

○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

○`[role]` values are valid

○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

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

○Input buttons have discernible text.

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

○Form elements have associated labels

○Links are distinguishable without relying on color.

○Links have a discernible name

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○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

Browser Compatibility

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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/yV/r/ce-O1eEeZ9o.js line 238, col 362

●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

●No browser errors logged to the console

●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

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.

Crawling and 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
`https://web.whatsapp.com/robots.txt`

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

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

○Structured data is valid

●Document has a `<title>` element

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`