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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	40 ms

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:0.653 source:map[column:488 line:121 type:source-location url:https://emt.gartnerweb.com/ngw/syspath-etc.clientlibs/emt/clientlibs/dependencies.min.826812b693b4ac1c6825032dd6fb6eb2.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:21.346 source:map[type:text value:[unattributed]]] map[reflowTime:0.27 source:map[column:58 line:153 type:source-location url:https://emt.gartnerweb.com/ngw/syspath-etc.clientlibs/emt/clientlibs/dependencies.min.826812b693b4ac1c6825032dd6fb6eb2.js urlProvider:network]] map[reflowTime:0.383 source:map[column:336 line:213 type:source-location url:https://emt.gartnerweb.com/ngw/syspath-etc.clientlibs/emt/clientlibs/dependencies.min.826812b693b4ac1c6825032dd6fb6eb2.js urlProvider:network]]]

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

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
cdn.vidyard.com/thumbnails/48964164/w0sDGxsgDJKfqFstmjOB9Q.png	0.0 ms	60.1 KiB
cdn.vidyard.com/thumbnails/43906426/Rem9CUvfaaRYkw8k_tXo4Q.png	0.0 ms	43.4 KiB
cdn.vidyard.com/thumbnails/43906426/Rem9CUvfaaRYkw8k_tXo4Q.png	0.0 ms	43.4 KiB
www.gartner.com/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/main.js?	14400.0 s	13.4 KiB
emt.gartnerweb.com/assets.calendly.com/assets/external/widget.js	43200.0 s	4.4 KiB
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 KiB
/a?id=AW-780045268&v=3&t=t&pid=1451469538&gtm=45be64h1v86...	0.0 ms	11 B
/a?id=AW-780045268&v=3&t=t&pid=1451469538&gtm=45be64h1v86...	0.0 ms	11 B
/a?id=AW-780045268&v=3&t=t&pid=1451469538&gtm=45be64h1v86...	0.0 ms	11 B
/a?id=AW-780045268&v=3&t=t&pid=1451469538&gtm=45be64h1v86...	0.0 ms	11 B
/a?id=AW-780045268&v=3&t=t&pid=1451469538&gtm=45be64h1v86...	0.0 ms	11 B
/a?id=AW-780045268&v=3&t=t&pid=1451469538&gtm=45be64h1v86...	0.0 ms	11 B

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
div.vidyard-player-container > div.vidyard-lightbox-thumbnail > div.vidyard-lightbox-centering > img.vidyard-lightbox-image `div.vidyard-player-container > div.vidyard-lightbox-thumbnail > div.vidyard-lightbox-centering > img.vidyard-lightbox-image`	cdn.vidyard.com/thumbnails/48964164/w0sDGxsgDJKfqFstmjOB9Q.png	59.7 KiB	26.5 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: 1.0 s

URL	Time Spent
gartner.com/	817 ms
www.gartner.com/	225 ms
www.gartner.com/en	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: 190 ms 136.0 KiB

URL	Transfer Size	Est Savings
/ngw/syspath-etc.clientlibs/emt/clientlibs/components/all...	140.6 KiB	136.0 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: 110 ms 947.2 KiB

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.8 KiB	244.4 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.8 KiB	176.6 KiB
/ngw/syspath-etc.clientlibs/emt/clientlibs/components/mar...	84.0 KiB	75.6 KiB
www.googletagmanager.com/gtag/destination?id=AW-16748165379&cx=c&gtm=4e64h1	150.3 KiB	73.0 KiB
www.googletagmanager.com/gtag/destination?id=AW-780045268&cx=c&gtm=4e64h1	145.1 KiB	69.2 KiB
www.googletagmanager.com/gtag/destination?id=AW-653925177&cx=c&gtm=4e64h1	134.1 KiB	68.8 KiB
www.googletagmanager.com/gtag/js?id=G-R1W5CE5FEV&cx=c&gtm=4e64h1	175.2 KiB	68.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-5398QBF&gtm=4e64h1	153.8 KiB	60.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-WWNT3B3	207.2 KiB	54.2 KiB
www.gartner.com/en/ruxitagentjs_A7NVfhqrux_10317250630095842.js	67.7 KiB	30.7 KiB
/ngw/syspath-etc.clientlibs/emt/clientlibs/dependencies.m...	53.3 KiB	26.0 KiB

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
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	362.4 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-WWNT3B3	207.5 KiB
www.googletagmanager.com/gtag/js?id=G-R1W5CE5FEV&cx=c&gtm=4e64h1	175.3 KiB
www.googletagmanager.com/gtm.js?id=GTM-5398QBF&gtm=4e64h1	153.9 KiB
www.googletagmanager.com/gtag/destination?id=AW-16748165379&cx=c&gtm=4e64h1	150.3 KiB
www.googletagmanager.com/gtag/destination?id=AW-780045268&cx=c&gtm=4e64h1	145.1 KiB
/ngw/syspath-etc.clientlibs/emt/clientlibs/components/all...	141.0 KiB
assets.vidyard.com/play/js/805-db264df0881e2f6a7c10cb10bc1772ff.js	134.9 KiB
www.googletagmanager.com/gtag/destination?id=AW-653925177&cx=c&gtm=4e64h1	134.1 KiB

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
div.full-text-wrapper > div.image-wrapper > picture > img.image `div.full-text-wrapper > div.image-wrapper > picture > img.image`	/ngw/commonassets/images/build-graphics/homepage-test/hyp...

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

●Max Potential First Input Delay 110 ms

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 7 user timings

●JavaScript execution time 1.2 s

●Minimizes main-thread work 1.8 s

●Avoid long main-thread tasks 6 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 200 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 180 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

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

Navigation

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
How CIOs Should Reinvent IT for the AI Age `div.text > div > div.headline > h4.h4`

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.full-text-wrapper > div.image-wrapper > picture > img.image `div.full-text-wrapper > div.image-wrapper > picture > img.image`

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.

Best practices

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.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
or call `ul.nav > li.bac-btn-container > p.dial-text > a`
+34919018119 `ul.nav > li.bac-btn-container > p.dial-text > a.InfinityNumber`

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○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

●Form elements have associated labels

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

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

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

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

●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

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

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●All heading elements contain content.

●Identical links have the same purpose.

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

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

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

○Uses ARIA roles only on compatible elements

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

○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
SharedStorage	www.gartner.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	www.gartner.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	www.gartner.com/cdn-cgi/challenge-platform/scripts/jsd/main.js

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
emt.gartnerweb.com/assets.calendly.com/assets/external/widget.css	`Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Blocked by cross-origin policy

●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

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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.gartner.com/en/products/executive-programs	Learn More

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.full-text-wrapper > div.image-wrapper > picture > img.image `div.full-text-wrapper > div.image-wrapper > picture > img.image`

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

Crawling and Indexing

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Back … `div.footer > div.flex-container > div.cta-container > a.back-button`

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

○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

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid