4 sec in total
359 ms
3.3 sec
344 ms
Welcome to otto.pl homepage info - get ready to check Otto best content right away, or after learning these important things about otto.pl
Responsible Commerce that inspires: Otto Group is a globally operating e-commerce and service group with around 41,000 employes.
Visit otto.plWe analyzed Otto.pl page load time and found that the first response time was 359 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
otto.pl performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value8.2 s
2/100
25%
Value6.8 s
34/100
10%
Value50 ms
100/100
30%
Value0.366
29/100
15%
Value7.5 s
47/100
10%
359 ms
594 ms
870 ms
272 ms
282 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Otto.pl, 83% (48 requests) were made to Otto.de and 7% (4 requests) were made to De.sitestat.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Otto.de.
Page size can be reduced by 1.0 MB (54%)
1.9 MB
886.5 kB
In fact, the total size of Otto.pl main page is 1.9 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. 35% of websites need less resources to load. CSS take 914.1 kB which makes up the majority of the site volume.
Potential reduce by 35.8 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 6.5 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 35.8 kB or 83% of the original size.
Potential reduce by 463.4 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. Obviously, Otto needs image optimization as it can save up to 463.4 kB or 59% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 118.6 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 118.6 kB or 63% of the original size.
Potential reduce by 424.1 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. Otto.pl needs all CSS files to be minified and compressed as it can save up to 424.1 kB or 46% of the original size.
Number of requests can be reduced by 20 (39%)
51
31
The browser has sent 51 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 9 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
otto.pl
359 ms
index.php
594 ms
design.css
870 ms
navigation.css
272 ms
jquery.fancybox.css
282 ms
jquery.jcarousel.css
270 ms
jquery.jcarousel.clipboard.css
274 ms
jquery.dd.css
275 ms
jquery.js
526 ms
jquery.fancybox.js
440 ms
jquery.jcarousel.js
440 ms
jquery.dd.js
445 ms
design.js
369 ms
sitestatFunction.js
459 ms
sitestat.js
528 ms
ga.js
76 ms
jquery.tools.min.js
527 ms
bg_grid.png
106 ms
clipboard.png
118 ms
spacer-metanav.gif
107 ms
button-search.gif
106 ms
trans.gif
105 ms
buttons_header.png
117 ms
logo.png
183 ms
Header-otto.com-januar-fin.jpg
1037 ms
Moebel-PM_Teaser-c56bfa5d9abe00ag27269861ebb93123.jpg
354 ms
Hermes_Lieferzeitfenster.jpg
267 ms
twoforfashion.png
206 ms
roombeez.png
210 ms
reblog.png
272 ms
soulfully.png
296 ms
facebook.png
299 ms
twitter.png
393 ms
youtube.png
368 ms
googlePlus.png
385 ms
kennzahlen.jpg
472 ms
karriere_9016-e62c5bf1e76f683g8baf28ff8c88911d.jpg
440 ms
teaser-trends-2d1f06ef8ba9533g636bcd02920b2313.jpg
461 ms
bv_neu_4-c3fe2f92bdc57d4ga1c05d349a12864b.jpg
655 ms
teaser_E-Commerce-d67b65979069d3bgfa36aeeea3dbdf2e.jpg
488 ms
logo-bottom.png
563 ms
intern-c1.png
546 ms
intern-c5.png
559 ms
TpPFhwFVbCnfq0wGOJY79ug03egfvtxv781wKUFbhfre2Fbplp7ovGMaZ9yfpf+n+zwk+aAAA=
11 ms
socialMedia-icons-start.png
561 ms
intern-c4.png
623 ms
link-standard.png
633 ms
buttons_bottom.png
638 ms
LTfwgL+NLOuE4O+UYTcGoicZjiBrxByTIVD0hFFzP5j4uqzH+2ZOLy1U8Sgmu6zkt0qvISVn78BUO2+9U=
12 ms
__utm.gif
67 ms
9g7CAT+2M69SQbzQBpyYShyluwBtULLPmAVXTxUz+46KU+c+WTFy++llCcE3XeYlOKS9h5ccfQS371A==
30 ms
s
1006 ms
getSocialMediaFeeds.php
711 ms
getSocialMediaFeeds.php
884 ms
getSocialMediaFeeds.php
796 ms
s
1015 ms
s
283 ms
s
271 ms
otto.pl 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-hidden="true"] elements contain focusable descendents
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
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.
otto.pl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
otto.pl 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
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otto.pl can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Otto.pl 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.pl
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: