3.6 sec in total
488 ms
2.9 sec
196 ms
Welcome to octilus.es homepage info - get ready to check Octilus best content right away, or after learning these important things about octilus.es
Tienda creada con PrestaShop
Visit octilus.esWe analyzed Octilus.es page load time and found that the first response time was 488 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
octilus.es performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value18.4 s
0/100
25%
Value11.2 s
5/100
10%
Value2,230 ms
6/100
30%
Value0.067
97/100
15%
Value18.6 s
3/100
10%
488 ms
226 ms
240 ms
254 ms
157 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Octilus.es, 11% (10 requests) were made to Static.xx.fbcdn.net and 6% (6 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (997 ms) relates to the external source Octilus.com.
Page size can be reduced by 660.8 kB (46%)
1.4 MB
778.4 kB
In fact, the total size of Octilus.es main page is 1.4 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 615.3 kB which makes up the majority of the site volume.
Potential reduce by 60.6 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 60.6 kB or 80% of the original size.
Potential reduce by 20.6 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. Octilus images are well optimized though.
Potential reduce by 436.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 436.6 kB or 75% of the original size.
Potential reduce by 143.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. Octilus.es needs all CSS files to be minified and compressed as it can save up to 143.0 kB or 85% of the original size.
Number of requests can be reduced by 51 (56%)
91
40
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Octilus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
octilus.com
488 ms
fb5eb79e534f0b8151ee0986ca39e92c_1443612724.css
226 ms
jquery.js
240 ms
prototype.js
254 ms
ccard.js
157 ms
validation.js
162 ms
builder.js
163 ms
effects.js
271 ms
dragdrop.js
274 ms
controls.js
277 ms
slider.js
302 ms
js.js
312 ms
form.js
313 ms
script.js
314 ms
translate.js
323 ms
cookies.js
324 ms
jquery.jqtransform.js
379 ms
functions.js
389 ms
jquery.hover.intent.js
390 ms
instorepickup.js
391 ms
jquery.easing.1.3.min.js
405 ms
jquery.slider.js
405 ms
efects.js
455 ms
on4u.js
467 ms
respond.min.js
472 ms
matchMedia.js
473 ms
menu1.css
484 ms
mobile.css
488 ms
ga.js
22 ms
es.gif
106 ms
logo_octilus_com.png
107 ms
banner_ES_becool_blue3_1105.jpg
337 ms
banner_SPT_2_ES_1105.jpg
171 ms
banner_ES_becool_new_1105.jpg
337 ms
soportes.jpg
315 ms
i6.jpg
308 ms
SPT-SSP-LG099.jpg
156 ms
throbber.gif
235 ms
P8-LITE.jpg
248 ms
SST-BQ023.jpg
318 ms
TPU-BQ023-WOO3.jpg
335 ms
SGP11415-1.jpg
454 ms
samsung-grand-prime.jpg
455 ms
banner_footer_1.png
457 ms
banner_footer_2.png
458 ms
banner_footer_3.png
457 ms
banner_footer_4.png
459 ms
banner_footer_5.png
461 ms
GoogleMaps.png
467 ms
Mail.png
476 ms
Phone.png
492 ms
Facebook.png
495 ms
Google.png
496 ms
Twitter.png
537 ms
Blogger.png
545 ms
Pinterest.png
550 ms
Tumblr.png
570 ms
Linked.png
575 ms
YouTube.png
575 ms
banner_footer_face_es.png
614 ms
cart_icon.png
617 ms
__utm.gif
29 ms
toplinksap.png
593 ms
slide-point2.png
609 ms
slide-point.png
618 ms
controls-sprite-prev.png
618 ms
collect
59 ms
997 ms
controls-sprite-next.png
588 ms
ga-audiences
46 ms
likebox.php
196 ms
prev-horizontal.png
555 ms
next-horizontal.png
560 ms
li-arr.png
508 ms
McLpmVM3wCm.css
28 ms
r6Aw0SZFbhw.css
31 ms
q68gy-v_YMF.js
42 ms
FJmpeSpHpjS.js
66 ms
0wM5s1Khldu.js
39 ms
1bNoFZUdlYZ.js
38 ms
12208595_10153089423006020_5404279686884759078_n.jpg
65 ms
12079450_10153024318961020_1330175905610885030_n.png
19 ms
12187768_1517312878580004_7211110615694996512_n.jpg
23 ms
33777_157953727555955_6560797_n.jpg
20 ms
12360038_10153797688492838_7713906200911792875_n.jpg
20 ms
11062776_858082574260648_2106835425956388188_n.jpg
21 ms
wL6VQj7Ab77.png
15 ms
s7jcwEQH7Sx.png
15 ms
I6-MnjEovm5.js
7 ms
pQrUxxo5oQp.js
2 ms
btn-cart.png
78 ms
item_avisame.png
79 ms
ca3534c88964ff242f8f4d979bb22719_1354201816.css
78 ms
nr-892.min.js
22 ms
octilus.es accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
octilus.es 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
octilus.es 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
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 Octilus.es 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 Octilus.es 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.
octilus.es
Open Graph description is not detected on the main page of Octilus. 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: