5.7 sec in total
581 ms
4.4 sec
645 ms
Click here to check amazing Nekermann content. Otherwise, check out these important facts you probably never knew about nekermann.de
Neckermann geht, aber die Auswahl bleibt! Finde deine neuen Möbel, Klamotten & Technick-Gadgets bei OTTO » Top Service ✔ Top Marken ✔ Aktuelle Trends ✔ » Jetzt shoppen!
Visit nekermann.deWe analyzed Nekermann.de page load time and found that the first response time was 581 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
nekermann.de performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value8.9 s
1/100
25%
Value12.8 s
2/100
10%
Value8,540 ms
0/100
30%
Value0.107
88/100
15%
Value16.5 s
5/100
10%
581 ms
447 ms
236 ms
288 ms
383 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Nekermann.de, 18% (18 requests) were made to I.otto.de. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Otto.de.
Page size can be reduced by 105.8 kB (39%)
270.3 kB
164.4 kB
In fact, the total size of Nekermann.de main page is 270.3 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. 60% of websites need less resources to load. HTML takes 125.9 kB which makes up the majority of the site volume.
Potential reduce by 104.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 104.5 kB or 83% of the original size.
Potential reduce by 0 B
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. Nekermann images are well optimized though.
Potential reduce by 552 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 765 B
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. Nekermann.de has all CSS files already compressed.
Number of requests can be reduced by 52 (57%)
92
40
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nekermann. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
581 ms
assets.polyfills.head.js
447 ms
assets.global-resources.legacy.nomodule.60456de4.js
236 ms
assets.global-resources.head.f7319cfc.css
288 ms
assets.global-resources.head.nomodule.821c9977.js
383 ms
assets.global-pattern.main.12123481.css
384 ms
assets.global-pattern.main.nomodule.f310575c.js
383 ms
ftfind.centipede.css.8133d043.css
299 ms
ftfind.cricket.resources.57653e12.css
357 ms
ftfind.grasshopper.head.c302c875.css
1157 ms
squirrel.stomachshop.resources.b9f34f7c.css
1160 ms
squirrel.stomachshop.resources.nomodule.91643d84.js
1163 ms
ft1.wishlist-view.miniWishlist.6306a45b.css
1158 ms
ft1.order-core.minibasket.b19c2e59.css
1163 ms
nav.imberator.bottom.df8a0f56.css
1163 ms
ft7bcn.wato.onsite.534a0894.css
1163 ms
assets.global-resources.body.nomodule.49692e68.js
1185 ms
tracking.bct.bct.19c983a8.js
1186 ms
otto-sans_fb84ead3.woff2
402 ms
otto-sans-bold_b7bb08ce.woff2
491 ms
OTTO-Icons_8a586867.woff2
404 ms
scale.shop-assets.scale_beacon.d208f684.js
404 ms
472 ms
482 ms
468 ms
434 ms
503 ms
501 ms
498 ms
461 ms
477 ms
513 ms
510 ms
517 ms
617 ms
542 ms
543 ms
545 ms
547 ms
001_2021_38_moeb_mak_redirect_neckermann_imagebanner_184106
547 ms
pl_logo_app-store.svg
377 ms
pl_logo_play-store.svg
374 ms
reptile.locust.head.nomodule.b80e7afd.js
368 ms
ftfind.cricket.resources.nomodule.c6564ab2.js
358 ms
heureka.leafcutter.private.nomodule.dd5f2dac.js
366 ms
assets.global-resources.fonts.607dafe6.css
332 ms
reptile.locust.head.bacc537a.css
356 ms
reptile.locust.head-css.34095882.css
350 ms
heureka.leafcutter.private.9323d00a.css
352 ms
pl_icon_close.svg
162 ms
pl_icon_search.svg
152 ms
otto-sans_6486f314.woff
141 ms
otto-sans-bold_19eb984b.woff
185 ms
pl_icon_basket.svg
146 ms
ft4.user.login-area.3b346b0d.js
117 ms
ft1.wishlist-view.miniWishlist.nomodule.3a945fda.js
108 ms
ft1.order-core.common-public.573ac3d1.js
106 ms
ft1.order-core.minibasket.95d21f5b.js
125 ms
nav.chekov.web_bundle.nomodule.53415483.js
145 ms
ft4.user.login-area.4a41f314.css
124 ms
nav.chekov.web_bundle.8941bae3.css
142 ms
nav.grimm.main.nomodule.04a4985d.js
129 ms
ft3.promo.staticcontent.nomodule.d81dcff6.js
154 ms
OTTO-Icons_c532a157.woff
123 ms
nav.grimm.main.a9b504b7.css
112 ms
ft3.promo.staticcontent.4c97ea4d.css
127 ms
ft3.promo.aggregation.nomodule.e12d88c8.js
109 ms
nav.imberator.js_bundle.nomodule.7bfad5b9.js
182 ms
sho.shoppages.assets-public.8201a17d.js
251 ms
ft4.user.newsletter-snippet.d387de48.js
239 ms
ft7bcn.wato.onsite.nomodule.2b405960.js
240 ms
pl_icon_person.svg
191 ms
pl_icon_voucher.svg
193 ms
pl_icon_feedback.svg
194 ms
pl_logo_ehi.svg
191 ms
pl_logo_sepa.svg
213 ms
pl_logo_visa.svg
213 ms
pl_logo_mastercard.svg
255 ms
pl_logo_amex.svg
255 ms
pl_logo_paypal.svg
255 ms
pl_logo_giropay.svg
257 ms
pl_logo_updated.svg
261 ms
pl_logo_market.svg
285 ms
pl_logo_otto-payments-lang-logo.svg
291 ms
pl_logo_finanzplus.svg
289 ms
pl_logo_retailmedia.svg
291 ms
pl_logo_cgi.svg
317 ms
pl_icon_check.svg
327 ms
pl_logo_pinterest.svg
314 ms
pl_logo_facebook.svg
358 ms
pl_logo_twitter.svg
360 ms
pl_logo_youtube.svg
358 ms
pl_logo_instagram.svg
403 ms
pl_logo_slogan.svg
441 ms
ft3.promo.aggregation.80ed0858.css
278 ms
sho.shoppages.assets-public.12a4dfd1.css
291 ms
ft4.user.newsletter-snippet.f445ce0c.css
287 ms
assets.global-resources.bodyasync.nomodule.914c3843.js
329 ms
ft1.order-core.common-public.573ac3d1.js
246 ms
nekermann.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
nekermann.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Page has valid source maps
nekermann.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
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nekermann.de 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 Nekermann.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.
nekermann.de
Open Graph description is not detected on the main page of Nekermann. 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: