Tools & Wizards About Us
sanction.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

sanction.com

Sanction Case Presentation | LexisNexis Litigation Solutions | LexisNexis

Page Load Speed

3.9 sec in total

First Response

113 ms

Resources Loaded

3.2 sec

Page Rendered

619 ms

sanction.com screenshot

About Website

Click here to check amazing Sanction content. Otherwise, check out these important facts you probably never knew about sanction.com

Sanction® case allows users to rapidly assemble documents, exhibits, transcripts, visuals and video for a compelling and seamless evidence presentation. Learn more!

Visit sanction.com

Key Findings

We analyzed Sanction.com page load time and found that the first response time was 113 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

sanction.com performance score

0

Network Requests Diagram

sanction.com

113 ms

sanction

107 ms

css

24 ms

styles.min.css

53 ms

medium.min.css

70 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Sanction.com, 50% (26 requests) were made to Lexisnexis.com and 10% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Lexisnexis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (17%)

Content Size

6.1 MB

After Optimization

5.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sanction.com main page is 6.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 4.7 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 49.2 kB

  • Original 60.1 kB
  • After minification 48.4 kB
  • After compression 10.9 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. This page needs HTML code to be minified as it can gain 11.7 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 49.2 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 24.0 kB

  • Original 4.7 MB
  • After minification 4.7 MB

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. Sanction images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 627.0 kB

  • Original 852.9 kB
  • After minification 723.8 kB
  • After compression 225.9 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 627.0 kB or 74% of the original size.

CSS Optimization

-83%

Potential reduce by 363.8 kB

  • Original 440.6 kB
  • After minification 438.1 kB
  • After compression 76.8 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. Sanction.com needs all CSS files to be minified and compressed as it can save up to 363.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (45%)

Requests Now

42

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sanction. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

sanction.com

sanction.com

113 ms

sanction

sanction

107 ms

css

css

24 ms

styles.min.css

styles.min.css

53 ms

medium.min.css

medium.min.css

70 ms

wide.min.css

wide.min.css

67 ms

litigation.min.css

litigation.min.css

72 ms

lypn-gtm.js

lypn-gtm.js

80 ms

lypn-gtm-youtube-tracking.js

lypn-gtm-youtube-tracking.js

79 ms

requirejs.js

requirejs.js

118 ms

logo-lexisnexis-lit.png

logo-lexisnexis-lit.png

51 ms

iStock_000000618811_Cropped.jpg

iStock_000000618811_Cropped.jpg

177 ms

CaseStudy_Herrick.jpg

CaseStudy_Herrick.jpg

178 ms

78724287_5_cropped.jpg

78724287_5_cropped.jpg

178 ms

SN4-Transcript.jpg

SN4-Transcript.jpg

2524 ms

50_50-594x348-edited.jpg

50_50-594x348-edited.jpg

176 ms

logo-white.png

logo-white.png

222 ms

re-logo.png

re-logo.png

225 ms

gtm.js

gtm.js

48 ms

widgets.js

widgets.js

200 ms

MRUIZcPeSrI

MRUIZcPeSrI

195 ms

menu-search.png

menu-search.png

188 ms

header-sprite.png

header-sprite.png

188 ms

breadcrumb-arrow.png

breadcrumb-arrow.png

187 ms

000024455687_Full-edited.jpg

000024455687_Full-edited.jpg

251 ms

bullet-points.png

bullet-points.png

249 ms

external-icon.png

external-icon.png

239 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

37 ms

nj47mAZe0mYUIySgfn0wpQ.ttf

nj47mAZe0mYUIySgfn0wpQ.ttf

45 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

134 ms

analytics.js

analytics.js

18 ms

conversion_async.js

conversion_async.js

110 ms

di.js

di.js

158 ms

main-blss-litigation.min.js

main-blss-litigation.min.js

251 ms

collect

collect

51 ms

collect

collect

149 ms

icons.woff

icons.woff

107 ms

109 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

181 ms

www-embed-player.js

www-embed-player.js

204 ms

base.js

base.js

263 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

300 ms

103 ms

ga-audiences

ga-audiences

128 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

10 ms

ad_status.js

ad_status.js

72 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

63 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

63 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

58 ms

jot

jot

94 ms

print.min.css

print.min.css

44 ms

eloqua-contact-form

eloqua-contact-form

156 ms

SEO Factors

sanction.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sanction.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Sanction.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

sanction.com

Open Graph description is not detected on the main page of Sanction. 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: