6 sec in total
1.5 sec
4 sec
540 ms
Visit icel.edu.mx now to see the best up-to-date ICEL content for Mexico and also check out these interesting facts you probably never knew about icel.edu.mx
Visit icel.edu.mxWe analyzed Icel.edu.mx page load time and found that the first response time was 1.5 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
icel.edu.mx performance score
name
value
score
weighting
Value15.5 s
0/100
10%
Value24.5 s
0/100
25%
Value15.5 s
0/100
10%
Value5,580 ms
0/100
30%
Value0.037
100/100
15%
Value33.0 s
0/100
10%
1532 ms
44 ms
38 ms
48 ms
17 ms
Our browser made a total of 217 requests to load all elements on the main page. We found that 48% of them (104 requests) were addressed to the original Icel.edu.mx, 10% (21 requests) were made to Maps.google.com and 10% (21 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Icel.edu.mx.
Page size can be reduced by 1.5 MB (24%)
6.2 MB
4.8 MB
In fact, the total size of Icel.edu.mx main page is 6.2 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. Images take 4.6 MB which makes up the majority of the site volume.
Potential reduce by 92.9 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 92.9 kB or 80% of the original size.
Potential reduce by 278.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. ICEL images are well optimized though.
Potential reduce by 832.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 832.5 kB or 68% of the original size.
Potential reduce by 263.3 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. Icel.edu.mx needs all CSS files to be minified and compressed as it can save up to 263.3 kB or 84% of the original size.
Number of requests can be reduced by 126 (60%)
211
85
The browser has sent 211 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ICEL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 63 to 1 for JavaScripts and from 42 to 1 for CSS and as a result speed up the page load time.
icel.edu.mx
1532 ms
k2.css
44 ms
font-awesome.css
38 ms
widgetkit-24689a6e.css
48 ms
style.css
17 ms
mootools-core.js
71 ms
core.js
41 ms
jquery.min.js
101 ms
jquery-noconflict.js
66 ms
jquery-migrate.min.js
66 ms
k2.js
65 ms
widgetkit-816e61bd.js
66 ms
engine.jquery.js
93 ms
base.css
93 ms
layout.css
92 ms
menus.css
94 ms
modules.css
95 ms
tools.css
95 ms
system.css
95 ms
extensions.css
96 ms
custom.css
134 ms
animations.css
130 ms
red.css
130 ms
dots.css
132 ms
ubuntu.css
131 ms
ubuntu.css
134 ms
bebas.css
137 ms
style.css
136 ms
print.css
136 ms
ubuntu.css
136 ms
bebas.css
136 ms
warp.js
137 ms
accordionmenu.js
140 ms
dropdownmenu.js
139 ms
template.js
137 ms
tagcanvas.min.js
139 ms
platform.js
141 ms
srizontb.css
129 ms
mag-popup.css
110 ms
elastislide.css
109 ms
modernizr.js
106 ms
srizonjq1.8.min.js
95 ms
srizonjq.easing.1.3.min.js
93 ms
srizontb2.js
86 ms
mag-popup.js
88 ms
elastislide.js
86 ms
jusertubeslider.js
89 ms
javascript.php
65 ms
search.js
61 ms
lightbox.js
37 ms
mediaelement-and-player.js
111 ms
spotlight.js
33 ms
base.css
31 ms
layout.css
37 ms
menus.css
37 ms
modules.css
40 ms
tools.css
38 ms
system.css
33 ms
system.css
37 ms
system-all.css
34 ms
print.css
33 ms
all.js
170 ms
plusone.js
89 ms
ip_query.php
272 ms
page.png
24 ms
camp2015-16.png
170 ms
campus-julio-2014.jpg
168 ms
20150825ui01.jpg
222 ms
00.jpg
183 ms
20150825ui02.jpg
180 ms
20150825ui03.jpg
180 ms
20150825ui04.jpg
386 ms
20150825ui05.jpg
239 ms
20150825ui06.jpg
336 ms
20150825ui07.jpg
386 ms
20150825ui08.jpg
388 ms
big_bachillerato.png
239 ms
big_licenciatura.png
254 ms
big_especialidad.png
258 ms
big_maestria.png
287 ms
ui_servicios.png
288 ms
economista.jpg
320 ms
page0001_i1.jpg
387 ms
Ubuntu-Regular-webfont.woff
361 ms
cb=gapi.loaded_0
8 ms
61 ms
xd_arbiter.php
155 ms
xd_arbiter.php
423 ms
tracker.php
1362 ms
initiate_dialog.png
111 ms
menu_line.png
113 ms
message-box.gif
104 ms
logo25.png
105 ms
fontawesome-webfont.woff
104 ms
widgets.js
265 ms
icel_bkmenu.png
69 ms
top_b.png
69 ms
top.png
71 ms
mod_box.png
70 ms
main.png
69 ms
ui_readmore.png
72 ms
border.png
72 ms
list_line_black.png
174 ms
mod_line_bottom-b.png
178 ms
totop_scroller.png
178 ms
BebasNeue-webfont.woff
165 ms
analytics.js
131 ms
slideshow.js
119 ms
map.js
150 ms
cb=gapi.loaded_1
60 ms
cb=gapi.loaded_2
58 ms
subscribe_embed
258 ms
close.png
128 ms
blank.gif
128 ms
loadingAnimation.gif
127 ms
js
109 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
254 ms
collect
42 ms
postmessageRelay
141 ms
common.js
12 ms
map.js
11 ms
util.js
68 ms
marker.js
10 ms
overlay.js
63 ms
like.php
118 ms
onion.js
77 ms
www-subscribe-embed-vflTum1sJ.css
169 ms
www-subscribe-embed.js
173 ms
3193398744-postmessagerelay.js
84 ms
rpc:shindig_random.js
84 ms
like_box.php
328 ms
ViewportInfoService.GetViewportInfo
157 ms
stats.js
45 ms
controls.js
67 ms
TY3MhkXpWJ-.js
436 ms
LVx-xkvaJ0b.png
414 ms
infowindow.js
100 ms
cb=gapi.loaded_0
73 ms
m1.png
66 ms
transparent.png
59 ms
css
116 ms
www-hitchhiker-vflvB63an.png
94 ms
cb=gapi.loaded_0
102 ms
offline.png
142 ms
blue-dot.png
143 ms
google4.png
140 ms
mapcnt6.png
70 ms
sv5.png
70 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.es.html
64 ms
tmapctrl.png
52 ms
cb_scout5.png
53 ms
tmapctrl4.png
51 ms
imgs8.png
53 ms
google_white5.png
52 ms
hDvwL1_H7g-.css
160 ms
56WNbrUYLbL.css
165 ms
yZ--Yu0PDbV.css
170 ms
QD6_ejUFoCN.css
200 ms
xxJgcoj8mOR.css
222 ms
1kPfZUdGrka.js
198 ms
Yuj_Y8xNH2C.js
296 ms
Mpe38fuBVZ2.js
219 ms
n8qIhCw3vMx.js
220 ms
QKy94bWvcbp.js
268 ms
6q5od22S-uf.js
343 ms
7B-2ZS3Qt8r.js
315 ms
qcMicXoOToy.js
367 ms
57RpJa05x58.js
321 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
38 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
38 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
39 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
38 ms
vt
72 ms
vt
91 ms
info.json
130 ms
vt
71 ms
vt
77 ms
vt
77 ms
vt
77 ms
vt
94 ms
vt
122 ms
vt
124 ms
vt
116 ms
vt
121 ms
cb=gapi.loaded_3
11 ms
border_3.gif
14 ms
subscribe_embed
56 ms
spacer.gif
13 ms
border_3.gif
6 ms
bubbleSprite_3.png
9 ms
bubbleDropR_3.png
10 ms
bubbleDropB_3.png
10 ms
AuthenticationService.Authenticate
49 ms
www-subscribe-embed-card-vflqARhQ4.css
4 ms
www-subscribe-embed-card.js
18 ms
jot
203 ms
12313923_1135008206517019_7686278858521369802_n.png
395 ms
safe_image.php
258 ms
1010063_630113680339810_1730064801_n.jpg
421 ms
12803300_1058628140860040_5415986255833103491_n.jpg
461 ms
12523901_584692395017857_414812935748123769_n.jpg
503 ms
12743634_10207596351599776_1341041677413055700_n.jpg
504 ms
375801_137276939740939_237837568_n.jpg
504 ms
10407060_1207094515975054_3963509962979161081_n.jpg
504 ms
10366151_1207038722647300_1080633926612427226_n.jpg
502 ms
1256_1207038725980633_8123347180334139556_n.jpg
544 ms
10590593_1207038719313967_2871474560274633061_n.jpg
548 ms
1918490_1207038759313963_261756602127710690_n.jpg
546 ms
1979551_1206857405998765_218499538422037148_n.jpg
543 ms
10478688_1206850715999434_4499361708210555411_n.jpg
548 ms
1918539_1206850722666100_8657410025607348881_n.jpg
570 ms
7661_1206850719332767_8981591937148230979_n.jpg
583 ms
wL6VQj7Ab77.png
136 ms
s7jcwEQH7Sx.png
136 ms
QDwYpIaRyfG.png
135 ms
VXcANLwwL5J.js
43 ms
AmlxWlqMvlv.js
79 ms
icel.edu.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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
icel.edu.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
icel.edu.mx 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 Icel.edu.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 Icel.edu.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.
icel.edu.mx
Open Graph description is not detected on the main page of ICEL. 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: