Tools & Wizards About Us
lexis.com screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

lexis.com

Lexis® - Sign In | LexisNexis

Page Load Speed

1.7 sec in total

First Response

106 ms

Resources Loaded

1.5 sec

Page Rendered

70 ms

lexis.com screenshot

About Website

Click here to check amazing Lexis content for United States. Otherwise, check out these important facts you probably never knew about lexis.com

LexisNexis users sign in here. Click here to login and begin conducting your legal research now.

Visit lexis.com

Key Findings

We analyzed Lexis.com page load time and found that the first response time was 106 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

lexis.com performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.048

99/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

checkBrowser

106 ms

ldcjquery_05-DEC-2015.js

191 ms

commonscript_05-DEC-2015.js

115 ms

browser_05-DEC-2015.js

59 ms

global_05-DEC-2015.css

129 ms

Our browser made a total of 5 requests to load all elements on the main page. We found that all of those requests were addressed to Lexis.com and no external sources were called. The less responsive or slowest element that took the longest time to load (191 ms) belongs to the original domain Lexis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 228.4 kB (69%)

Content Size

331.9 kB

After Optimization

103.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lexis.com main page is 331.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. Javascripts take 210.7 kB which makes up the majority of the site volume.

HTML Optimization

-54%

Potential reduce by 1.4 kB

  • Original 2.5 kB
  • After minification 2.5 kB
  • After compression 1.2 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 1.4 kB or 54% of the original size.

Image Optimization

-0%

Potential reduce by 3 B

  • Original 42.1 kB
  • After minification 42.1 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Lexis images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 161.7 kB

  • Original 210.7 kB
  • After minification 181.6 kB
  • After compression 49.0 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 161.7 kB or 77% of the original size.

CSS Optimization

-85%

Potential reduce by 65.4 kB

  • Original 76.6 kB
  • After minification 63.9 kB
  • After compression 11.2 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Lexis.com needs all CSS files to be minified and compressed as it can save up to 65.4 kB or 85% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

4

After Optimization

4

  • JavaScript
  • CSS

The browser has sent 4 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lexis. According to our analytics all requests are already optimized.

Network Requests Diagram

checkBrowser

checkBrowser

106 ms

ldcjquery_05-DEC-2015.js

ldcjquery_05-DEC-2015.js

191 ms

commonscript_05-DEC-2015.js

commonscript_05-DEC-2015.js

115 ms

browser_05-DEC-2015.js

browser_05-DEC-2015.js

59 ms

global_05-DEC-2015.css

global_05-DEC-2015.css

129 ms

Accessibility Review

lexis.com accessibility score

94

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

lexis.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

lexis.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lexis.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lexis.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

lexis.com

Open Graph description is not detected on the main page of Lexis. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: