4.3 sec in total
345 ms
3.4 sec
542 ms
Visit ottonet.de now to see the best up-to-date Ottonet content for Germany and also check out these interesting facts you probably never knew about ottonet.de
OTTO Online-Shop » Hier klicken ✓ Mode, Technik & Wohnen: Top-Trends 2016 ✓ Großes Service-Angebot: Aufbauservice ✓ Altgeräte-Mitnahme ✓ Ratenkauf ✓
Visit ottonet.deWe analyzed Ottonet.de page load time and found that the first response time was 345 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 65% of websites can load faster.
ottonet.de performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value6.3 s
10/100
25%
Value6.2 s
44/100
10%
Value260 ms
83/100
30%
Value0.087
93/100
15%
Value5.8 s
67/100
10%
345 ms
587 ms
577 ms
405 ms
712 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Ottonet.de, 56% (40 requests) were made to Images.otto.de and 20% (14 requests) were made to Otto.de. The less responsive or slowest element that took the longest time to load (827 ms) relates to the external source Assets.cdn-otto.de.
Page size can be reduced by 1.3 MB (51%)
2.5 MB
1.2 MB
In fact, the total size of Ottonet.de main page is 2.5 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. 50% of websites need less resources to load. Images take 776.6 kB which makes up the majority of the site volume.
Potential reduce by 403.0 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 79.7 kB, which is 15% 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 403.0 kB or 75% of the original size.
Potential reduce by 28.9 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. Ottonet images are well optimized though.
Potential reduce by 515.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 515.8 kB or 70% of the original size.
Potential reduce by 315.7 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. Ottonet.de needs all CSS files to be minified and compressed as it can save up to 315.7 kB or 72% of the original size.
Number of requests can be reduced by 10 (15%)
66
56
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ottonet. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
ottonet.de
345 ms
www.otto.de
587 ms
public_critical_min.css
577 ms
private_critical_min.css
405 ms
public_thirdparty_min.js
712 ms
public_critical_min.js
827 ms
private_shoppages_critical_min.js
388 ms
001_2016_9_kamp_tv_slideshow
417 ms
apple-app-store-badge-de.png
121 ms
15453984
397 ms
15680581
398 ms
12722504
422 ms
13469261
419 ms
001_2016_11_mark_mdw_mop_shopteaser
427 ms
15831353
416 ms
14939832
417 ms
001_2016_11_sale_powerbook_shopteaser
442 ms
001_2016_11_mark_lacoste_shopteaser
444 ms
16063774
445 ms
15877771
447 ms
12776761
448 ms
001_2016_3_kamp_stoerer_loft_uni50
453 ms
001_2016_11_kamp_fashionkamp_fs16_uni50
486 ms
001_2015_10_serv_deutschland_schafft_platz_uni50
496 ms
001_2016_2_kamp_lieblingsoutfit_2_uni50
487 ms
1640985.gif
488 ms
9166235.gif
488 ms
google-play-badge.png
391 ms
OTTO-Icons.woff
237 ms
daily_deal.png
148 ms
001_2016_5_kund_nl_vorteil_470x250px.jpg
107 ms
sprite.png
178 ms
otto-sans.css
139 ms
otto-sans-bold.css
296 ms
otto-sans-thin.css
316 ms
public_non-critical_min.js
131 ms
public_non-critical_min.css
157 ms
getPerformanceMarketingData.js
408 ms
a_info
394 ms
14401902.gif
101 ms
shoppinghistory
386 ms
a2995.16030318.js
298 ms
1640683.gif
102 ms
1640592.gif
98 ms
1640269.gif
99 ms
1641162.gif
102 ms
1640844.gif
99 ms
1640970.gif
99 ms
1641018.gif
102 ms
3428349.gif
101 ms
1640701.gif
102 ms
1640445.gif
177 ms
1640351.gif
175 ms
001_2016_8_sais_nh_ostern_slideshow
215 ms
001_2016_11_waes_bademoden_slideshow
215 ms
15403117
175 ms
15090029
174 ms
15828949
236 ms
13451893
231 ms
11587003
229 ms
14184958
229 ms
15867141
235 ms
amount.json
364 ms
amount.json
450 ms
customerServiceWidget
431 ms
TpPFhwFVbCnfq0wGOJY79ug03egfvtxv781wKUFbhfre2Fbplp7ovGMaZ9yfpf+n+zwk+aAAA=
6 ms
ottolatency.gif
343 ms
wcJqEiKAAEAAAAKAAwADgAAAAAAAA==
4 ms
srp.js
722 ms
pi.aspx
626 ms
ottorum.gif
92 ms
ottonet.de accessibility score
ottonet.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
Page has valid source maps
ottonet.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ottonet.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ottonet.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.
ottonet.de
Open Graph description is not detected on the main page of Ottonet. 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: