3.6 sec in total
157 ms
3.1 sec
325 ms
Welcome to mintransporte.gov.co homepage info - get ready to check Min Transporte best content for Colombia right away, or after learning these important things about mintransporte.gov.co
Ministerio de transporte
Visit mintransporte.gov.coWe analyzed Mintransporte.gov.co page load time and found that the first response time was 157 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
mintransporte.gov.co performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value50.6 s
0/100
25%
Value23.6 s
0/100
10%
Value12,540 ms
0/100
30%
Value0.484
17/100
15%
Value46.2 s
0/100
10%
157 ms
906 ms
133 ms
109 ms
101 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 69% of them (88 requests) were addressed to the original Mintransporte.gov.co, 11% (14 requests) were made to Pbs.twimg.com and 6% (7 requests) were made to Translate.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Mintransporte.gov.co.
Page size can be reduced by 1.2 MB (28%)
4.2 MB
3.0 MB
In fact, the total size of Mintransporte.gov.co main page is 4.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 2.7 MB which makes up the majority of the site volume.
Potential reduce by 93.1 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 93.1 kB or 83% of the original size.
Potential reduce by 81.0 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. Min Transporte images are well optimized though.
Potential reduce by 338.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 338.0 kB or 57% of the original size.
Potential reduce by 664.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. Mintransporte.gov.co needs all CSS files to be minified and compressed as it can save up to 664.8 kB or 83% of the original size.
Number of requests can be reduced by 55 (45%)
123
68
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Min Transporte. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
mintransporte.gov.co
157 ms
mintransporte.gov.co
906 ms
bootstrap-all.min.css
133 ms
jquery-ui-1.10.4.custom.min.css
109 ms
prettyPhoto.min.css
101 ms
nx_default.min.css
104 ms
global.css
107 ms
aplicacion.css
153 ms
personal.css
195 ms
font-awesome.css
195 ms
materialize.css
233 ms
web_menuinferior215.css
198 ms
bloqueTabs2.css
225 ms
opcionesFormato.css
244 ms
jquery-1.11.1.min.js
321 ms
jquery.validate.min.js
287 ms
messages_es.js
296 ms
nx_default.min.js
318 ms
funcGenerales.min.js
339 ms
element.js
75 ms
jquery-ui-1.10.4.custom.min.js
400 ms
jsValidaciones.min.js
364 ms
jsValidaciones_es.js
366 ms
jquery.prettyPhoto.min.js
389 ms
jquery.megamenu.min.js
400 ms
jquery.photogallery-all.min.js
400 ms
jquery.translate.js
496 ms
global.js
496 ms
global.js
496 ms
jquery.enlaces.slider.js
514 ms
jquery.cookie.js
543 ms
opcionesFormato.js
544 ms
galeriaAudio.js
605 ms
logoMinisterio.png
370 ms
logoMinisterio02.png
370 ms
cargando.gif
370 ms
imgbloqSliderNoti352773.jpg
411 ms
imgbloqSliderNoti352993.jpg
412 ms
imgbloqSliderNoti352624.jpg
508 ms
imgbloqSliderNoti352721.jpg
515 ms
imgbloqSliderNoti35210.jpg
607 ms
pubInt4735.jpg
551 ms
pubInt4734.jpg
621 ms
pubInt4733.jpg
650 ms
pubInt4732.jpg
800 ms
th_img6403.jpg
643 ms
th_img6402.jpg
771 ms
th_img6401.jpg
772 ms
th_img6400.jpg
773 ms
th_img6399.jpg
841 ms
th_img6398.jpg
840 ms
th_img6397.jpg
915 ms
img1512.jpg
915 ms
img1513.jpg
914 ms
translateelement.css
54 ms
main.js
73 ms
img1515.jpg
938 ms
img1517.jpg
901 ms
img6451.jpg
964 ms
img6422.png
959 ms
img6446.png
961 ms
img6452.jpg
931 ms
fontawesome-webfont.woff
1047 ms
element_main.js
41 ms
hqdefault.jpg
60 ms
fontawesome-webfont.woff
923 ms
img6435.png
992 ms
img6436.png
990 ms
ga.js
166 ms
analytics.js
72 ms
img6437.png
948 ms
img6438.png
946 ms
img6439.png
1008 ms
collect
80 ms
widgets.js
134 ms
img6440.png
888 ms
img6442.png
897 ms
img6443.png
927 ms
__utm.gif
18 ms
img6445.png
888 ms
nexura.gif
922 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
30 ms
vinnetaLista.png
846 ms
arrowSlider_left.png
847 ms
syndication
103 ms
348105209383370753
105 ms
arrowSlider_right.png
843 ms
iconosPeticion.png
793 ms
fondoFormato.png
821 ms
fondoFormatoT2.png
827 ms
fondoFormatoT.png
812 ms
iconosfoot.png
955 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
32 ms
translate_24dp.png
162 ms
l
98 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
97 ms
googlelogo_color_42x16dp.png
166 ms
BcB0P1u3_normal.png
90 ms
u16015Dm_normal.png
99 ms
2IrTUHkn_normal.jpg
102 ms
6v1MFdeB_normal.png
104 ms
CcYlcrCWIAA5GHZ.jpg:small
115 ms
CcYjDuXWIAAifaF.jpg:small
107 ms
CcYhgu8WwAA0CjX.jpg:small
112 ms
CcWFynEWEAAUQRi.jpg:small
108 ms
CcVS50UWoAIOUlv.jpg:small
114 ms
CcPca0jWwAAhLwD.jpg:small
111 ms
CcPT7EpW0AAgcoi.jpg:small
118 ms
CcPMQCeWoAA5U4-.jpg:small
117 ms
CcPNAEOWwAQFZsH.jpg:small
118 ms
CcPIld4WEAEi8tN.jpg:small
117 ms
logoGobierno.png
719 ms
vinnetasMenuGel.png
750 ms
cleardot.gif
74 ms
te_ctrl3.gif
30 ms
loading.gif
58 ms
googlelogo_color_68x28dp.png
62 ms
vinnetaMenu.png
760 ms
bullet.png
747 ms
next.png
778 ms
te_bk.gif
31 ms
jot
36 ms
prev.png
721 ms
ui-bg_flat_75_ffffff_40x100.png
727 ms
ui-icons_222222_256x240.png
762 ms
pubDefault.jpg
757 ms
jot
30 ms
mintransporte.gov.co accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
Buttons do not have an accessible name
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
Some elements have a [tabindex] value greater than 0
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.
mintransporte.gov.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
mintransporte.gov.co SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mintransporte.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 Mintransporte.gov.co main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
mintransporte.gov.co
Open Graph description is not detected on the main page of Min Transporte. 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: