4.6 sec in total
680 ms
3.6 sec
356 ms
Welcome to otter.ro homepage info - get ready to check Otter best content for Romania right away, or after learning these important things about otter.ro
Peste 4500 modele de incaltaminte si genti. ✓Livrare rapida si retur gratuit la orice comanda. Descopera acum noua colectie!
Visit otter.roWe analyzed Otter.ro page load time and found that the first response time was 680 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.
otter.ro performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value9.4 s
0/100
25%
Value12.7 s
3/100
10%
Value2,640 ms
4/100
30%
Value0.004
100/100
15%
Value25.5 s
0/100
10%
680 ms
346 ms
274 ms
188 ms
186 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 57% of them (75 requests) were addressed to the original Otter.ro, 11% (14 requests) were made to Static.xx.fbcdn.net and 3% (4 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Otter.ro.
Page size can be reduced by 1.6 MB (43%)
3.8 MB
2.2 MB
In fact, the total size of Otter.ro main page is 3.8 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. 60% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 84.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. 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 84.8 kB or 81% of the original size.
Potential reduce by 82.0 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. Otter images are well optimized though.
Potential reduce by 1.2 MB
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 1.2 MB or 75% of the original size.
Potential reduce by 289.9 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. Otter.ro needs all CSS files to be minified and compressed as it can save up to 289.9 kB or 86% of the original size.
Number of requests can be reduced by 79 (63%)
125
46
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otter. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 61 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.otter.ro
680 ms
73924a.js
346 ms
styles2.css
274 ms
button.css
188 ms
button.css
186 ms
button.css
185 ms
rwd.css
189 ms
amazon.css
186 ms
mirasvit_searchindex.css
275 ms
prototype.js
461 ms
jquery-1.10.2.min.js
411 ms
noconflict.js
288 ms
ccard.js
288 ms
validation.js
409 ms
builder.js
410 ms
effects.js
410 ms
dragdrop.js
410 ms
controls.js
455 ms
slider.js
456 ms
js.js
467 ms
form.js
469 ms
translate.js
470 ms
cookies.js
544 ms
jquery-1.10.2.min.js
636 ms
jquery.min.js
640 ms
underscore.js
555 ms
backbone.js
557 ms
form.js
560 ms
autocomplete.js
632 ms
modernizr.custom.min.js
645 ms
selectivizr.js
647 ms
matchMedia.js
647 ms
matchMedia.addListener.js
722 ms
enquire.js
724 ms
app.js
729 ms
jquery.cycle2.min.js
734 ms
jquery.cycle2.swipe.min.js
735 ms
css
25 ms
conversion.js
18 ms
madisonisland.css
661 ms
slideshow.js
637 ms
imagesloaded.js
639 ms
minicart.js
643 ms
visitor.js
178 ms
font-awesome.min.css
443 ms
css
21 ms
analytics.js
21 ms
fbds.js
20 ms
otter-logo-nou-mic.png
242 ms
logo_white.png
159 ms
logo.gif
160 ms
Noua%20colectie.jpg
409 ms
Femei.jpg
503 ms
Barbati.jpg
558 ms
Copii.jpg
503 ms
Genti,%20posete,%20accesorii.jpg
580 ms
Produse%20de%20ingrijire.jpg
558 ms
Reduceri.jpg
595 ms
clarks-hp.jpg
585 ms
geox-hp.jpg
588 ms
epica-hp.jpg
648 ms
otter-hp.jpg
648 ms
gryxx-hp.jpg
669 ms
pantofi-dama.jpg
676 ms
pantofi-barbati.jpg
683 ms
marochinarie.jpg
687 ms
DSC_8971_1.jpg
737 ms
dsc_9296_2.jpg
738 ms
DSC_8268.JPG
760 ms
DSC_8132.JPG
766 ms
DSC_8578_1.jpg
775 ms
DSC_8057.JPG
777 ms
DSC_8300.JPG
833 ms
DSC_8182.JPG
833 ms
catalog.jpg
1030 ms
abonare-newsletter.jpg
1035 ms
produse-de-ingrijire-hp.jpg
955 ms
fidelity_card_footer.jpg
870 ms
mobilpay%20(1).png
917 ms
logo-trusted-vertical.png
922 ms
tracker.js
525 ms
gtm.js
148 ms
122 ms
collect
34 ms
collect
192 ms
fontawesome-webfont.woff
1008 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
110 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
160 ms
sdk.js
108 ms
onclick-order.png
955 ms
mask.png
959 ms
trk.js
259 ms
tag.js
143 ms
141 ms
collect
53 ms
collect
32 ms
94 ms
ga-audiences
91 ms
ga-audiences
89 ms
88 ms
xd_arbiter.php
61 ms
xd_arbiter.php
108 ms
capture-apps-4.8.0.js
41 ms
iframeStorage.html
131 ms
jquery.min.js
253 ms
iframeStorage.js
8 ms
s.js
301 ms
e.js
337 ms
widget.js
390 ms
widget.js
390 ms
e.js
289 ms
appsmanagerinit
237 ms
trk.php
134 ms
e.js
130 ms
8 ms
page.php
140 ms
o_zjiOVHPPW.css
41 ms
AIusK7M5MGT.css
49 ms
_rx8naC75Dy.js
70 ms
t-KLv3gqZy0.js
64 ms
uLtKx7ldlvR.js
86 ms
wyIfBc7KBcg.js
99 ms
wFYNJ9lyaMJ.js
99 ms
Xs81m_2832G.js
98 ms
11666102_1730845407201945_3225678045829161476_n.jpg
119 ms
11016837_1602543850032102_1317635810266962624_n.png
27 ms
wL6VQj7Ab77.png
12 ms
CSXXCvknpgK.png
12 ms
R9a_DtVRZgv.js
9 ms
cUDgRFxaoIk.js
8 ms
0JBr1QHp8Gi.js
9 ms
kDOzhTr2W91.js
9 ms
otter.ro 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 input fields do not have accessible names
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
otter.ro 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
Page has valid source maps
otter.ro 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
RO
RO
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Otter.ro can be misinterpreted by Google and other search engines. Our service has detected that Romanian is used on the page, and it matches the claimed language. Our system also found out that Otter.ro 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.
otter.ro
Open Graph description is not detected on the main page of Otter. 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: