3.7 sec in total
296 ms
2.8 sec
561 ms
Visit lechler.com now to see the best up-to-date Lechler content for United States and also check out these interesting facts you probably never knew about lechler.com
Mit über 25.000 Düsenvarianten haben wir für jede Anforderung die passende Lösung. ✔Verschiedene Branchen ✔Großes Sortiment ✔140 Jahre Erfahrung
Visit lechler.comWe analyzed Lechler.com page load time and found that the first response time was 296 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
lechler.com performance score
name
value
score
weighting
Value2.7 s
60/100
10%
Value13.8 s
0/100
25%
Value8.9 s
15/100
10%
Value820 ms
35/100
30%
Value0.141
78/100
15%
Value13.3 s
12/100
10%
296 ms
390 ms
95 ms
216 ms
201 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 91% of them (53 requests) were addressed to the original Lechler.com, 2% (1 request) were made to Maps.googleapis.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Seal.website-check.de.
Page size can be reduced by 301.0 kB (25%)
1.2 MB
916.8 kB
In fact, the total size of Lechler.com main page is 1.2 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. 40% of websites need less resources to load. Images take 872.3 kB which makes up the majority of the site volume.
Potential reduce by 91.6 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 91.6 kB or 87% of the original size.
Potential reduce by 55.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. Lechler images are well optimized though.
Potential reduce by 153.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 153.9 kB or 64% of the original size.
Number of requests can be reduced by 40 (77%)
52
12
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lechler. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
lechler.com
296 ms
lechler.com
390 ms
95 ms
de
216 ms
app.min.css
201 ms
override.css
283 ms
vivus.min.js
285 ms
vendor.min.js
474 ms
app.min.js
312 ms
pardot.js
311 ms
markerclusterer.js
312 ms
Main.js
308 ms
js
108 ms
snazzy-info-window.min.js
313 ms
gtm.js
128 ms
72ed840921b741e8.js
524 ms
seal
1109 ms
globe-icon.svg
147 ms
flag-circle-deutschland.svg
149 ms
flag-deutschland.svg
150 ms
flag-china.svg
152 ms
flag-belgien.svg
160 ms
flag-spanien.svg
370 ms
flag-frankreich.svg
371 ms
flag-indien.svg
374 ms
flag-italien.svg
373 ms
flag-malaysia.svg
376 ms
flag-niederlande.svg
377 ms
flag-russland.svg
381 ms
flag-finnland.svg
378 ms
flag-schweden.svg
379 ms
flag-england.svg
380 ms
flag-usa.svg
443 ms
search-icon.svg
446 ms
country-dropdown-arrow.svg
447 ms
btn-arrow-01.svg
448 ms
magnifying.svg
448 ms
lechler-logo-silber.png
717 ms
product-teaser.svg
476 ms
triangle-teaser-svg.svg
520 ms
event.svg
529 ms
lechler_home_scrubber-broschuere.jpg
960 ms
header-visual.svg
496 ms
btn-arrow-03.svg
530 ms
Roboto-Light-webfont.woff
574 ms
Roboto-Bold-webfont.woff
771 ms
triangle-home-wg-02.svg
567 ms
triangle-home-wg-01.svg
597 ms
stretch-teaser-blue.svg
644 ms
triangle-home-blue-01.svg
657 ms
triangle-home-blue-02.svg
689 ms
btn-arrow-02.svg
737 ms
social-icon-fb.svg
671 ms
social-icon-li.svg
678 ms
social-icon-xi.svg
709 ms
social-icon-yt.svg
757 ms
social-icon-insta.svg
753 ms
track
490 ms
lechler.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
Buttons do not have an accessible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
lechler.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
lechler.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lechler.com can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Lechler.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.
lechler.com
Open Graph description is not detected on the main page of Lechler. 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: