3.2 sec in total
298 ms
2.4 sec
482 ms
Visit otto.de now to see the best up-to-date OTTO content for Germany and also check out these interesting facts you probably never knew about otto.de
OTTO Online-Shop » Über 4.000 Marken entdecken ✓ Aktuelle Trends ✓ Top Service » Ratenkauf ✓ Altgeräte-Mitnahme ✓ Aufbauservice ✓ Jetzt shoppen!
Visit otto.deWe analyzed Otto.de page load time and found that the first response time was 298 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
otto.de performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value14.0 s
0/100
25%
Value16.8 s
0/100
10%
Value12,190 ms
0/100
30%
Value0.099
90/100
15%
Value20.3 s
2/100
10%
298 ms
566 ms
1081 ms
694 ms
285 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 56% of them (39 requests) were addressed to the original Otto.de, 33% (23 requests) were made to I.otto.de and 11% (8 requests) were made to Static.otto.de. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Otto.de.
Page size can be reduced by 164.5 kB (46%)
356.6 kB
192.1 kB
In fact, the total size of Otto.de main page is 356.6 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. 50% of websites need less resources to load. HTML takes 197.4 kB which makes up the majority of the site volume.
Potential reduce by 164.1 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 164.1 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. OTTO images are well optimized though.
Potential reduce by 71 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 389 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. Otto.de has all CSS files already compressed.
Number of requests can be reduced by 30 (44%)
68
38
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OTTO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
otto.de
298 ms
www.otto.de
566 ms
assets.polyfills.head.js
1081 ms
assets.global-resources.legacy.nomodule.6d3bca70.js
694 ms
assets.global-resources.head.0dcd88f0.css
285 ms
assets.global-resources.head.nomodule.6ed75915.js
296 ms
quality.shop-assets.quality_beacon.nomodule.d3a5a04c.js
278 ms
assets.global-pattern.main.973b780e.css
296 ms
assets.global-pattern.main.nomodule.c7fa9612.js
299 ms
assets.components.main.module.uaSK4fat.js
695 ms
assets.components.main.DCmXkVBO.css
295 ms
sho.shoppages.assets-public.fc08fa0c.css
277 ms
sho.shoppages.assets-public.nomodule.14a6dd04.js
281 ms
sho.shoppages.assets-private.0c8c2a75.css
282 ms
reptile.header.head.7e00a829.css
282 ms
squirrel.stomachshop.searchbar.module.ssmF8c8w.js
467 ms
squirrel.stomachshop.searchbar.hi0CZAWL.css
374 ms
ft1.wishlist-view.miniWishlist.6306a45b.css
290 ms
ft1.order-core.minibasket.8fd79c46.css
292 ms
assets.global-resources.body.nomodule.e8f2ebe3.js
215 ms
tracking.bct.bct.nomodule.f40de3eb.js
289 ms
ft7bcn.wato.onsite.534a0894.css
384 ms
ft9bcn.up-teaser.up_teaser_no_content_app.nomodule.95e61af1.js
383 ms
ft3.promo.aggregation.css.NMAj9MPh.css
384 ms
ft3.promo.aggregation.module.zLBuY-Py.js
384 ms
001_2021_42_sale_angebote_der_woche_kleine_shoppromotion_design_189584
162 ms
001_2021_42_sale_deal_des_tages_kleine_shoppromotion_design_189585
162 ms
mpp360_51460_62485
161 ms
mpp360_78403_86382
189 ms
001_2022_29_sale_tmr_kleine_shoppromotion_266383
168 ms
mpp360_92162_103335
163 ms
001_2021_42_sale_unser_tipp_kleine_shoppromotion_design_189587
191 ms
184 ms
163 ms
166 ms
164 ms
171 ms
169 ms
168 ms
171 ms
172 ms
173 ms
177 ms
176 ms
174 ms
178 ms
3ef8444476f42313ad64fba0781203dd
179 ms
mpp360_90095_102208
253 ms
pl_logo_otto.svg
123 ms
pl_logo_app-store.svg
120 ms
pl_logo_play-store.svg
122 ms
pl_icon_close.svg
164 ms
pl_icon_search.svg
165 ms
pl_icon_arrow-left.svg
166 ms
pl_icon_arrow-right.svg
160 ms
pl_icon_basket.svg
157 ms
pl_logo_otto-app.svg
158 ms
pl_icon_voucher.svg
159 ms
pl_icon_person.svg
96 ms
pl_icon_feedback.svg
96 ms
pl_logo_ehi.svg
98 ms
pl_logo_sepa.svg
97 ms
pl_logo_paypal.svg
99 ms
pl_icon_check.svg
149 ms
pl_logo_pinterest.svg
186 ms
pl_logo_facebook.svg
187 ms
pl_logo_twitter.svg
189 ms
pl_logo_youtube.svg
190 ms
pl_logo_instagram.svg
186 ms
pl_logo_slogan.svg
240 ms
otto.de 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
button, link, and menuitem elements do not have accessible names.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
otto.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Page has valid source maps
otto.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 Otto.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 Otto.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.
otto.de
Open Graph description is not detected on the main page of OTTO. 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: