Tools & Wizards About Us
lanxess.de screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lanxess.de

▷ Spezialchemie | Energizing Chemistry | LANXESS

Page Load Speed

2.8 sec in total

First Response

378 ms

Resources Loaded

2.2 sec

Page Rendered

200 ms

lanxess.de screenshot

About Website

Click here to check amazing LANXESS content for Germany. Otherwise, check out these important facts you probably never knew about lanxess.de

Entwicklung, Herstellung und Vertrieb von Kunststoffen, Kautschuken, Zwischenprodukten und Spezialchemikalien.

Visit lanxess.de

Key Findings

We analyzed Lanxess.de page load time and found that the first response time was 378 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

lanxess.de performance score

0

Network Requests Diagram

378 ms

import_corp.css

388 ms

lanxess_rebrush.css

384 ms

jplayer.css

195 ms

lanxess_rebrush_corporate.css

199 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 91% of them (64 requests) were addressed to the original Lanxess.de, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Lanxess.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 621.2 kB (30%)

Content Size

2.1 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lanxess.de main page is 2.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. 30% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 35.5 kB

  • Original 44.9 kB
  • After minification 42.2 kB
  • After compression 9.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. 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 35.5 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 7.5 kB

  • Original 1.2 MB
  • After minification 1.2 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. LANXESS images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 423.9 kB

  • Original 602.7 kB
  • After minification 529.3 kB
  • After compression 178.8 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 423.9 kB or 70% of the original size.

CSS Optimization

-86%

Potential reduce by 154.3 kB

  • Original 179.4 kB
  • After minification 155.3 kB
  • After compression 25.1 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. Lanxess.de needs all CSS files to be minified and compressed as it can save up to 154.3 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (60%)

Requests Now

68

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

378 ms

import_corp.css

import_corp.css

388 ms

lanxess_rebrush.css

lanxess_rebrush.css

384 ms

jplayer.css

jplayer.css

195 ms

lanxess_rebrush_corporate.css

lanxess_rebrush_corporate.css

199 ms

lanxess_corporate_override.css

lanxess_corporate_override.css

191 ms

jquery-1.7.min.js

jquery-1.7.min.js

374 ms

jquery-ui.min.js

jquery-ui.min.js

668 ms

jquery.tools.min.js

jquery.tools.min.js

379 ms

jquery.blockUI.js

jquery.blockUI.js

291 ms

jquery.validate.js

jquery.validate.js

480 ms

jquery.dimensions.js

jquery.dimensions.js

468 ms

lanxess_rebrush.js

lanxess_rebrush.js

570 ms

jcap.js

jcap.js

475 ms

md5.js

md5.js

476 ms

swfobject.js

swfobject.js

560 ms

lxsjcap.js

lxsjcap.js

567 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

574 ms

jplayer.playlist.min.js

jplayer.playlist.min.js

571 ms

jquery.tweet.js

jquery.tweet.js

654 ms

conversion.js

conversion.js

17 ms

ga.js

ga.js

85 ms

body-shadow.png

body-shadow.png

113 ms

minichart_intra2.gif

minichart_intra2.gif

201 ms

wrapper-shadow.png

wrapper-shadow.png

101 ms

arrow-language-active.png

arrow-language-active.png

101 ms

lanxess-share-icons-01.png

lanxess-share-icons-01.png

102 ms

lanxess.png

lanxess.png

104 ms

arrow-small-red-margin.png

arrow-small-red-margin.png

105 ms

header-flyout-border.png

header-flyout-border.png

173 ms

search-glass.png

search-glass.png

190 ms

btn-header-search.png

btn-header-search.png

189 ms

btn3.png

btn3.png

192 ms

arrow-small-white.png

arrow-small-white.png

191 ms

header-worldmap.png

header-worldmap.png

192 ms

arrow-down-small-grey.png

arrow-down-small-grey.png

265 ms

newsroom_719dfd03bc.jpg

newsroom_719dfd03bc.jpg

282 ms

Motiv_film_2b0bb1415c.jpg

Motiv_film_2b0bb1415c.jpg

282 ms

Annual_Report_Titel_01_8f0baeb473.jpg

Annual_Report_Titel_01_8f0baeb473.jpg

283 ms

Quartal_80c96c1842.jpg

Quartal_80c96c1842.jpg

284 ms

dfd0eebe00.jpg

dfd0eebe00.jpg

284 ms

Leder_Levaderm_01.jpg

Leder_Levaderm_01.jpg

912 ms

TackLite_StickGo_Anwendungsbeispiel_Kueche_01.png

TackLite_StickGo_Anwendungsbeispiel_Kueche_01.png

746 ms

Anhydrit_CAB30_Stage_01.jpg

Anhydrit_CAB30_Stage_01.jpg

1022 ms

JV-Logo-Stage.jpg

JV-Logo-Stage.jpg

470 ms

Wir-zusammen_Logo-Stage_01.jpg

Wir-zusammen_Logo-Stage_01.jpg

473 ms

arrow-left-stage.png

arrow-left-stage.png

380 ms

layer-white.png

layer-white.png

474 ms

Leder_Levaderm_01_f005117a94.jpg

Leder_Levaderm_01_f005117a94.jpg

565 ms

TackLite_StickGo_Anwendungsbeispiel_Kueche_01_01c7a05e12.png

TackLite_StickGo_Anwendungsbeispiel_Kueche_01_01c7a05e12.png

566 ms

Anhydrit_CAB30_Stage_01_18815376a1.jpg

Anhydrit_CAB30_Stage_01_18815376a1.jpg

566 ms

JV_Logo_Teaser_01_15b31f304a.jpg

JV_Logo_Teaser_01_15b31f304a.jpg

657 ms

Wir-zusammen-Teaser2.jpg

Wir-zusammen-Teaser2.jpg

660 ms

arrow-right-stage.png

arrow-right-stage.png

660 ms

prd-srch_back.jpg

prd-srch_back.jpg

753 ms

pager-line.png

pager-line.png

754 ms

arrow-mini-red.png

arrow-mini-red.png

755 ms

LXS-IMG_LED_2_Teaser_04_3607515dfd.jpg

LXS-IMG_LED_2_Teaser_04_3607515dfd.jpg

835 ms

arrow-small-red.png

arrow-small-red.png

844 ms

69 ms

__utm.gif

__utm.gif

25 ms

46 ms

2016-00018_Aromatenverbund_Teaser_01_a1ae344267.jpg

2016-00018_Aromatenverbund_Teaser_01_a1ae344267.jpg

757 ms

LXS-IMG_Tablet_Cover_1_Teaser_01_33bc379532.jpg

LXS-IMG_Tablet_Cover_1_Teaser_01_33bc379532.jpg

757 ms

Lanxess2_Teaser_e742ff6fe6.jpg

Lanxess2_Teaser_e742ff6fe6.jpg

837 ms

2016-00015_Saltidin__Teaser_29e6ac14a6.jpg

2016-00015_Saltidin__Teaser_29e6ac14a6.jpg

845 ms

block-shader.png

block-shader.png

846 ms

footer_shadow.png

footer_shadow.png

846 ms

arrow-stage-active.png

arrow-stage-active.png

837 ms

btn4.png

btn4.png

844 ms

SEO Factors

lanxess.de SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lanxess.de can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is German. Our system also found out that Lanxess.de 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

lanxess.de

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