3.7 sec in total
1 sec
2.5 sec
181 ms
Welcome to otto.ee homepage info - get ready to check Otto best content for Estonia right away, or after learning these important things about otto.ee
Responsible Commerce that inspires: Otto Group is a globally operating e-commerce and service group with around 41,000 employes.
Visit otto.eeWe analyzed Otto.ee page load time and found that the first response time was 1 sec and then it took 2.7 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.ee performance score
name
value
score
weighting
Value6.8 s
1/100
10%
Value10.5 s
0/100
25%
Value8.7 s
16/100
10%
Value260 ms
83/100
30%
Value0.366
29/100
15%
Value8.5 s
38/100
10%
1005 ms
225 ms
229 ms
233 ms
25 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 70% of them (47 requests) were addressed to the original Otto.ee, 15% (10 requests) were made to Static.xx.fbcdn.net and 7% (5 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Otto.ee.
Page size can be reduced by 221.7 kB (22%)
999.6 kB
777.9 kB
In fact, the total size of Otto.ee main page is 999.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. 45% of websites need less resources to load. Images take 736.5 kB which makes up the majority of the site volume.
Potential reduce by 86.9 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 45.0 kB, which is 47% 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 86.9 kB or 90% of the original size.
Potential reduce by 25.7 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. Otto images are well optimized though.
Potential reduce by 96.0 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 96.0 kB or 64% of the original size.
Potential reduce by 13.0 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.ee needs all CSS files to be minified and compressed as it can save up to 13.0 kB or 79% of the original size.
Number of requests can be reduced by 15 (24%)
63
48
The browser has sent 63 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 8 to 1 for CSS and as a result speed up the page load time.
otto.ee
1005 ms
index.css
225 ms
mod_login.css
229 ms
stylesheet.css
233 ms
css
25 ms
doc_frontp.css
238 ms
styles.css.php
236 ms
jquery-1.6.2.min.js
662 ms
product.js
338 ms
analytics.js
29 ms
logo.png
121 ms
bullet2.png
117 ms
button_search.gif
112 ms
bullet1.png
115 ms
bar2.png
119 ms
bar1.png
118 ms
turvaline_ostukoht_must.png
221 ms
1.jpg
444 ms
2.jpg
568 ms
3.jpg
472 ms
4.jpg
471 ms
5.jpg
472 ms
6.jpg
469 ms
7.jpg
665 ms
9.gif
586 ms
10.gif
585 ms
11.gif
585 ms
8.jpg
588 ms
arrow2.png
679 ms
75_110_9000074.jpg
702 ms
75_110_9000138.jpg
700 ms
75_110_9000316.jpg
703 ms
75_110_9000231.jpg
706 ms
75_110_9000299.jpg
774 ms
75_110_9000490.jpg
791 ms
75_110_9000284.jpg
817 ms
75_110_9000712.jpg
816 ms
75_110_9000722.jpg
821 ms
75_110_9000083.jpg
823 ms
75_110_9000226.jpg
884 ms
75_110_9000163.jpg
905 ms
75_110_9000032.jpg
932 ms
75_110_9000732.jpg
933 ms
75_110_9000238.jpg
938 ms
75_110_9000221.jpg
941 ms
arrow3.png
995 ms
collect
16 ms
likebox.php
143 ms
v8_72sD3DYMKyM0dn3LtWm4ooKQJV7rZJEeBgiz-w_g.ttf
20 ms
itc_avant_garde_gothic_condce_bold-webfont.woff
1037 ms
itc_avant_garde_ce_gothic_book-webfont.woff
1062 ms
footer_text.gif
943 ms
kyEKgjk51ZE.css
80 ms
xgj7bXhJNEH.css
98 ms
q68gy-v_YMF.js
133 ms
FJmpeSpHpjS.js
167 ms
0wM5s1Khldu.js
158 ms
1bNoFZUdlYZ.js
131 ms
12654469_1148200138546783_3320431074729289885_n.png
135 ms
11009201_1007447655955366_5704956906574242640_n.png
78 ms
11181322_1611733662440962_8642535419584070533_n.jpg
89 ms
1377995_669348379750014_1759312673_n.jpg
112 ms
10405686_415016505356221_3966952112732242816_n.jpg
88 ms
wL6VQj7Ab77.png
19 ms
s7jcwEQH7Sx.png
20 ms
I6-MnjEovm5.js
22 ms
pQrUxxo5oQp.js
22 ms
otto.ee 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.ee 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.ee 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otto.ee 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 Otto.ee 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.ee
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: