1.8 sec in total
149 ms
863 ms
775 ms
Click here to check amazing OZOM content for Chile. Otherwise, check out these important facts you probably never knew about ozom.com
Con Ozom 2.0 cualquier hogar puede ser Smart. Descubre lo fácil que es tener un hogar inteligente y accesible para todos. Aduéñate de tus espacios y vive una verdadera experiencia Smart.
Visit ozom.comWe analyzed Ozom.com page load time and found that the first response time was 149 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
ozom.com performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value6.2 s
11/100
25%
Value2.5 s
98/100
10%
Value20 ms
100/100
30%
Value0.03
100/100
15%
Value4.5 s
82/100
10%
149 ms
61 ms
13 ms
59 ms
47 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 86% of them (51 requests) were addressed to the original Ozom.com, 3% (2 requests) were made to Cstatic.weborama.fr and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (438 ms) belongs to the original domain Ozom.com.
Page size can be reduced by 154.4 kB (15%)
1.1 MB
906.7 kB
In fact, the total size of Ozom.com main page is 1.1 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. 40% of websites need less resources to load. Images take 828.0 kB which makes up the majority of the site volume.
Potential reduce by 26.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.7 kB, which is 20% 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 26.8 kB or 79% of the original size.
Potential reduce by 947 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. OZOM images are well optimized though.
Potential reduce by 98.3 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 98.3 kB or 60% of the original size.
Potential reduce by 28.4 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. Ozom.com needs all CSS files to be minified and compressed as it can save up to 28.4 kB or 80% of the original size.
Number of requests can be reduced by 26 (45%)
58
32
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OZOM. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
ozom.com
149 ms
products.js
61 ms
analytics.js
13 ms
adperf_conversion.js
59 ms
normalize.min.css
47 ms
style.css
80 ms
logoFondoBlanco.png
78 ms
nuevo_home.jpg
189 ms
appStore.png
99 ms
googlePlay.png
100 ms
modem.png
145 ms
enchufe.png
115 ms
ampolleta.png
152 ms
pack.png
172 ms
mano.png
260 ms
foto.jpg
305 ms
vid2.jpg
192 ms
vid3.jpg
190 ms
vid4.jpg
211 ms
vid5.jpg
257 ms
telefono.png
304 ms
producto1.png
316 ms
producto2.png
325 ms
producto3.png
303 ms
mobileMobile.png
326 ms
chile.jpg
339 ms
peru.jpg
340 ms
colombia.jpg
339 ms
brasil.jpg
359 ms
logoBlanco.png
360 ms
modal3.jpg
438 ms
collect
3 ms
collect
81 ms
6385.js
87 ms
fondo.jpg
293 ms
home.png
292 ms
videos.png
293 ms
myozom.png
318 ms
carro.png
314 ms
compartir.png
327 ms
contacto.png
328 ms
international_blanco.png
329 ms
triangulo_blanco.png
351 ms
der.png
362 ms
izq.png
364 ms
FuturaMdBTMedium.woff
366 ms
play.png
369 ms
maletin.png
386 ms
hombre.png
373 ms
recicla.png
357 ms
flechaAbajo.png
345 ms
sobre.png
327 ms
telefonito.png
312 ms
sociales.png
331 ms
flecha.png
332 ms
dispatch.fcgi
316 ms
media-queries.css
41 ms
src=5116512;type=invmedia;cat=jo2k9zrq;ord=3993467451073.2295
33 ms
jquery-1.10.2.min.js
86 ms
ozom.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
ozom.com 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
ozom.com SEO score
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ozom.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Ozom.com 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.
ozom.com
Open Graph description is not detected on the main page of OZOM. 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: