Tools & Wizards About Us
livent.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

livent.com

Rio Tinto | Global

Page Load Speed

4.6 sec in total

First Response

90 ms

Resources Loaded

2.3 sec

Page Rendered

2.2 sec

livent.com screenshot

About Website

Visit livent.com now to see the best up-to-date Livent content for United States and also check out these interesting facts you probably never knew about livent.com

Rio Tinto is a leading global mining group that focuses on finding, mining and processing the Earth’s mineral resources. Discover more about Rio Tinto's mining operations today.

Visit livent.com

Key Findings

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

Performance Metrics

livent.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value83.6 s

0/100

25%

SI (Speed Index)

Value37.1 s

0/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.168

70/100

15%

TTI (Time to Interactive)

Value70.5 s

0/100

10%

Network Requests Diagram

livent.com

90 ms

arcadiumlithium.com

1714 ms

css2

35 ms

ium4lgk.css

84 ms

swiper-bundle.min.css

39 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Livent.com, 90% (76 requests) were made to Arcadiumlithium.com and 2% (2 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Arcadiumlithium.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 15.4 MB (79%)

Content Size

19.5 MB

After Optimization

4.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Livent.com main page is 19.5 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. Only a small number of websites need less resources to load. Images take 19.1 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 170.6 kB

  • Original 194.0 kB
  • After minification 118.4 kB
  • After compression 23.4 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 75.6 kB, which is 39% 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 170.6 kB or 88% of the original size.

Image Optimization

-80%

Potential reduce by 15.2 MB

  • Original 19.1 MB
  • After minification 3.9 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. Obviously, Livent needs image optimization as it can save up to 15.2 MB or 80% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-28%

Potential reduce by 24.7 kB

  • Original 87.6 kB
  • After minification 87.6 kB
  • After compression 62.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 24.7 kB or 28% of the original size.

CSS Optimization

-8%

Potential reduce by 9.3 kB

  • Original 114.6 kB
  • After minification 114.5 kB
  • After compression 105.3 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. Livent.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (34%)

Requests Now

82

After Optimization

54

  • Images
  • JavaScript
  • CSS

The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Livent. 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 16 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

livent.com

livent.com

90 ms

arcadiumlithium.com

arcadiumlithium.com

1714 ms

css2

css2

35 ms

ium4lgk.css

ium4lgk.css

84 ms

swiper-bundle.min.css

swiper-bundle.min.css

39 ms

style.min.css

style.min.css

57 ms

p.css

p.css

25 ms

style.min.css

style.min.css

15 ms

style.css

style.css

40 ms

ikz1cnq.css

ikz1cnq.css

47 ms

style.css

style.css

32 ms

style.css

style.css

53 ms

search-forms.css

search-forms.css

36 ms

js_composer.min.css

js_composer.min.css

89 ms

us.png

us.png

26 ms

es.svg

es.svg

25 ms

fr.svg

fr.svg

37 ms

ja.svg

ja.svg

45 ms

zh-hans.svg

zh-hans.svg

38 ms

p.css

p.css

2 ms

logo-xl.png

logo-xl.png

65 ms

Home_Overview@2x.png

Home_Overview@2x.png

76 ms

Graves@2x.png

Graves@2x.png

59 ms

Antoniazzi@2x.png

Antoniazzi@2x.png

38 ms

Ponessa@2x.png

Ponessa@2x.png

56 ms

Markmann@2x.png

Markmann@2x.png

55 ms

Fochtman@2x.png

Fochtman@2x.png

80 ms

Cortes@2x.png

Cortes@2x.png

67 ms

Couture@2x.png

Couture@2x.png

78 ms

Porta@2x.png

Porta@2x.png

74 ms

JoseIgnacioCosta.png

JoseIgnacioCosta.png

83 ms

Vizental@2x.png

Vizental@2x.png

72 ms

Franklyn@2x.png

Franklyn@2x.png

99 ms

Neil_Robertson-1.jpg

Neil_Robertson-1.jpg

109 ms

Maryssael@2x.png

Maryssael@2x.png

102 ms

Czarnecki@2x.png

Czarnecki@2x.png

110 ms

Thumbnail_Graves@2x-1.png

Thumbnail_Graves@2x-1.png

110 ms

Thumbnail_Antoniazzi@2x.png

Thumbnail_Antoniazzi@2x.png

113 ms

Thumbnail_Ponessa@2x.png

Thumbnail_Ponessa@2x.png

128 ms

Thumbnail_Markmann@2x.png

Thumbnail_Markmann@2x.png

137 ms

Thumbnail_Fochtman@2x.png

Thumbnail_Fochtman@2x.png

141 ms

Thumbnail_Cortes@2x.png

Thumbnail_Cortes@2x.png

140 ms

Thumbnail_Couture@2x.png

Thumbnail_Couture@2x.png

139 ms

Thumbnail_Porta@2x.png

Thumbnail_Porta@2x.png

144 ms

JoseIgnacioCosta_Thumbnail.png

JoseIgnacioCosta_Thumbnail.png

159 ms

Thumbnail_Vizental@2x.png

Thumbnail_Vizental@2x.png

166 ms

Thumbnail_Franklyn@2x.png

Thumbnail_Franklyn@2x.png

177 ms

Headshots_Neil_Robertson-_portrait-1.jpg

Headshots_Neil_Robertson-_portrait-1.jpg

166 ms

Thumbnail_Maryssael@2x.png

Thumbnail_Maryssael@2x.png

177 ms

Thumbnail_Czarnecki@2x.png

Thumbnail_Czarnecki@2x.png

179 ms

spinner.gif

spinner.gif

169 ms

Home_Purpose@2x.png

Home_Purpose@2x.png

201 ms

Arcadium_Icons_For-Each-Other-2.png

Arcadium_Icons_For-Each-Other-2.png

195 ms

Arcadium_Icons_Stakeholders_2-1-2.png

Arcadium_Icons_Stakeholders_2-1-2.png

197 ms

Arcadium_Icons_Values_Future-2.png

Arcadium_Icons_Values_Future-2.png

198 ms

font-awesome.css

font-awesome.css

159 ms

normalize.css

normalize.css

156 ms

mega-superstorefinder.css

mega-superstorefinder.css

169 ms

scripts.js

scripts.js

165 ms

script.min.js

script.min.js

224 ms

modernizr.min.js

modernizr.min.js

155 ms

html5shiv.3.7.0.min.js

html5shiv.3.7.0.min.js

159 ms

homebrew.js

homebrew.js

213 ms

fastclick.min.js

fastclick.min.js

225 ms

init.js

init.js

206 ms

mega-openclose.js

mega-openclose.js

202 ms

mega-superstorefinder.js

mega-superstorefinder.js

201 ms

super-analytics.js

super-analytics.js

198 ms

js_composer_front.min.js

js_composer_front.min.js

182 ms

rocket-loader.min.js

rocket-loader.min.js

179 ms

1944@2x.png

1944@2x.png

193 ms

FMC_466x620.jpg

FMC_466x620.jpg

188 ms

1991@2x.png

1991@2x.png

188 ms

2008@2x.png

2008@2x.png

279 ms

2010@2x.png

2010@2x.png

174 ms

2015@2x.png

2015@2x.png

163 ms

2016@2x.png

2016@2x.png

163 ms

2018@2x.png

2018@2x.png

173 ms

2021@2x.png

2021@2x.png

165 ms

Logo@2x.png

Logo@2x.png

164 ms

SDV-people-pond.jpg

SDV-people-pond.jpg

171 ms

MicrosoftTeams-image-16.png

MicrosoftTeams-image-16.png

214 ms

main.js

main.js

11 ms

swiper-bundle.min.js

swiper-bundle.min.js

19 ms

Accessibility Review

livent.com accessibility score

89

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

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.

Impact

Issue

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

livent.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

livent.com SEO score

86

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a valid hreflang

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Livent.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 Livent.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

livent.com

Open Graph data is detected on the main page of Livent. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: