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 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.lexisnexis.com/css/lndc-styles.css?v=481772548751000	0.0 ms	304.0 KiB
www.lexisnexis.com/images/gateway/gateway-bg.jpg	0.0 ms	201.3 KiB
www.lexisnexis.com/fonts/Lato-Italic.woff2	0.0 ms	191.4 KiB
www.lexisnexis.com/fonts/Lato-Bold.woff2	0.0 ms	180.9 KiB
webanalytics.lexisnexis.com/js/container_lexisnexiscorporate.min.js	7200.0 s	69.8 KiB
cdn.cookielaw.org/scripttemplates/202512.1.0/otBannerSdk.js	86400.0 s	126.0 KiB
www.lexisnexis.com/fonts/lato-regular-400.woff2	0.0 ms	25.8 KiB
www.lexisnexis.com/fonts/lato-regular-300.woff2	0.0 ms	25.1 KiB
www.lexisnexis.com/fonts/lato-black-800.woff2	0.0 ms	25.1 KiB
www.lexisnexis.com/js/modernizr-2.0.js	0.0 ms	16.3 KiB
www.lexisnexis.com/css/gateway-new.css	0.0 ms	5.5 KiB
www.lexisnexis.com/images/gateway/ln-logo.png	0.0 ms	5.0 KiB
cdn.cookielaw.org/consent/3517c230-6d84-4491-9d6b-3108c68fcd94/OtAutoBlock.js	86400.0 s	11.9 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
/logos/c7f35e9f-bc78-43c8-9f0e-7cd83009704c/c0c5f5c0-2a29...	86400.0 s	8.0 KiB
try.abtasty.com/b21d51b3c7a68f1f78c6388542a04d7a.js	30.0 s	3.1 KiB
www.lexisnexis.com/js/gateway-page-visit-new.js	0.0 ms	2.2 KiB
www.lexisnexis.com/images/gateway/sign-in.png	0.0 ms	1.9 KiB
cdn.cookielaw.org/logos/static/powered_by_logo.svg	86400.0 s	2.6 KiB
webanalytics.lexisnexis.com/js/selectorPath.js	7200.0 s	1.2 KiB
www.lexisnexis.com/js/year.js	0.0 ms	887 B

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.

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
www.lexisnexis.com/css/lndc-styles.css?v=481772548751000	304.0 KiB	727 ms
cdn.cookielaw.org/scripttemplates/otSDKStub.js	9.1 KiB	227 ms
www.lexisnexis.com/css/gateway-new.css	5.5 KiB	361 ms
try.abtasty.com/b21d51b3c7a68f1f78c6388542a04d7a.js	3.1 KiB	202 ms

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.1 s

URL	Time Spent
lexisnexis.com/	532 ms
www.lexisnexis.com/	531 ms
www.lexisnexis.com/en-us/gateway.page	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

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: 40 ms 10.1 KiB

URL	Transfer Size	Est Savings
www.lexisnexis.com/js/modernizr-2.0.js	15.6 KiB	10.1 KiB

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: 440 ms 321.9 KiB

URL	Transfer Size	Est Savings
www.lexisnexis.com/css/lndc-styles.css?v=481772548751000	303.4 KiB	303.2 KiB
	21.3 KiB	18.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: 130 ms 184.0 KiB

URL	Transfer Size	Est Savings
cdn.cookielaw.org/scripttemplates/202512.1.0/otBannerSdk.js	125.9 KiB	65.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-T2S8RJ	192.8 KiB	50.9 KiB
try.abtasty.com/b21d51b3c7a68f1f78c6388542a04d7a/main.9cb1223070b764ad8408.js	65.7 KiB	43.8 KiB
webanalytics.lexisnexis.com/js/container_lexisnexiscorporate.min.js	69.4 KiB	23.3 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
body > div.header > h1.logo > img `body > div.header > h1.logo > img`	www.lexisnexis.com/images/gateway/ln-logo.png

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

●Max Potential First Input Delay 90 ms

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

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

●JavaScript execution time 0.3 s

●Minimizes main-thread work 0.7 s

●Avoid long main-thread tasks 1 long task found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 110 ms

●Server Backend Latencies 320 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

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

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
body > div.header > h1.logo > img `body > div.header > h1.logo > img`

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cookie Policy. `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

○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

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

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

●`[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 are distinguishable without relying on color.

●Links have a discernible name

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

○ARIA IDs are unique

○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

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

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

○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

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
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/backend/csp-reports/report	`Failed to load resource: the server responded with a status of 400 ()`
www.lexisnexis.com/en-us/gateway.page	`The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.`
cdn.cookielaw.org/scripttemplates/202512.1.0/otBannerSdk.js line 6, col 24454	`The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.`
cdn.cookielaw.org/scripttemplates/202512.1.0/otBannerSdk.js line 6, col 24454	`The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.`
cdn.cookielaw.org/scripttemplates/202512.1.0/otBannerSdk.js line 6, col 24454	`The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.`
cdn.cookielaw.org/scripttemplates/202512.1.0/otBannerSdk.js line 6, col 24454	`The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.`
	TypeError: Cannot read properties of null (reading 'addEventListener') at <anonymous>:1:112 at <anonymous>:2:483 at https://www.googletagmanager.com/gtm.js?id=GTM-T2S8RJ:1030:429 at uR (https://www.googletagmanager.com/gtm.js?id=GTM-T2S8RJ:1032:31) at Md.tR (https://www.googletagmanager.com/gtm.js?id=GTM-T2S8RJ:1029:92) at Md.<anonymous> (https://www.googletagmanager.com/gtm.js?id=GTM-T2S8RJ:434:187) at k.apply (https://www.googletagmanager.com/gtm.js?id=GTM-T2S8RJ:360:466) at fb (https://www.googletagmanager.com/gtm.js?id=GTM-T2S8RJ:323:719) at eb (https://www.googletagmanager.com/gtm.js?id=GTM-T2S8RJ:323:470) at Md.<anonymous> (https://www.googletagmanager.com/gtm.js?id=GTM-T2S8RJ:384:473)
www.googletagmanager.com/gtm.js?id=GTM-T2S8RJ line 285, col 503	`Uncaught [object Object]`
www.googletagmanager.com/gtm.js?id=GTM-T2S8RJ line 285, col 503	`Uncaught [object Object]`
ajax.googleapis.com/ajax/libs/jquery/3.7.1/jquery.min.js line 1, col 28759	`Uncaught ReferenceError: piTracker is not defined`

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
Content security policy

●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

●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

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
body > div.header > h1.logo > img `body > div.header > h1.logo > img`

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 have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`