Lighthouse Mobile
· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.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.
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
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.
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.
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.
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 |
|---|---|---|
| www.lexisnexis.com/css/lndc-styles.css?v=481772548751000 | 304.0 KiB | 2.3 s |
| cdn.cookielaw.org/scripttemplates/otSDKStub.js | 0 B | 780 ms |
| www.lexisnexis.com/css/gateway-new.css | 5.5 KiB | |
| try.abtasty.com/b21d51b3c7a68f1f78c6388542a04d7a.js | 3.1 KiB | 752 ms |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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.
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 |
|---|---|
| lexisnexis.com/ | 1.1 s |
| www.lexisnexis.com/ | 883 ms |
| www.lexisnexis.com/en-us/gateway.page | 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 |
|---|---|
LEGAL & PROFESSIONAL SOLUTIONS
For law firms, corporations, government agencie… body > div.vcenter > div#wrapper > div.box | 0.103 |
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.lexisnexis.com/css/lndc-styles.css?v=481772548751000 | 303.4 KiB | 303.3 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Performance issues directly impact user engagement and conversion rates.
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Performance issues directly impact user engagement and conversion rates.
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 3.9 s |
| Other | 961 ms |
| Script Parsing & Compilation | 609 ms |
| Style & Layout | 203 ms |
| Parse HTML & CSS | 158 ms |
| Garbage Collection | 121 ms |
| Rendering | 24 ms |
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.lexisnexis.com/js/modernizr-2.0.js | 15.6 KiB | 10.1 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
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 | |
|---|---|
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.
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.
Contrast
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
VISIT SITE div#wrapper > div.box > a.content-l > span#_GW_Legal_RM_ |
VISIT SITE div#wrapper > div.box > a.content-r > span#_GW_Risk_RM_ |
These are opportunities to improve the legibility of your content.
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.
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.
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.
Informational: a Permissions-Policy directive showing feature -> allowed origins.
Source: MDN Permissions-Policy
| Failing Elements |
|---|
head > meta#viewport head > meta#viewport |
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.js html.js |
These items highlight common accessibility best practices.
Best Practices
User Experience
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 | |
|---|---|---|---|---|
body > div.header > h1.logo > img body > div.header > h1.logo > img | www.lexisnexis.com/images/gateway/ln-logo.png | 173 x 39 | 173 x 39 | 260 x 59 |
General
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 |
|---|---|
| AttributionReporting | line 2, col 436 |
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Failed to load resource: net::ERR_NAME_NOT_RESOLVED | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
Failed to load resource: the server responded with a status of 400 () | |
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 |
Uncaught SyntaxError: Unexpected identifier 'content' | |
Uncaught SyntaxError: Unexpected identifier 'content' | |
Uncaught SyntaxError: Unexpected identifier 'content' | |
Uncaught SyntaxError: Unexpected identifier 'content' | |
Uncaught SyntaxError: Unexpected identifier 'content' | |
Uncaught SyntaxError: Unexpected identifier 'content' |
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.
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Content security policy |
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Performance issues directly impact user engagement and conversion rates.
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.
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.