Spain · Madrid Completed: Apr 21, 2026 21:51 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 67 / 100
Based on 8 categories, 0 sections
Decent speed, but optimizing further could improve engagement.
Several missing protections leave your users and data exposed.
Major barriers for users with disabilities — up to 15% of your audience.
Solid SEO basics — a few optimizations could boost rankings.
Good server performance with room for optimization.
Mostly compliant — a few items need attention.
Good content signals with minor gaps.
Heavier than average — reducing page weight saves energy and bandwidth.
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.
Cookie 'LNMEGASITE' is missing the Secure flag
Security gaps expose your site and users to attacks, eroding trust.
HSTS 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.
4 image(s) missing alt attribute
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
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/e7319ba6-1ecb-4b18-90c6-1a7ea9851c02)<a href="https://beavercheck.com/results/e7319ba6-1ecb-4b18-90c6-1a7ea9851c02"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Flexisnexis.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Flexisnexis.comThis badge auto-updates with your latest scan result.
Your site has several issues that may be affecting user experience and business outcomes. 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.
10 barrier(s) likely increasing bounce by ~40%.
Page takes 10.1s to load
+12% bounceUsers abandon at ~3s — you're 7.6s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 2.3s
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
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 viewport meta tag
+15% bounceMobile browsers render at desktop width and shrink — text unreadable, tap targets miniature
Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">
Thin content
+3% bounceUnder 300 words — visitors bounce looking for substance, search engines rank competitors first
Fix: Add a substantive FAQ, product detail, or case-study section
Content is hard to read
+2% bounceGraduate-level reading difficulty — limits the addressable audience for product or blog pages
Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
13 broken link(s) on the page
+5% bounceClicks land on 404s — trust drops and the session often ends
Fix: Fix or remove the broken destinations surfaced on the Content tab
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
$350 investment → $5,394/month returns + USD 157,500 risk avoided
$350
4h · 5 findings
$5,394 /mo
~$64,732 / year
USD 157,500
if kept compliant
$200 — 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.
3.5 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$13,126 / month at risk
~$157,508 / year if left unfixed
$157,500
+2 more
$0.70 /mo
8782.8 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 5 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.
4.59 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
10.11 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
2.32 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.103
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
4.59 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.
26.99 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.
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.
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.
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
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.
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.
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| 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.
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 |
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.
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.
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.
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.
2.14 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
4.37 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
44 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.14 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.
4.37 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.
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.
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 | 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.
Performance issues directly impact user engagement and conversion rates.
| 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.
Performance issues directly impact user engagement and conversion rates.
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 |
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.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.
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 |
|---|---|---|
| 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
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.
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.
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.
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 |
|---|
Cookie Policy. div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link |
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: 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. | |
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.
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Content security policy |
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.
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.
Send Feedback