10.3 sec in total
520 ms
9.4 sec
461 ms
Click here to check amazing MIO content for Colombia. Otherwise, check out these important facts you probably never knew about mio.com.co
Sitio Oficial del Masivo Integrado de Occidente MIO. Cali
Visit mio.com.coWe analyzed Mio.com.co page load time and found that the first response time was 520 ms and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
mio.com.co performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value10.4 s
0/100
25%
Value9.9 s
10/100
10%
Value4,860 ms
0/100
30%
Value0.005
100/100
15%
Value16.9 s
5/100
10%
520 ms
45 ms
19 ms
674 ms
421 ms
Our browser made a total of 152 requests to load all elements on the main page. We found that 55% of them (84 requests) were addressed to the original Mio.com.co, 7% (11 requests) were made to Maps.googleapis.com and 6% (9 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (7.1 sec) belongs to the original domain Mio.com.co.
Page size can be reduced by 990.2 kB (31%)
3.2 MB
2.2 MB
In fact, the total size of Mio.com.co main page is 3.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. 65% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 67.2 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 67.2 kB or 79% of the original size.
Potential reduce by 183.9 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. MIO images are well optimized though.
Potential reduce by 690.4 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 690.4 kB or 62% of the original size.
Potential reduce by 48.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. Mio.com.co needs all CSS files to be minified and compressed as it can save up to 48.6 kB or 63% of the original size.
Number of requests can be reduced by 74 (51%)
144
70
The browser has sent 144 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MIO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
520 ms
sdk.js
45 ms
analytics.js
19 ms
9006b7195da7eb0a3f5e3c071df4da1d.css
674 ms
421 ms
template.css.php
254 ms
430 ms
1095 ms
4265981d71a5a5b3ed62766d7ea9596a.js
3486 ms
1454 ms
jquery.min.js
39 ms
k2.js
650 ms
2136 ms
jquery.min.js
59 ms
1470 ms
ja.rightcol.js
1244 ms
css
35 ms
linkid.js
15 ms
collect
27 ms
57 ms
xd_arbiter.php
60 ms
xd_arbiter.php
94 ms
collect
78 ms
jquery.min.js
41 ms
js
94 ms
gsearch.js
1205 ms
jsapi
39 ms
ffpscript.js
1579 ms
gfdynamicfeedcontrol.css
40 ms
element.js
71 ms
32_867519228d1d5325856fc61d710ded0e_s.png
2042 ms
31_fa55c8bad0e242eb7986dc1135b50adb_s.png
1674 ms
30_1c0ae2205709722b62e843abc0471a55_s.png
1583 ms
29_fc34f61d23b74be53ee07d469bd32064_s.png
2332 ms
28_01f1a05053c6242fcfa23075e5b963c1_s.png
2347 ms
27_787ae9ec9023a82f5aa7e4c1a64f73cb_s.png
2614 ms
26_feb4274796d93ff716e9650163a77fb8_s.png
2886 ms
25_af2ef6a0e2c9c528b09655df79f3b312_s.png
3572 ms
24_233826a67be66a810b23a263230da62e_s.png
2879 ms
banercontacto-2_01.png
2982 ms
banercontacto-2_02.png
2824 ms
banercontacto-2_04.png
3034 ms
banercontacto-2_06.png
3094 ms
banercontacto-2_09.png
3101 ms
banercontacto-2_10.png
3200 ms
poweredgoogle.png
3351 ms
botones-webrutas.png
3308 ms
botones%20web-02.png
3314 ms
botones%20web-03.png
3617 ms
botones%20web-05.png
3526 ms
botones%20web-04l.png
3838 ms
botones%20web-07.png
3567 ms
botones%20web-06.png
3577 ms
gfdynamicfeedcontrol.css
31 ms
botones%20web-08.png
3601 ms
botones%20web-09.png
3473 ms
botones%20web-10.png
3930 ms
canalmetro-1.png
7148 ms
enlacePlanifica.png
3271 ms
system.css
2960 ms
enlacemapa.png
2868 ms
enlaceEstaciones.png
2859 ms
termconmio-curvas.png
3473 ms
manual.png
2817 ms
guia.png
2650 ms
logosryt.png
3238 ms
logosmio.png
3266 ms
logosmetro.png
2906 ms
logosalcaldia.png
2899 ms
header2.jpg
1116 ms
logo-t3.gif
1115 ms
grad1.gif
1201 ms
grad1-mask.png
1219 ms
opaque.png
1305 ms
arrow.png
1311 ms
circulo.png
1315 ms
t3_logo_light_sm.png
1407 ms
font-tool.gif
1420 ms
icon-youtube.png
1511 ms
wZLYhRRxZWGToTRP78bqJQ.woff
35 ms
fondo.png
1303 ms
loading.gif
1501 ms
transparent_bg.png
1507 ms
black_stripes.gif
1615 ms
bullet.gif
1632 ms
32_867519228d1d5325856fc61d710ded0e_t.jpg
1714 ms
31_fa55c8bad0e242eb7986dc1135b50adb_t.jpg
1716 ms
30_1c0ae2205709722b62e843abc0471a55_t.jpg
1727 ms
29_fc34f61d23b74be53ee07d469bd32064_t.jpg
1835 ms
28_01f1a05053c6242fcfa23075e5b963c1_t.jpg
3020 ms
27_787ae9ec9023a82f5aa7e4c1a64f73cb_t.jpg
1922 ms
26_feb4274796d93ff716e9650163a77fb8_t.jpg
1929 ms
25_af2ef6a0e2c9c528b09655df79f3b312_t.jpg
1943 ms
24_233826a67be66a810b23a263230da62e_t.jpg
2051 ms
banercontacto-2_11.png
2127 ms
fondo.png
713 ms
common.js
27 ms
util.js
70 ms
geocoder.js
70 ms
controls.js
69 ms
places_impl.js
69 ms
20 ms
default+en.css
24 ms
default+en.I.js
29 ms
widgets.js
34 ms
b-br.gif
2155 ms
prueba.html
740 ms
powered-by-google-on-white3.png
628 ms
autocomplete-icons.png
646 ms
gsearch.html
704 ms
b-bl.gif
1983 ms
translateelement.css
606 ms
main.js
632 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
34 ms
b-tr.gif
1533 ms
b-tl.gif
1608 ms
arrow2.png
1629 ms
syndication
201 ms
345263117820887041
325 ms
element_main.js
40 ms
saldo.css
214 ms
jquery-1.9.0.js
51 ms
inputmask.js
231 ms
maia.css
46 ms
default.css
54 ms
css
53 ms
js
52 ms
translate_24dp.png
90 ms
l
57 ms
cleardot.gif
52 ms
googlelogo_color_116x41dp.png
22 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
33 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
35 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
35 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
34 ms
te_ctrl3.gif
17 ms
googlelogo_color_68x28dp.png
10 ms
loading.gif
20 ms
te_bk.gif
11 ms
tusaldo-copia.png
1907 ms
tarjetastempla.png
3090 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
2 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
5 ms
W6gX_lpo_normal.jpg
127 ms
jot
25 ms
common.js
21 ms
util.js
38 ms
controls.js
16 ms
places_impl.js
20 ms
icon-hide.png
214 ms
Gfeeds
81 ms
garrow.gif
13 ms
mio.com.co 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
Form elements do not have associated labels
Links do not have a discernible name
mio.com.co 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
mio.com.co SEO score
ES
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mio.com.co can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it does not match the claimed English language. Our system also found out that Mio.com.co 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.
mio.com.co
Open Graph description is not detected on the main page of MIO. 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: