2.4 sec in total
578 ms
1.5 sec
329 ms
Visit oelux.com now to see the best up-to-date Oelux content and also check out these interesting facts you probably never knew about oelux.com
Iluminación de vanguardia., Iluminación de Vanguardia
Visit oelux.comWe analyzed Oelux.com page load time and found that the first response time was 578 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
oelux.com performance score
578 ms
295 ms
130 ms
130 ms
24 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 92% of them (55 requests) were addressed to the original Oelux.com, 5% (3 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (578 ms) belongs to the original domain Oelux.com.
Page size can be reduced by 609.6 kB (24%)
2.5 MB
1.9 MB
In fact, the total size of Oelux.com main page is 2.5 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. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 14.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. This page needs HTML code to be minified as it can gain 2.5 kB, which is 14% 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 14.1 kB or 81% of the original size.
Potential reduce by 136.2 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. Oelux images are well optimized though.
Potential reduce by 310.7 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 310.7 kB or 75% of the original size.
Potential reduce by 148.6 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. Oelux.com needs all CSS files to be minified and compressed as it can save up to 148.6 kB or 86% of the original size.
Number of requests can be reduced by 28 (51%)
55
27
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oelux. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
oelux.com
578 ms
style.css
295 ms
responsive.css
130 ms
blue-color.css
130 ms
css
24 ms
prettyPhoto.css
178 ms
font-awesome.min.css
168 ms
layer-slider.css
135 ms
flexslider.css
175 ms
revolution-slider.css
162 ms
jquery.min.js
304 ms
jquery-ui.js
23 ms
flex-slider.min.js
245 ms
navigation.min.js
251 ms
jquery.layerslider.js
342 ms
layerslider.transitions.js
300 ms
map.min.js
278 ms
carousel.js
341 ms
jquery.theme.plugins.min.js
350 ms
jquery.themepunch.revolution.min.js
354 ms
flickr.js
352 ms
instagram.js
353 ms
jquery.twitter.js
352 ms
prettyPhoto.min.js
353 ms
jquery.tooltips.min.js
368 ms
isotope.min.js
365 ms
scrolltopcontrol.js
379 ms
jquery.easy-pie-chart.js
373 ms
jquery.transit.min.js
376 ms
custom.js
387 ms
skin.css
163 ms
body-bg-1.jpg
49 ms
logo.png
86 ms
shadow-top.png
64 ms
shadow-bottom.png
72 ms
slide1-bg.jpg
323 ms
slide0-1.png
267 ms
toggle.png
109 ms
slide-bg.jpg
223 ms
slide3-bg.jpg
226 ms
slide3-bg.png
222 ms
producto-01.jpg
226 ms
producto-02.jpg
224 ms
producto-03.jpg
233 ms
producto-04.jpg
247 ms
vineta.png
247 ms
portfolio-item-1.jpg
290 ms
portfolio-item-2.jpg
352 ms
portfolio-item-3.jpg
344 ms
portfolio-item-4.jpg
373 ms
portfolio-item-5.jpg
311 ms
portfolio-item-6.jpg
425 ms
top.png
388 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
12 ms
HqHm7BVC_nzzTui2lzQTDaCWcynf_cDxXwCLxiixG1c.ttf
11 ms
bH7276GfdCjMjApa_dkG6aCWcynf_cDxXwCLxiixG1c.ttf
14 ms
fontawesome-webfont.woff
383 ms
slider-prev.png
180 ms
slider-next.png
174 ms
skin.png
187 ms
oelux.com SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oelux.com 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 Oelux.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.
oelux.com
Open Graph description is not detected on the main page of Oelux. 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: