4 sec in total
137 ms
3.6 sec
185 ms
Welcome to ecocel.mx homepage info - get ready to check Ecocel best content for Mexico right away, or after learning these important things about ecocel.mx
Ecocel - Tu mejor compañero
Visit ecocel.mxWe analyzed Ecocel.mx page load time and found that the first response time was 137 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster. This domain responded with an error, which can significantly jeopardize Ecocel.mx rating and web reputation
ecocel.mx performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value5.0 s
27/100
25%
Value5.5 s
54/100
10%
Value230 ms
86/100
30%
Value0.37
29/100
15%
Value4.8 s
79/100
10%
137 ms
1818 ms
94 ms
120 ms
100 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 61% of them (89 requests) were addressed to the original Ecocel.mx, 8% (12 requests) were made to Apis.google.com and 6% (8 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Ecocel.mx.
Page size can be reduced by 916.7 kB (60%)
1.5 MB
609.8 kB
In fact, the total size of Ecocel.mx main page is 1.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. 75% 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 528.1 kB which makes up the majority of the site volume.
Potential reduce by 61.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. 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 61.4 kB or 82% of the original size.
Potential reduce by 59.1 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, Ecocel needs image optimization as it can save up to 59.1 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 354.5 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 354.5 kB or 69% of the original size.
Potential reduce by 441.8 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. Ecocel.mx needs all CSS files to be minified and compressed as it can save up to 441.8 kB or 84% of the original size.
Number of requests can be reduced by 74 (54%)
138
64
The browser has sent 138 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ecocel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
ecocel.mx
137 ms
1818 ms
mod_bannerslider.css
94 ms
style.css
120 ms
style_ie7.css
100 ms
modal.css
109 ms
k2.css
106 ms
system.css
111 ms
general.css
166 ms
addons.css
166 ms
layout.css
167 ms
template.css
176 ms
joomla.css
185 ms
gk_stuff.css
186 ms
typo.css
219 ms
vm_major.css
213 ms
vm_gk_flypage.css
219 ms
browse_notables.css
232 ms
css3.css
236 ms
style3.css
228 ms
mootools.js
326 ms
domready_fix.js
254 ms
modal.js
281 ms
k2.js
293 ms
caption.js
292 ms
mega.css
279 ms
mega.js
316 ms
gk.script.js
330 ms
mod_bannerslider.js
348 ms
jquery.min.js
26 ms
slider.js
376 ms
slider-ie7.js
333 ms
widget.js
82 ms
plusone.js
85 ms
in.js
11 ms
main_bg.jpg
260 ms
nuevo%20logo%202.png
226 ms
ofetas2.jpg
196 ms
ofetas1.jpg
196 ms
banner-bb.png
199 ms
htc%202014%202.png
340 ms
banner-iphone.png
358 ms
banner-lg.png
358 ms
banner-samsung.png
487 ms
banner-moto.png
389 ms
banners--nokia.png
394 ms
banners--sonye.png
422 ms
banner-alcatel.png
484 ms
t-DSEU10.jpg
479 ms
CENTROS_DE_CARGA_549da388d72f3_100x90.jpg
478 ms
TOUCH_SAMSUNG_S5_54a1911ce2c28_100x90.jpg
485 ms
LCD_SAMSUNG_S385_54f095937f9bd_100x90.jpg
483 ms
t-DBB8220.jpg
512 ms
LCD_NOKIA_N303_54a17b732b8f9_100x90.jpg
547 ms
SONY_ERICSSON__B_54ef87de812a6_100x90.jpg
519 ms
t-DLGKP570.jpg
518 ms
t-TSEW150.jpg
513 ms
t-DSEW100i.jpg
516 ms
LCD_SONY_ERICSSO_54a17cf876252_100x90.jpg
580 ms
t-DSEW595.jpg
597 ms
FLEXOR_SONY_ERIC_549db849f2e7a_100x90.jpg
580 ms
t-FIPH2GANT.jpg
574 ms
t-DBB9700V2.jpg
575 ms
noimage.gif
590 ms
t-BAPIPH4G.jpg
623 ms
t-BAPIPH3G.jpg
624 ms
t-DSAA777.jpg
633 ms
piwik.js
638 ms
LCD___TOUCH_SAMS_549dbcdd93ad8_100x90.jpg
638 ms
FLEXOR_SAMSUNG_S_549db7b56ef71_100x90.jpg
620 ms
FLEXOR_SAMSUNG_B_549db7081d516_100x90.jpg
639 ms
widgets.js
104 ms
cb=gapi.loaded_0
31 ms
cb=gapi.loaded_1
26 ms
cb=gapi.loaded_2
46 ms
badge
139 ms
secureAnonymousFramework
107 ms
all.js
38 ms
uploads
72 ms
postmessageRelay
124 ms
subscribe_widget
201 ms
189 ms
xd_arbiter.php
60 ms
xd_arbiter.php
166 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
293 ms
t-FBB9650JOY.jpg
494 ms
t-FBB9500prin.jpg
492 ms
t-FBB8530JOY.jpg
470 ms
rs=AGLTcCPol5LxJ8VE8vsY9K9nUlO762ujLA
19 ms
rs=AGLTcCOJ4AMNA1EZSgGPzZnainRbXAPPWA
35 ms
rs=AGLTcCP6UXflGmKIuWe_n5R28T__wpu8xQ
35 ms
t-FBB8350TEC.jpg
470 ms
photo.jpg
112 ms
3193398744-postmessagerelay.js
126 ms
rpc:shindig_random.js
100 ms
rs=AGLTcCP6UXflGmKIuWe_n5R28T__wpu8xQ
38 ms
logo1-289x145-px.jpg
436 ms
grlryt2bdKIyfMSOhzd1eA.woff
115 ms
d-QWLnp4didxos_6urzFtg.woff
137 ms
vxNK-E6B13CyehuDCmvQvw.woff
149 ms
qr_code-ecocel.png
418 ms
www-core-vflL2i7T6.css
66 ms
www-pageframe-vflf2xejO.css
112 ms
www-the-rest-vflDnl7Oj.css
139 ms
menu_logo.gif
406 ms
cart_icon.png
387 ms
rs=AGLTcCP6UXflGmKIuWe_n5R28T__wpu8xQ
43 ms
cb=gapi.loaded_0
9 ms
menu_lvl1_bg.png
349 ms
menu_lvl1_bullet.png
354 ms
submenu_line.png
347 ms
subsubmenu_line.png
315 ms
search_icon.png
313 ms
moduletable_title.png
317 ms
fb12-right.png
332 ms
fb_loading.gif
334 ms
tw12-right.png
352 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
43 ms
gp12-right.png
339 ms
yt12-right.png
339 ms
li12-right.png
338 ms
button.png
348 ms
jot
105 ms
button-h.png
61 ms
xdrpc.html
49 ms
like_box.php
69 ms
public_profile
245 ms
profile
290 ms
410ucuAGgaJ.css
37 ms
tSbl8xBI27R.css
40 ms
q68gy-v_YMF.js
39 ms
FJmpeSpHpjS.js
64 ms
0wM5s1Khldu.js
37 ms
1bNoFZUdlYZ.js
63 ms
I6-MnjEovm5.js
23 ms
pQrUxxo5oQp.js
24 ms
css
23 ms
anonymoususerspace
74 ms
js
27 ms
css
33 ms
css
55 ms
js
7 ms
3e07384.jpg
49 ms
sprite_connect_v13.png
25 ms
icon_no_company_logo_60x60.png
5 ms
ecocel.mx 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.
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
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.
ecocel.mx 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
ecocel.mx 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 Ecocel.mx 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 Ecocel.mx 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.
ecocel.mx
Open Graph description is not detected on the main page of Ecocel. 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: