2.1 sec in total
204 ms
1.7 sec
189 ms
Welcome to lanxess.us homepage info - get ready to check LANXESS best content for United States right away, or after learning these important things about lanxess.us
Home USA
Visit lanxess.usWe analyzed Lanxess.us page load time and found that the first response time was 204 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
lanxess.us performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value6.4 s
9/100
25%
Value5.1 s
61/100
10%
Value760 ms
39/100
30%
Value0
100/100
15%
Value6.1 s
63/100
10%
204 ms
179 ms
447 ms
14 ms
191 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 88% of them (49 requests) were addressed to the original Lanxess.us, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (887 ms) belongs to the original domain Lanxess.us.
Page size can be reduced by 101.9 kB (11%)
889.8 kB
787.9 kB
In fact, the total size of Lanxess.us main page is 889.8 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. 35% of websites need less resources to load. Images take 768.0 kB which makes up the majority of the site volume.
Potential reduce by 58.3 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 13.0 kB, which is 19% 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 58.3 kB or 85% of the original size.
Potential reduce by 11.5 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. LANXESS images are well optimized though.
Potential reduce by 32.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 32.0 kB or 60% of the original size.
Number of requests can be reduced by 23 (43%)
53
30
The browser has sent 53 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 5 to 1 for JavaScripts and as a result speed up the page load time.
lanxess.us
204 ms
merged-57215b6d6802003ba6eeff34dfb3e2e8-a736e30113bfa01219842339e8fff023.css.gzip
179 ms
merged-a46681acf8e535e513b3524e5dd257c7-6c3058fccaba900e1ebaca09dbc872c5.js.gzip
447 ms
conversion.js
14 ms
vhs-assets-homesiteContactTeaser-productsearch-home-25357-0.js
191 ms
body-shadow.png
93 ms
wrapper-shadow.png
93 ms
arrow-language-active.png
91 ms
lanxess-share-icons-01.png
180 ms
lanxess.png
183 ms
countryflag_usa.jpg
268 ms
arrow-small-red-margin.png
183 ms
header-flyout-border.png
185 ms
search-glass.png
187 ms
btn-header-search.png
270 ms
btn3.png
268 ms
arrow-small-white.png
270 ms
header-worldmap.png
269 ms
arrow-down-small-grey.png
271 ms
Formula_E_press_photo2_996x412.jpg
445 ms
Health_Briefs_filming_Papadourakis_desk_web_996x412.jpg
620 ms
CR-Sponsoring-El-Dorado.jpg
535 ms
CCW-Award.jpg
360 ms
Zachert-HV-2016.jpg
446 ms
arrow-left-stage.png
357 ms
layer-white.png
446 ms
csm_Formula_E_press_photo2_996x412_a195f1f81b.jpg
449 ms
csm_Health_Briefs_filming_Papadourakis_desk_web_996x412_110f76693e.jpg
534 ms
csm_CR-Sponsoring-El-Dorado_e42fe6674a.jpg
534 ms
csm_CCW-Award_ce1e87b667.jpg
535 ms
csm_Zachert-HV-2016_43a04ae6ed.jpg
537 ms
arrow-right-stage.png
622 ms
contact_phone_74.jpg
622 ms
pager-line.png
623 ms
arrow-mini-red.png
622 ms
csm_LANXESS_Tower_Teaser_03c79855a5.jpg
626 ms
arrow-small-red.png
705 ms
csm_LXS-IMG_Tepex_Durchlade_1_Teaser_63e621290f.jpg
710 ms
csm_Formula_E_press_photo1_Teaser_7a684c0d63.jpg
711 ms
tepex_vor_auto_1_02_318x179.jpg
887 ms
gtm.js
48 ms
58 ms
csm_Formula_E_press_photo2_650x366_0fc4f8964f.jpg
694 ms
analytics.js
11 ms
33 ms
arrow-small-grey.png
630 ms
btn4.png
709 ms
collect
12 ms
csm_Chemtura-Acquisition-handshake_08cb7451a1.jpg
703 ms
collect
47 ms
quality_film.jpg
627 ms
qw_landing_01.jpg
623 ms
block-shader.png
626 ms
footer_shadow.png
704 ms
arrow-stage-active.png
707 ms
merged-dd900fa01b86413c6cc2bd2a256ded8d-9c5e0d3b1ca17a17fc2d6c0e9259b7f0.css.gzip
91 ms
lanxess.us accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
lanxess.us best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
lanxess.us SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lanxess.us 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 Lanxess.us 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.
lanxess.us
Open Graph data is detected on the main page of LANXESS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: