4.1 sec in total
203 ms
3.4 sec
428 ms
Click here to check amazing Lands End content for Germany. Otherwise, check out these important facts you probably never knew about landsend.de
Aktuelle Mode online kaufen im Lands' End Onlineshop. Große Auswahl an Mode & Fashion für Herren und Damen in allen Preisklassen.
Visit landsend.deWe analyzed Landsend.de page load time and found that the first response time was 203 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
landsend.de performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value15.5 s
0/100
25%
Value12.4 s
3/100
10%
Value3,250 ms
2/100
30%
Value0.069
96/100
15%
Value24.8 s
0/100
10%
203 ms
106 ms
61 ms
444 ms
719 ms
Our browser made a total of 109 requests to load all elements on the main page. We found that 5% of them (5 requests) were addressed to the original Landsend.de, 67% (73 requests) were made to Demandware.edgesuite.net and 3% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Demandware.edgesuite.net.
Page size can be reduced by 4.2 MB (50%)
8.3 MB
4.1 MB
In fact, the total size of Landsend.de main page is 8.3 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. Javascripts take 3.8 MB which makes up the majority of the site volume.
Potential reduce by 119.5 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 119.5 kB or 81% of the original size.
Potential reduce by 29.3 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. Lands End images are well optimized though.
Potential reduce by 3.1 MB
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 3.1 MB or 82% of the original size.
Potential reduce by 962.6 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. Landsend.de needs all CSS files to be minified and compressed as it can save up to 962.6 kB or 81% of the original size.
Number of requests can be reduced by 53 (54%)
99
46
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lands End. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.landsend.de
203 ms
satelliteLib-6b5dbb13b45a5be00f848b396f2b7ccc3c7b5557.js
106 ms
jquery-ui.min.css
61 ms
jquery-2.1.1.min.js
444 ms
jquery-ui.min.js
719 ms
jquery.jcarousel.min.js
59 ms
jquery.validate.min.js
32 ms
jquery.zoom.min.js
211 ms
leScrollbar.js
45 ms
jquery.tinyscrollbar.js
58 ms
jquery.serialScroll.js
284 ms
jquery.scrollToFixed.js
115 ms
jquery.scrollTo.js
70 ms
jquery.scrollorama.js
78 ms
jquery.overthrow.js
88 ms
jquery.nanoscroller.min.js
325 ms
jquery.localscroll.js
340 ms
jquery.ba-throttle-debounce.js
218 ms
jquery.hoverIntent.minified.js
324 ms
dwac-14.8.js
298 ms
style.css
321 ms
site.css
457 ms
powerreviews.css
357 ms
euBase.css
455 ms
euBaseMobile.css
466 ms
css
60 ms
css
73 ms
responsiveslides.min.js
478 ms
modal.js
563 ms
classie.js
546 ms
category-copy.css
475 ms
app.js
539 ms
resxclsa.js
612 ms
dwanalytics.js
601 ms
gretel.min.js
34 ms
entry.js
8 ms
header_icon_bag_blk.png
143 ms
lands-end-logo.png
128 ms
dropdown_w_all.jpg
131 ms
dropdown_m_all.jpg
288 ms
lato-regular-webfont.woff
95 ms
lato-black-webfont.woff
109 ms
fontawesome-webfont.woff
186 ms
homepage-feature-09.png
125 ms
homepage-feature-09.jpg
545 ms
homepage-feature-02.png
355 ms
homepage-feature-02.jpg
1067 ms
homepage-feature-01.png
336 ms
homepage-feature-01.jpg
808 ms
homepage-feature-09-medium.png
403 ms
homepage-feature-09-medium.jpg
778 ms
homepage-feature-01-medium.png
504 ms
homepage-feature-01-medium.jpg
926 ms
homepage-sub-01.jpg
638 ms
homepage-sub-02.jpg
675 ms
homepage-sub-03.jpg
888 ms
homepage-sub-04.jpg
810 ms
homepage-banner-01-medium.png
922 ms
homepage-banner-01-medium.jpg
1137 ms
homepage-banner-02-medium.jpg
1198 ms
homepage-banner-03-medium.png
1013 ms
homepage-banner-03-medium.jpg
1046 ms
sale-banner-01-medium.png
1050 ms
sale-banner-01-medium.jpg
1364 ms
homepage-banner-01.png
1174 ms
homepage-banner-01.jpg
1184 ms
homepage-banner-02.jpg
1677 ms
homepage-banner-03.png
1290 ms
homepage-banner-03.jpg
1434 ms
homepage-banner-04.png
1302 ms
homepage-banner-04.jpg
1452 ms
footer_facebook.png
1327 ms
footer_twitter.png
1328 ms
footer_pinterest.png
1387 ms
footer_youtube.png
1428 ms
gk5FxslNkTTHtojXrkp-xD1GzwQ5qF9DNzkQQVRhJ4g.ttf
46 ms
gk5FxslNkTTHtojXrkp-xJhsE6jcpsD2oq89kgohWx0.ttf
55 ms
4GwpJM7qx9X5Obd9KsnKxQ.ttf
65 ms
footer_image_1.gif
1576 ms
LE_globalnav_footer3.jpg
1395 ms
right_arrow.gif
1417 ms
bvh-ehi-logo.gif
1384 ms
sessioncam.recorder.js
42 ms
sub2.js
195 ms
ContainerJavaScript.ashx
316 ms
conversion.js
22 ms
satellite-547d58b33864310015b60000.js
34 ms
s-code-contents-a60a50a0e1e1604a578e77d148c00aab138cf3a6.js
90 ms
config.aspx
70 ms
VeriSign.gif
1263 ms
creditcards.gif
1298 ms
s41891719182021
8 ms
67 ms
analytics.js
47 ms
fbds.js
151 ms
ld.js
43 ms
bat.js
41 ms
themes.png
959 ms
collect
22 ms
collect
60 ms
39 ms
SUB2_Code_obj_min_1.1.js
173 ms
24 ms
sub2_custom.js
87 ms
__Analytics-Tracking
95 ms
event
18 ms
4 ms
event
188 ms
getIndividual
92 ms
landsend.de 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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.
landsend.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
landsend.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Image elements do not have [alt] attributes
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
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Landsend.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Landsend.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.
landsend.de
Open Graph description is not detected on the main page of Lands End. 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: