8.3 sec in total
241 ms
7.6 sec
473 ms
Click here to check amazing Intelicel content. Otherwise, check out these important facts you probably never knew about intelicel.net
Visit intelicel.netWe analyzed Intelicel.net page load time and found that the first response time was 241 ms and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
intelicel.net performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value7.7 s
3/100
25%
Value7.1 s
31/100
10%
Value40 ms
100/100
30%
Value0.861
4/100
15%
Value8.3 s
40/100
10%
241 ms
71 ms
462 ms
124 ms
163 ms
Our browser made a total of 173 requests to load all elements on the main page. We found that 81% of them (140 requests) were addressed to the original Intelicel.net, 9% (15 requests) were made to Fonts.gstatic.com and 4% (7 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Intelicel.net.
Page size can be reduced by 3.2 MB (69%)
4.6 MB
1.4 MB
In fact, the total size of Intelicel.net main page is 4.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 475.4 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 65.8 kB, which is 13% 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 475.4 kB or 93% of the original size.
Potential reduce by 156.4 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. Obviously, Intelicel needs image optimization as it can save up to 156.4 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 899.9 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 899.9 kB or 74% of the original size.
Potential reduce by 1.6 MB
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. Intelicel.net needs all CSS files to be minified and compressed as it can save up to 1.6 MB or 89% of the original size.
Number of requests can be reduced by 117 (79%)
149
32
The browser has sent 149 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Intelicel. 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 46 to 1 for CSS and as a result speed up the page load time.
intelicel.net
241 ms
intelicel
71 ms
462 ms
wp-emoji-release.min.js
124 ms
settings.css
163 ms
css
23 ms
css
34 ms
css
37 ms
styles.css
142 ms
jquery.qtip.css
145 ms
default.css
147 ms
rounded.css
150 ms
settings.css
306 ms
style.css
315 ms
yith_wcas_ajax_search.css
308 ms
frontend.css
309 ms
yit-advanced-reviews.css
310 ms
ywot_style.css
311 ms
frontend.css
312 ms
prettyPhoto.css
317 ms
jquery.selectBox.css
319 ms
wishlist.css
320 ms
font-awesome.min.css
344 ms
style.css
402 ms
js_composer.css
595 ms
ie_assets.css
413 ms
responsive.css
395 ms
jquery.js
495 ms
jquery-migrate.min.js
468 ms
lightbox.js
478 ms
jquery.themepunch.tools.min.js
543 ms
jquery.themepunch.essential.min.js
550 ms
iphorm.js
552 ms
swfupload.js
559 ms
swfobject.js
565 ms
swfupload.swfobject.js
634 ms
swfupload.queue.js
634 ms
jquery.themepunch.revolution.min.js
703 ms
add-to-cart.min.js
632 ms
css
25 ms
vc_carousel.css
622 ms
picturefill.min.js
550 ms
woocommerce-add-to-cart.js
573 ms
ywar-attachments.js
574 ms
jquery.tooltipster.min.js
577 ms
ywot.js
613 ms
jquery.iphorm.js
592 ms
widget_v2.134.js
12 ms
jquery.form.min.js
639 ms
jquery.smooth-scroll.min.js
529 ms
jquery.qtip.min.js
521 ms
jquery.uniform.js
492 ms
jquery.infieldlabel.min.js
532 ms
rounded.js
525 ms
jquery.blockUI.min.js
569 ms
woocommerce.min.js
604 ms
jquery.cookie.min.js
597 ms
cart-fragments.min.js
612 ms
yith-autocomplete.min.js
601 ms
yith.infinitescroll.js
578 ms
yith-infs.js
577 ms
frontend.min.js
597 ms
jquery.prettyPhoto.min.js
593 ms
css
17 ms
css
15 ms
css
16 ms
bootstrap.min.css
597 ms
font-awesome.min.css
557 ms
yit-faq.css
562 ms
logos_slider.css
587 ms
owl.css
534 ms
yit-testimonial.css
556 ms
style.css
548 ms
style.css
533 ms
shortcodes.css
627 ms
widgets.css
521 ms
blog.css
521 ms
masterslider.css
585 ms
comment.css
539 ms
animate.css
538 ms
prettyPhoto.css
563 ms
scrollbar.css
535 ms
dynamics.css
552 ms
responsive.css
554 ms
jquery.prettyPhoto.init.min.js
607 ms
jquery.selectBox.min.js
604 ms
jquery.yith-wcwl.js
563 ms
contact.min.js
540 ms
google-api.js
540 ms
bootstrap.js
640 ms
jquery.commonlibraries.js
570 ms
internal.js
631 ms
woocommerce.js
589 ms
woocommerce_2.3.js
559 ms
jquery.scrollbar.js
551 ms
shortcodes.js
615 ms
owl.carousel.js
615 ms
jquery.placeholder.js
607 ms
masonry.min.js
573 ms
jquery.masonry.min.js
544 ms
common.js
540 ms
masterslider.min.js
594 ms
yit-testimonial-frontend.js
585 ms
wp-embed.min.js
569 ms
js_composer_front.js
534 ms
transition.js
599 ms
vc_carousel.js
581 ms
fondo-intelicel.jpg
436 ms
facebook.png
347 ms
intelicel-celulares-en-medellin-a-credito3.png
308 ms
intelicel-celulares-enmedellin.jpg
399 ms
carrito-intelicel5.png
399 ms
dummy.png
1430 ms
nokia.png
1426 ms
blackberry.png
1428 ms
google-company-motorola.png
1867 ms
htc.png
1431 ms
samsung.png
1866 ms
lg.png
1865 ms
sony.png
1864 ms
huawei.png
1865 ms
apple.png
1863 ms
300x200transparent.png
1865 ms
analytics.js
37 ms
collect
33 ms
__$$__stringtable_lang_es.js
47 ms
z5FX9Qd-HoKg9NPm1Znu5gLUuEpTyoUstqEm5AMlJo4.ttf
20 ms
fontawesome-webfont.woff
1569 ms
fontawesome-webfont.woff
1567 ms
recaptcha__it.js
1396 ms
file-upload-tick.png
442 ms
captcha-refresh-icon.png
443 ms
default-loading.gif
442 ms
error.png
444 ms
success.png
443 ms
avatar_simple_visitor.png
162 ms
aL63HcygAAVYuCCsAAA==
11 ms
sdk.js
907 ms
revolution.extension.slideanims.min.js
676 ms
revolution.extension.navigation.min.js
677 ms
1285 ms
input-active-bg-rep.png
160 ms
file-upload-progress-area.png
161 ms
file-progress-bar-bg.png
159 ms
file-close.png
160 ms
button-active-bg-rep.png
105 ms
mega-plaza-1.jpg
497 ms
slider-2.jpg
497 ms
smart-balance-2.jpg
445 ms
loader.gif
173 ms
k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf
26 ms
EInbV5DfGHOiMmvb1Xr-hpS3E-kSBmtLoNJPDtbj2Pk.ttf
27 ms
MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf
27 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
27 ms
DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf
28 ms
egfont.woff
223 ms
revicons.woff
97 ms
Samsung-Galaxy-S5.jpg
222 ms
Samsung-Galaxy-Gear.jpg
221 ms
htc-intelicel.jpg
133 ms
200 ms
xd_arbiter.php
76 ms
xd_arbiter.php
137 ms
PKCRbVvRfd5n7BTjtGiFZMDdSZkkecOE1hvV7ZHvhyU.ttf
13 ms
1ImRNPx4870-D9a1EBUdPMDdSZkkecOE1hvV7ZHvhyU.ttf
13 ms
JbtMzqLaYbbbCL9X6EvaI8DdSZkkecOE1hvV7ZHvhyU.ttf
12 ms
xkvoNo9fC8O2RDydKj12b8DdSZkkecOE1hvV7ZHvhyU.ttf
13 ms
CcKI4k9un7TZVWzRVT-T88DdSZkkecOE1hvV7ZHvhyU.ttf
53 ms
UAnF6lSK1JNc1tqTiG8pNALUuEpTyoUstqEm5AMlJo4.ttf
52 ms
-_Ctzj9b56b8RgXW8FAricDdSZkkecOE1hvV7ZHvhyU.ttf
53 ms
8KhZd3VQBtXTAznvKjw-k8DdSZkkecOE1hvV7ZHvhyU.ttf
52 ms
RJMlAoFXXQEzZoMSUteGWCZ2oysoEQEeKwjgmXLRnTc.ttf
53 ms
SonyXperiaHonamioZ1-intelicel.jpg
154 ms
intelicel.net 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
intelicel.net 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
intelicel.net 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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Intelicel.net 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 Intelicel.net 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.
intelicel.net
Open Graph description is not detected on the main page of Intelicel. 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: