10.6 sec in total
501 ms
9.7 sec
373 ms
Visit idu.gov.co now to see the best up-to-date IDU content for Colombia and also check out these interesting facts you probably never knew about idu.gov.co
Conoce todo sobre la estructuración y desarrollo de proyectos de infraestructura vial y movilidad multimodal en la ciudad de Bogotá
Visit idu.gov.coWe analyzed Idu.gov.co page load time and found that the first response time was 501 ms and then it took 10.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
idu.gov.co performance score
501 ms
5966 ms
182 ms
550 ms
575 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 51% of them (68 requests) were addressed to the original Idu.gov.co, 9% (12 requests) were made to Apis.google.com and 9% (12 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (6 sec) belongs to the original domain Idu.gov.co.
Page size can be reduced by 2.3 MB (50%)
4.5 MB
2.3 MB
In fact, the total size of Idu.gov.co main page is 4.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. Only a small number of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.
Potential reduce by 194.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 194.9 kB or 86% of the original size.
Potential reduce by 622.3 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, IDU needs image optimization as it can save up to 622.3 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 762.0 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 762.0 kB or 70% of the original size.
Potential reduce by 696.1 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. Idu.gov.co needs all CSS files to be minified and compressed as it can save up to 696.1 kB or 85% of the original size.
Number of requests can be reduced by 59 (46%)
127
68
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IDU. 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 13 to 1 for CSS and as a result speed up the page load time.
idu.gov.co
501 ms
inicio
5966 ms
foundation.min.css
182 ms
aui.css
550 ms
main.css
575 ms
main.css
313 ms
main.css
315 ms
main.css
316 ms
main.css
315 ms
barebone.jsp
633 ms
main.css
589 ms
all.js
10 ms
widgets.js
8 ms
main.js
327 ms
jquery.js
726 ms
foundation.min.js
820 ms
interaction.js
726 ms
ga.js
360 ms
wmifnZMjDTk
409 ms
fondowebidu.jpg
689 ms
fondoTools.png
359 ms
Fondo-redes.png
300 ms
Iconos-Redes.png
300 ms
fontSizePlus.png
359 ms
fontSizeMenos.png
357 ms
llave.png
413 ms
c72f3229-a229-47aa-b7dc-f00e7ea38d70
480 ms
IdentidadAlcaldiaBogota.jpg
457 ms
Fondo-menuprincipal.png
455 ms
fondo-buscador.png
456 ms
search.png
492 ms
icono-home.png
557 ms
article
888 ms
article
890 ms
article
739 ms
article
887 ms
article
686 ms
article
888 ms
article
995 ms
fondo-itemsArrowSelectedGris.png
885 ms
spacer.png
1103 ms
_sprite.png
1101 ms
openid.gif
1101 ms
fondo-sombraServicios.png
1100 ms
Share.png
1100 ms
verMas.png
1157 ms
1909c6d1-d0db-4fed-a749-271b36af4a42
1244 ms
article
1234 ms
article
1235 ms
article
1233 ms
article
1234 ms
widgets.js
256 ms
article
1208 ms
article
1244 ms
article
1240 ms
plusone.js
377 ms
491 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
130 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
131 ms
fontawesome-alloy.woff
1006 ms
1023 ms
article
1044 ms
xd_arbiter.php
111 ms
__utm.gif
53 ms
article
1000 ms
article
1027 ms
article
1028 ms
like.php
334 ms
like.php
388 ms
like.php
345 ms
like.php
343 ms
like.php
332 ms
syndication
229 ms
593152227788890112
450 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
40 ms
www-embed-player-vflZsBgOl.css
223 ms
www-embed-player.js
322 ms
base.js
357 ms
article
974 ms
article
953 ms
95957335-5dcf-4976-ba7a-2438c3f7d7f1
1840 ms
Iconos-BotonesCarrusel.png
991 ms
cb=gapi.loaded_0
41 ms
cb=gapi.loaded_1
101 ms
fastbutton
217 ms
fastbutton
150 ms
fastbutton
94 ms
fastbutton
213 ms
fastbutton
213 ms
IdentidadIDUFooter.png
985 ms
rs=AGLTcCOh7WcI8ZhFTr5WjjogfXi0j1MeYw
38 ms
postmessageRelay
162 ms
cb=gapi.loaded_0
141 ms
cb=gapi.loaded_1
136 ms
qbEHJxuVK5u.js
303 ms
LVx-xkvaJ0b.png
259 ms
qbEHJxuVK5u.js
295 ms
qbEHJxuVK5u.js
350 ms
qbEHJxuVK5u.js
342 ms
api.js
260 ms
core:rpc:shindig.random:shindig.sha1.js
462 ms
2536007149-postmessagerelay.js
436 ms
jot.html
159 ms
qbEHJxuVK5u.js
349 ms
qbEHJxuVK5u.js
357 ms
1eJU4PjErWSV5LNTKFXcze5UHikZLg3viIH581vcHWA.js
329 ms
ad_status.js
334 ms
1f44d.png
318 ms
1f44d-1f3fb.png
316 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
54 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
324 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
129 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
346 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
372 ms
rz1Thlf5_normal.jpg
252 ms
UfyHKA4j_normal.png
256 ms
smiY38v3_normal.jpg
254 ms
QUTNSxb5_normal.jpg
258 ms
Ko6_Dbuw_normal.jpg
256 ms
OQ19RQHT_normal.jpg
256 ms
emxkG8nc_normal.png
255 ms
43yrQQ5Z_normal.jpg
257 ms
CcaknwVWAAAyFHA.jpg:small
258 ms
CcakVuTXIAIXebb.jpg:small
259 ms
CcIyi-QVIAEVS-X.jpg:small
261 ms
CcEOwnVUsAAukd-.jpg:small
259 ms
jot
37 ms
148 ms
130 ms
available_languages.jsp
108 ms
302 ms
297 ms
175 ms
110 ms
idu.gov.co SEO score
![]()
ES
![]()
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Idu.gov.co 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 Idu.gov.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.
idu.gov.co
Open Graph description is not detected on the main page of IDU. 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: