Mobile 375 × 812

Desktop 1440 × 900

Score: 76 / 100
Based on 8 categories, 0 sections
Fast site — your users get a smooth experience.
Several missing protections leave your users and data exposed.
Several issues make your site difficult for assistive technology users.
Well-optimized for search — your content is discoverable.
Solid infrastructure — fast server responses across the board.
Mostly compliant — a few items need attention.
Good content signals with minor gaps.
Reasonable footprint with room for optimization.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
2 button(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
No <main> landmark found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
40 third-party resources (100% of weight)
Performance issues directly impact user engagement and conversion rates.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/122fe45e-67ec-4591-beb4-953f9b8c5817)<a href="https://beavercheck.com/results/122fe45e-67ec-4591-beb4-953f9b8c5817"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwhatsapp.net" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwhatsapp.netThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 4.5s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.
4 barrier(s) likely increasing bounce by ~23%.
Page takes 4.5s to load
+12% bounceUsers abandon at ~3s — you're 2.0s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
Layout shifts during page load
+3% bounceContent movement causes mis-clicks on CTAs and form fields
Fix: Add width/height to images; reserve space for late-loading embeds
No structured data
+2% bounceNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
$600 investment → $3,369/month returns + USD 157,500 risk avoided
$600
6h · 5 findings
$3,369 /mo
~$40,433 / year
USD 157,500
if kept compliant
$100 — in quick wins — start here for the fastest payback
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
6.0 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$13,125 / month at risk
~$157,503 / year if left unfixed
$157,500
+4 more
$0.22 /mo
2708.0 MB/mo × 0.080 USD/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 4 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
3.56 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
4.47 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
10 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.156
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.56 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
5.52 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
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.
Performance issues directly impact user engagement and conversion rates.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Performance issues directly impact user engagement and conversion rates.
| URL | Est Savings |
|---|---|
| static.whatsapp.net/rsrc.php/yN/r/fQtw5exLIdT.woff2 | 75 ms |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| static.whatsapp.net/rsrc.php/v4/yD/r/qDXfTrpu0Qv.js | 100.8 KiB | 600 ms |
| static.whatsapp.net/rsrc.php/v5/yC/l/0,cross/Jld_ox0qHt4.css | 3.2 KiB | |
| static.whatsapp.net/rsrc.php/v5/yT/l/0,cross/2C6Y15M3ulD.css | 19.6 KiB | 150 ms |
| static.whatsapp.net/rsrc.php/v5/yf/l/0,cross/kVqnnGSuZMa.css | 1.9 KiB | 773 ms |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
screenshot of end to end encrypted video call of user connecting with their fam… div#u_0_q_GE > div#u_0_r_YP > picture._9uh7 > img._9v7q | /v/t39.8562-34/314953329_693432345387154_1215169011003584... | 21.6 KiB | 8.3 KiB |
whatsapp user profile image of happy lady laughing div#u_0_13_Sz > div._af05 > picture._9uh7 > img._9v7q | /v/t39.8562-34/659653507_956164453426749_1354931642582727... | 40.6 KiB | 6.4 KiB |
woman in the city stopping to look at the messages on her phone div._ain8 > div._aina > picture._9uh7 > img._9v7q | /v/t39.8562-34/668131880_929782383248177_2928882737729578... | 19.4 KiB | 4.7 KiB |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| whatsapp.net/ | 800 ms |
| www.whatsapp.com/ | 0.0 ms |
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Performance issues directly impact user engagement and conversion rates.
| Element | Layout shift score |
|---|---|
With private messaging and calling, you can be yourself, speak freely and feel … div._2y_d > div#content-wrapper > div._adhc > section._9t2b | 0.154 |
* Data charges may apply. Contact your provider for details. div._9t2c > article._9ta2 > div._9tar > span._9vg3 | 0.002 |
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| static.whatsapp.net/rsrc.php/v5/yT/l/0,cross/2C6Y15M3ulD.css | 18.1 KiB | 15.9 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.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| static.whatsapp.net/rsrc.php/v4/yD/r/qDXfTrpu0Qv.js | 100.5 KiB | 55.1 KiB |
| static.whatsapp.net/rsrc.php/v4/ye/r/GoPsVrX3zqn.js | 81.2 KiB | 47.7 KiB |
| static.whatsapp.net/rsrc.php/v4i7M54/yc/l/en_US-j/J3EtfcjxlpA.js | 39.3 KiB | 30.9 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
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 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 |
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
screenshot of whatsapp group customized to be called best friend group div#u_0_z_8Z > div._af05 > picture._9uh7 > img._9v7q | /v/t39.8562-34/472788114_28309722868643717_39006718000144... |
screenshot of whatsapp business showing an online grocery store with products f… div#u_0_1e_AV > div#u_0_1f_9Z > picture._9uh7 > img._9v7q | /v/t39.8562-34/318716890_590436546220129_8444143897573501... |
whatsapp user profile image of happy lady laughing div#u_0_13_Sz > div._af05 > picture._9uh7 > img._9v7q | /v/t39.8562-34/659653507_956164453426749_1354931642582727... |
screenshot of end to end encrypted video call of user connecting with their fam… div#u_0_s_Vy > div#u_0_t_W6 > picture._9uh7 > img._9v7q | /v/t39.8562-34/473039923_1248309032903788_228546763990592... |
screenshot of whatsapp feature group conversation including photo and message e… div#u_0_10_uP > div#u_0_11_PV > picture._9uh7 > img._9v7q | /v/t39.8562-34/659198996_1263333499311132_110893147561133... |
whatsapp feature showing users status using happy face and heart sticker with l… div#u_0_18_ri > div#u_0_19_gk > picture._9uh7 > img._9v7q | /v/t39.8562-34/312201775_3436222206622878_599206513212171... |
screenshot of end to end encrypted video call of user connecting with their fam… div#u_0_q_GE > div#u_0_r_YP > picture._9uh7 > img._9v7q | /v/t39.8562-34/314953329_693432345387154_1215169011003584... |
bubbles of text saying hello in different languages with individual users icons div#u_0_n_WN > article._9ta2 > picture._9uh7 > img._9v7q | /v/t39.8562-34/472788341_629864479611494_9174171895768642... |
bubbles of text saying hello in different languages with individual users icons div#u_0_j_C4 > article._9ta2 > picture._9uh7 > img._9v7q | /v/t39.8562-34/473051620_1130745678463614_278254744382451... |
WhatsApp Main Page span._afw1 > a._asnw > span._advp > img._afvz | static.whatsapp.net/rsrc.php/yY/r/_mMwO8HKa4V.svg |
WhatsApp Main Logo span._9uog > a._asnw > span._advp > img._aeok | static.whatsapp.net/rsrc.php/yM/r/ys-5GPT4pwS.svg |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div._afvx > div._afvy > div._af8g > button#u_0_2_S7 div._afvx > div._afvy > div._af8g > button#u_0_2_S7 |
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
What we do div._9vd6 > div._9vd5 > div._8l_f > h4 |
These are opportunities to improve keyboard navigation in your application.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Sitemap span._aeom > div._9tar > span > a._asnw |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html#facebook html#facebook |
These items highlight common accessibility best practices.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Download div._9vd6 > div._adhc > div._asz5 > a._aeo8 |
Download div._9tar > span._ae_s > div._asz5 > a._aeo8 |
About us div._9t2j > div._9tar > div._9vd6 > a._asnw |
Contact Us div._9t2j > div._9tar > div._9vd6 > a#contact_us_link_footer |
Apps div._9t2j > div._9tar > div._9vd6 > a._asnw |
Terms & Privacy Policy div._9t2m > span._aeom > div._9tar > a._9vcv |
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Performance issues directly impact user engagement and conversion rates.
| URL | Displayed size | Actual size | Expected size | |
|---|---|---|---|---|
bubbles of text saying hello in different languages with individual users icons div#u_0_j_C4 > article._9ta2 > picture._9uh7 > img._9v7q | /v/t39.8562-34/473051620_1130745678463614_278254744382451... | 298 x 168 | 332 x 187 | 447 x 252 |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
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/yD/r/qDXfTrpu0Qv.js line 322, col 790 |
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.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| www.whatsapp.com/calling | Learn more |
| www.whatsapp.com/privacy | Learn more |
| www.whatsapp.com/community | Learn more |
| www.whatsapp.com/messaging | Learn more |
| business.whatsapp.com/ | Learn more |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.01 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.35 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
0 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.376
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.01 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
1.35 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
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.
Performance issues directly impact user engagement and conversion rates.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Performance issues directly impact user engagement and conversion rates.
| URL | Est Savings |
|---|---|
| static.whatsapp.net/rsrc.php/yN/r/fQtw5exLIdT.woff2 | 70 ms |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| static.whatsapp.net/rsrc.php/v4/yD/r/qDXfTrpu0Qv.js | 100.8 KiB | 80 ms |
| static.whatsapp.net/rsrc.php/v5/yC/l/0,cross/Jld_ox0qHt4.css | 3.2 KiB | |
| static.whatsapp.net/rsrc.php/v5/yf/l/0,cross/kVqnnGSuZMa.css | 1.9 KiB | 220 ms |
| static.whatsapp.net/rsrc.php/v5/yT/l/0,cross/2C6Y15M3ulD.css | 19.6 KiB |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
screenshot of end to end encrypted video call of user connecting with their fam… div#u_0_w_iO > div#u_0_x_/x > picture._9uh7 > img._9v7q | /v/t39.8562-34/472770474_998885868928301_7820026646601892... | 51.3 KiB | 16.0 KiB |
whatsapp feature showing users status using happy face and heart sticker with l… div#u_0_1b_O/ > div#u_0_1c_xB > picture._9uh7 > img._9v7q | /v/t39.8562-34/311869879_1082331725759559_538213680480128... | 20.1 KiB | 15.5 KiB |
whatsapp user profile image of happy lady laughing div#u_0_1a_y5 > div._af05 > picture._9uh7 > img._9v7q | /v/t39.8562-34/659653507_956164453426749_1354931642582727... | 40.6 KiB | 6.4 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| static.whatsapp.net/rsrc.php/v4/yD/r/qDXfTrpu0Qv.js | 100.5 KiB | 55.1 KiB |
| static.whatsapp.net/rsrc.php/v4/ye/r/GoPsVrX3zqn.js | 81.2 KiB | 47.7 KiB |
| static.whatsapp.net/rsrc.php/v4i7M54/yc/l/en_US-j/J3EtfcjxlpA.js | 39.3 KiB | 30.9 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
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 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 |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| static.whatsapp.net/rsrc.php/v5/yT/l/0,cross/2C6Y15M3ulD.css | 18.1 KiB | 14.7 KiB |
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
screenshot of end to end encrypted video call of user connecting with their fam… div#u_0_z_gk > div#u_0_10_cH > picture._9uh7 > img._9v7q | /v/t39.8562-34/473060158_1449917663062833_590860575737065... |
bubbles of text saying hello in different languages with individual users icons div#u_0_t_Fl > article._9ta2 > picture._9uh7 > img._9v7q | /v/t39.8562-34/660428698_2328129864265018_232382178265635... |
Mac native version of WhatsApp highlighting video chats and various messaging c… div._9tar > div._9vd6 > picture._9uh7 > img._9v7q | /v/t39.8562-34/557983832_816108114297284_7708787262743294... |
bubbles of text saying hello in different languages with individual users icons div#u_0_p_On > article._9ta2 > picture._9uh7 > img._9v7q | /v/t39.8562-34/657146264_1235058018697365_245138965546914... |
span._9vf_ > div._af05 > picture._9uh7 > img._9v7q span._9vf_ > div._af05 > picture._9uh7 > img._9v7q | /v/t39.8562-34/319083687_560355302533985_4513178005349338... |
screenshot of end to end encrypted video call of user connecting with their fam… div#u_0_w_iO > div#u_0_x_/x > picture._9uh7 > img._9v7q | /v/t39.8562-34/472770474_998885868928301_7820026646601892... |
screenshot of whatsapp group customized to be called best friend group div#u_0_16_jZ > div._af05 > picture._9uh7 > img._9v7q | /v/t39.8562-34/473285216_1384759809157265_121252201687680... |
screenshot of whatsapp business showing an online grocery store with products f… div#u_0_1l_f+ > div#u_0_1m_Ko > picture._9uh7 > img._9v7q | /v/t39.8562-34/329699257_2856843487782508_780054550541766... |
whatsapp user profile image of happy lady laughing div#u_0_1a_y5 > div._af05 > picture._9uh7 > img._9v7q | /v/t39.8562-34/659653507_956164453426749_1354931642582727... |
screenshot of whatsapp feature group conversation including photo and message e… div#u_0_17_9s > div#u_0_18_rR > picture._9uh7 > img._9v7q | /v/t39.8562-34/659198996_1263333499311132_110893147561133... |
whatsapp feature showing users status using happy face and heart sticker with l… div#u_0_1b_O/ > div#u_0_1c_xB > picture._9uh7 > img._9v7q | /v/t39.8562-34/311869879_1082331725759559_538213680480128... |
example of whatsapp event with multiple attendees going to French Class div#u_0_g_zN > div#u_0_h_TM > picture._9uh7 > img._9v7q | /v/t39.8562-34/656665442_4215181615403350_209439401965278... |
secure text on whatsapp platform reading ready when you are div#u_0_m_jM > div#u_0_n_6/ > picture._9uh7 > img._9v7q | /v/t39.8562-34/657250101_2229945731166928_792335821559596... |
example of text bubble on whatsapp reading still on for studying div#u_0_i_Nw > div#u_0_j_iv > picture._9uh7 > img._9v7q | /v/t39.8562-34/657609706_2270399193448511_279476224734901... |
WhatsApp Main Logo div._9vd6 > a._asnw > span._advp > img._aeok | static.whatsapp.net/rsrc.php/yJ/r/twC7frrXavH.svg |
thumbs up, heart, glasses emoji reaction to a message on whatsapp div#u_0_k_E5 > div#u_0_l_SK > picture._9uh7 > img._9v7q | /v/t39.8562-34/655911721_1293480736049643_682203208397811... |
WhatsApp Main Page span._afw1 > a._asnw > span._advp > img._afvz | static.whatsapp.net/rsrc.php/yY/r/_mMwO8HKa4V.svg |
More information about the performance of your application. These numbers don't directly affect the Performance score.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| whatsapp.net/ | 249 ms |
| www.whatsapp.com/ | 0.0 ms |
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Performance issues directly impact user engagement and conversion rates.
| Element | Layout shift score |
|---|---|
With private messaging and calling, you can be yourself, speak freely and feel … div._2y_d > div#content-wrapper > div._adhc > section._9t2b | 0.348 |
Message privately
Simple, reliable, private messaging and calling for free*, a… div._9t2c > div._9tar > div._9vd6 > article._9ta2 | 0.020 |
example of whatsapp event with multiple attendees going to French Class section._9t2b > div._9t2c > div._9tar > div._9vd6 | 0.008 |
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
What we do div._9vd6 > div._9vd5 > div._8l_f > h4 |
These are opportunities to improve keyboard navigation in your application.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html#facebook html#facebook |
These items highlight common accessibility best practices.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Apps nav._afwe > ul._afwg > li._afn_ > a._9vd5 |
Log in span._ag1l > div#u_0_b_Sj > div._9tar > a._aeo8 |
Download Mac app div._9t2c > div._9tar > div._9vd6 > a._aeo8 |
About us div._9t2j > div._9tar > div._9vd6 > a._asnw |
Contact Us div._9t2j > div._9tar > div._9vd6 > a#contact_us_link_footer |
Apps div._9t2j > div._9tar > div._9vd6 > a._asnw |
Terms & Privacy Policy div._9t2m > span._aeom > div._9tar > a._9vcv |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
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/yD/r/qDXfTrpu0Qv.js line 322, col 790 |
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.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| www.whatsapp.com/calling | Learn more |
| www.whatsapp.com/privacy | Learn more |
| www.whatsapp.com/community | Learn more |
| www.whatsapp.com/messaging | Learn more |
| business.whatsapp.com/ | Learn more |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback