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.

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.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:3.925 source:map[column:30333 line:1 type:source-location url:https://www.zohowebstatic.com/sites/zweb/js/common/zcms.js urlProvider:network]]]

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

items: [map[reflowTime:25.351 source:map[type:text value:[unattributed]]] map[reflowTime:1.938 source:map[column:87613 line:0 type:source-location url:https://www.zohowebstatic.com/sites/zweb/js/common/zcms.js urlProvider:network]] map[reflowTime:0.555 source:map[column:87037 line:0 type:source-location url:https://www.zohowebstatic.com/sites/zweb/js/common/zcms.js urlProvider:network]] map[reflowTime:4.274 source:map[column:51681 line:0 type:source-location url:https://www.zohowebstatic.com/sites/zweb/js/common/zcms.js urlProvider:network]] map[reflowTime:1.319 source:map[column:52357 line:0 type:source-location url:https://www.zohowebstatic.com/sites/zweb/js/common/zcms.js urlProvider:network]] map[reflowTime:0.257 source:map[column:52415 line:0 type:source-location url:https://www.zohowebstatic.com/sites/zweb/js/common/zcms.js urlProvider:network]] map[reflowTime:0.234 source:map[column:52479 line:0 type:source-location url:https://www.zohowebstatic.com/sites/zweb/js/common/zcms.js urlProvider:network]] map[reflowTime:0.772 source:map[column:53392 line:0 type:source-location url:https://www.zohowebstatic.com/sites/zweb/js/common/zcms.js urlProvider:network]] map[reflowTime:0.143 source:map[column:54809 line:0 type:source-location url:https://www.zohowebstatic.com/sites/zweb/js/common/zcms.js urlProvider:network]] map[reflowTime:0.075 source:map[column:51703 line:0 type:source-location url:https://www.zohowebstatic.com/sites/zweb/js/common/zcms.js urlProvider:network]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Core-value-banner `div#zw-template-inner > div.zwc-pagewrapper > section.zwc-section-values > img.zwc-img-animate`	/sites/zweb/images/zoho_general_pages/core-value-banner-i...	327.6 KiB	252.9 KiB
Zia `div.zwc-apps-container > div.zwc-apps-iwrap > div.zwc-zia-agents-card > img`	/sites/zweb/images/zoho_general_pages/index/zia-logo-grad...	44.9 KiB	42.0 KiB
Aurian `div.zwc-enterprise-testi > figcaption > div > img`	www.zoho.com/sites/zweb/images/zoho_general_pages/zh-testimonial-poster.png	34.6 KiB	33.5 KiB
div.content-wrap > div.zwc-one-iwrap > figure.zwc-one-testi > ::before `div.content-wrap > div.zwc-one-iwrap > figure.zwc-one-testi > ::before`	www.zohowebstatic.com/sites/zweb/images/zoho_general_pages/zh-newhome-sprite.png	79.7 KiB	19.7 KiB
Paul `figure.zwc-one-testi > figcaption > div > img`	/sites/zweb/images/zoho_general_pages/zh-video-poster-pra...	18.5 KiB	17.4 KiB
	www.zohowebstatic.com/sites/zweb/images/otherbrandlogos/zomato.png	15.8 KiB	15.4 KiB
Paul `figure.zwc-one-testi > figcaption > div > img`	www.zoho.com/sites/zweb/images/zoho_general_pages/zh-video-poster-paul.png	14.3 KiB	13.4 KiB
Aurian `div.zwc-enterprise-testi > figcaption > div > img`	/sites/zweb/images/zoho_general_pages/index/santhosh-iyer...	7.8 KiB	6.8 KiB

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-5-SECTION

nodeLabel: Your life's work, powered by our life's work A unique and powerful software su…

path: 1,HTML,1,BODY,1,MAIN,0,DIV,0,DIV,0,SECTION

selector: main > div#zw-template-inner > div.zwc-pagewrapper > section.zwc-section-banner

snippet: <section class="zwc-section-banner zwc-banner-wrap">

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

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

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
www.zohowebstatic.com/sites/zweb/css/product/zoho_general_pages.css	4.7 KiB
www.zohowebstatic.com/sites/zweb/css/common/zc-footer.css	9.4 KiB
www.zohowebstatic.com/sites/zweb/js/ztm/zoho.js	685 B
www.zohowebstatic.com/sites/zweb/css/common/zohocustom.css	21.0 KiB	443 ms
www.zohowebstatic.com/sites/zweb/css/common/zc-headerfooter-v2.css	12.8 KiB
www.zohowebstatic.com/sites/zweb/css/translation/zoho_general_pages/41687.css	6.5 KiB
www.zohowebstatic.com/sites/zweb/js/common/var_init.js	2.7 KiB
www.zohowebstatic.com/sites/zweb/css/common/zc-footer-v1.css	5.2 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
www.zoho.com/sites/zweb/images/zoho_general_pages/zh-marketplace.png	604800.0 s	234.1 KiB
www.zoho.com/sites/zweb/images/zoho_general_pages/zh-one-poster.png	604800.0 s	79.3 KiB
www.zoho.com/sites/zweb/images/zoho_general_pages/zh-testimonial-poster.png	604800.0 s	34.9 KiB
www.zoho.com/sites/zweb/images/zoho_general_pages/zh-video-poster-paul.png	604800.0 s	14.6 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 715 ms

URL	Time Spent
zoho.com/	715 ms
www.zoho.com/	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: 40 ms 28.6 KiB

URL	Transfer Size	Est Savings
www.zohowebstatic.com/sites/zweb/css/common/zohocustom.css	20.6 KiB	17.1 KiB
/salesiq/styles/floatbutton1_GIFLbol1kJZVrV24d51HLLrd0QNz...	11.7 KiB	11.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: 40 ms 88.4 KiB

URL	Transfer Size	Est Savings
www.zohowebstatic.com/sites/zweb/js/common/zohocustom.js	71.0 KiB	35.4 KiB
salesiq.zoho.in/widget	47.7 KiB	28.4 KiB
cdn-in.pagesense.io/js/7nbagtjv/a63a3daff87f4d33b6cffbe7a949ff5f.js	108.5 KiB	24.6 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 5.9 KiB

URL	Transfer Size	Est Savings
www.zohowebstatic.com/sites/zweb/js/common/zcms.js	36.2 KiB	5.9 KiB

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

●Max Potential First Input Delay 70 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Avoids enormous network payloads Total size was 2,410 KiB

●JavaScript execution time 0.4 s

●Minimizes main-thread work 1.0 s

●Avoid long main-thread tasks 1 long task found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 230 ms

●Server Backend Latencies 200 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

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 require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Amazon `div.content-wrap > div.zwc-brand-wrap > div.zwc-brand-slider > li.zwc-tb-amazon`
KPMG `div.content-wrap > div.zwc-brand-wrap > div.zwc-brand-slider > li.zwc-tb-kpmg`
Renault `div.content-wrap > div.zwc-brand-wrap > div.zwc-brand-slider > li.zwc-tb-renault`
Netflix `div.content-wrap > div.zwc-brand-wrap > div.zwc-brand-slider > li.zwc-tb-netflix`
HP `div.content-wrap > div.zwc-brand-wrap > div.zwc-brand-slider > li.zwc-tb-hp`
Facebook `div.content-wrap > div.zwc-brand-wrap > div.zwc-brand-slider > li.zwc-tb-fb`

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

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

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

●Links have a discernible name

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

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

○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

○No form fields have multiple labels

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

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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

100

Best Practices

●Uses HTTPS

●Avoids deprecated APIs

●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 browser errors logged to the console

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

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

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.

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
www.zoho.com/enterprise/?src=zindex	LEARN MORE
www.zoho.com/blog/general/uae-data-centres-abu-dhabi-dubai-launch.html	Read More

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

○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 are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`