5.5 sec in total
244 ms
4.8 sec
437 ms
Welcome to fopae.gov.co homepage info - get ready to check Fopae best content right away, or after learning these important things about fopae.gov.co
Visit fopae.gov.coWe analyzed Fopae.gov.co page load time and found that the first response time was 244 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fopae.gov.co performance score
244 ms
465 ms
257 ms
171 ms
171 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fopae.gov.co, 59% (74 requests) were made to Idiger.gov.co and 12% (15 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Idiger.gov.co.
Page size can be reduced by 4.4 MB (57%)
7.7 MB
3.3 MB
In fact, the total size of Fopae.gov.co main page is 7.7 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. 50% of websites need less resources to load. Images take 6.8 MB which makes up the majority of the site volume.
Potential reduce by 65.7 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 65.7 kB or 82% of the original size.
Potential reduce by 3.8 MB
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, Fopae needs image optimization as it can save up to 3.8 MB or 56% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 356.3 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 356.3 kB or 58% of the original size.
Potential reduce by 192.9 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. Fopae.gov.co needs all CSS files to be minified and compressed as it can save up to 192.9 kB or 81% of the original size.
Number of requests can be reduced by 45 (37%)
122
77
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fopae. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
fopae.gov.co
244 ms
www.idiger.gov.co
465 ms
main.css
257 ms
slider.css
171 ms
LogosFooter.css
171 ms
banners.css
163 ms
main.css
168 ms
main.css
166 ms
barebone.jsp
606 ms
jquery-min-1.8.2.js
420 ms
jquery.bxSlider.min.js
333 ms
main.css
342 ms
element.js
34 ms
main.js
329 ms
bg.jpg
173 ms
bg_header.jpg
172 ms
logo-alcadia.jpg
249 ms
logo-bogota.jpg
246 ms
titulo-header.gif
250 ms
icon-facebook-s.png
172 ms
icon-twitter-s.png
325 ms
icon-youtube-s.png
328 ms
icon-flickr-s.png
328 ms
bg-input-buscar.jpg
404 ms
btn-buscar.jpg
405 ms
key.png
407 ms
bg-menu-separador.png
483 ms
bg-caption-slider.png
485 ms
1-prueba.png
970 ms
2-prueba.jpg
956 ms
3-prueba.jpg
653 ms
9aa48094-3182-4819-a287-09956dbd14c8
872 ms
history.png
651 ms
article
3362 ms
rss.png
797 ms
1.png
1049 ms
3.png
1111 ms
2.png
1193 ms
4.png
1354 ms
6.png
1369 ms
5.png
1369 ms
7.png
1428 ms
8.png
1531 ms
9.png
1752 ms
10.png
1766 ms
logo_01.gif
1608 ms
logo_06.gif
1675 ms
logo_09.gif
1689 ms
logo_15.gif
1845 ms
logo_16.gif
1906 ms
translateelement.css
58 ms
main.js
68 ms
barra2015.js
391 ms
element_main.js
37 ms
BulbGrey.png
1748 ms
btn-slider.png
1768 ms
btn-slider-prev.png
1846 ms
btn-slider-next.png
1837 ms
vineta-menu-2.png
1853 ms
7818q41WXYZ.css
100 ms
analytics.js
8 ms
btn_bogota.gif
182 ms
popup1.gif
190 ms
popup2.gif
199 ms
popup3.gif
195 ms
ico_f.png
201 ms
ico_t.png
199 ms
ico_flk.png
271 ms
collect
17 ms
collect
55 ms
ga-audiences
67 ms
collect
20 ms
escudo.png
172 ms
menu1.jpg
181 ms
menu2.jpg
184 ms
menu3.png
185 ms
input_shadow.png
1501 ms
paging_first.png
1577 ms
paging_previous.png
1645 ms
paging_next.png
1659 ms
paging_last.png
1660 ms
open_window.png
1736 ms
widgets.js
15 ms
bg-banner.jpg
1791 ms
fon-footer.png
1872 ms
icontec1.png
1872 ms
1850 ms
1927 ms
footer_list.png
1891 ms
icon-facebook.jpg
1794 ms
icon-twitter.jpg
1733 ms
icon-youtube.jpg
1787 ms
btn-banner-prev.png
1783 ms
btn-banner-next.png
1723 ms
btn-slider-active.png
1048 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
15 ms
syndication
102 ms
300962461861953537
219 ms
245 ms
translate_24dp.png
25 ms
l
44 ms
cleardot.gif
16 ms
googlelogo_color_68x28dp.png
5 ms
te_ctrl3.gif
22 ms
loading.gif
21 ms
Cdw7d2IWAAAJ1vx.jpg
217 ms
CddBNDFWIAEsHqK.jpg
226 ms
CdM2u88WAAA6rIq.jpg
240 ms
CdMwTvzWIAQso5w.jpg
247 ms
Cc_PDlfW4AA3T1l.jpg
253 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
47 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
48 ms
te_bk.gif
15 ms
XNvnANK__normal.jpg
169 ms
43yrQQ5Z_normal.jpg
163 ms
4FiV0lTE_normal.jpg
195 ms
Cdw9QkHWAAAK7B9.jpg:small
196 ms
Cdt6pb7WIAEXVSk.jpg:small
199 ms
CdrhOR3W0AASaBV.jpg:small
197 ms
CdTfUQRXEAALJ3U.jpg:small
206 ms
CdNDybiWAAAU67R.jpg:small
207 ms
CdJD1PMW0AESYm6.jpg:small
209 ms
CcussjXXIAARbMK.jpg:small
216 ms
available_languages.jsp
171 ms
170 ms
jot
24 ms
fopae.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 Fopae.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 Fopae.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.
fopae.gov.co
Open Graph description is not detected on the main page of Fopae. 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: