13.5 sec in total
6.1 sec
7.2 sec
260 ms
Welcome to flacso.org homepage info - get ready to check Flacso best content for Colombia right away, or after learning these important things about flacso.org
Visit flacso.orgWe analyzed Flacso.org page load time and found that the first response time was 6.1 sec and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
flacso.org performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value6.2 s
11/100
25%
Value6.5 s
39/100
10%
Value380 ms
70/100
30%
Value0.136
80/100
15%
Value10.2 s
25/100
10%
6050 ms
74 ms
76 ms
91 ms
88 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 82% of them (87 requests) were addressed to the original Flacso.org, 9% (10 requests) were made to Static.xx.fbcdn.net and 6% (6 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (6.1 sec) belongs to the original domain Flacso.org.
Page size can be reduced by 346.5 kB (48%)
718.7 kB
372.2 kB
In fact, the total size of Flacso.org main page is 718.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 281.7 kB which makes up the majority of the site volume.
Potential reduce by 45.8 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 45.8 kB or 82% of the original size.
Potential reduce by 20.7 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. Flacso images are well optimized though.
Potential reduce by 177.7 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 177.7 kB or 70% of the original size.
Potential reduce by 102.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. Flacso.org needs all CSS files to be minified and compressed as it can save up to 102.3 kB or 81% of the original size.
Number of requests can be reduced by 77 (73%)
105
28
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flacso. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 40 to 1 for CSS and as a result speed up the page load time.
flacso.org
6050 ms
system.base.css
74 ms
system.menus.css
76 ms
system.messages.css
91 ms
system.theme.css
88 ms
comment.css
88 ms
date.css
120 ms
datepicker.1.7.css
118 ms
date_repeat_field.css
121 ms
field.css
134 ms
google_analytics_reports.css
133 ms
google_cse.css
138 ms
node.css
166 ms
om_maximenu.css
163 ms
poll.css
165 ms
search.css
178 ms
user.css
189 ms
views.css
187 ms
ckeditor.css
212 ms
ctools.css
205 ms
views_slideshow.css
206 ms
mobile_navigation.css
227 ms
views_slideshow_cycle.css
229 ms
responsive_menus_simple.css
230 ms
superfish.css
241 ms
at.settings.style.headings.css
249 ms
at.settings.style.image.css
255 ms
at.layout.css
272 ms
colors.css
275 ms
pixture_reloaded.css
289 ms
pixture_reloaded.settings.style.css
280 ms
pixture_reloaded.responsive.layout.css
288 ms
pixture_reloaded.fonts.css
300 ms
responsive.desktop.css
318 ms
sweaver_pixture_reloaded_1_live.css
320 ms
jquery.min.js
387 ms
jquery.once.js
271 ms
drupal.js
274 ms
google_analytics_reports.js
284 ms
google_cse.js
286 ms
om_maximenu.js
291 ms
es_vWpsne57CMBqSXMjYZCbXhBOH3PPeluxhfIwYYhqu7s.js
290 ms
views_slideshow.js
274 ms
custom_search.js
297 ms
tableheader.js
316 ms
jquery.cycle.all.min.js
290 ms
views_slideshow_cycle.js
284 ms
mobile_menu.js
302 ms
mobile_navigation.js
274 ms
responsive_menus_simple.js
288 ms
googleanalytics.js
291 ms
captcha.js
325 ms
jquery.hoverIntent.minified.js
316 ms
sftouchscreen.js
314 ms
supposition.js
299 ms
jquery.bgiframe.min.js
298 ms
superfish.js
291 ms
supersubs.js
284 ms
superfish.js
282 ms
bg-wall.png
286 ms
ga.js
6 ms
__utm.gif
14 ms
header-tile1.png
190 ms
header.png
55 ms
favicon.png
99 ms
flacso.png
73 ms
flacso_mexico_0.jpg
73 ms
posgrado.jpg
72 ms
revista.JPG
110 ms
flacsomexico1.jpg
121 ms
bullet-round.png
118 ms
feed.png
129 ms
logosisalc2.png
154 ms
yfwv6pf90o6pb6dcntwbkacslpdpdq-pre.jpg
156 ms
lib_tesis.jpg
165 ms
logo-siibe.png
184 ms
comentariosgral.png
226 ms
convocatorias2016_1.png
206 ms
proyectosyproduc2016_0.png
207 ms
tesis2016_0.png
219 ms
lib_nuevo_regionalismo_1.jpg
238 ms
f-icon.png
222 ms
in-icon.png
245 ms
t-icon.png
259 ms
shadow.png
269 ms
likebox.php
266 ms
410ucuAGgaJ.css
43 ms
tSbl8xBI27R.css
49 ms
q68gy-v_YMF.js
62 ms
FJmpeSpHpjS.js
89 ms
0wM5s1Khldu.js
61 ms
1bNoFZUdlYZ.js
87 ms
responsive.smartphone.portrait.css
136 ms
1233493_521447414598305_941720595_n.jpg
71 ms
11188238_811015375641506_1980506367354367143_n.jpg
26 ms
556920_350724838366428_71613630_n.jpg
28 ms
540134_613878428626871_44632436_n.jpg
26 ms
12733465_10207229096338734_1224164687361676796_n.jpg
28 ms
10394516_10152979760016884_6278070479530236576_n.jpg
27 ms
wL6VQj7Ab77.png
18 ms
s7jcwEQH7Sx.png
21 ms
responsive.smartphone.landscape.css
51 ms
I6-MnjEovm5.js
9 ms
pQrUxxo5oQp.js
4 ms
responsive.tablet.portrait.css
50 ms
responsive.tablet.landscape.css
49 ms
flacso.org accessibility score
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
<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
flacso.org 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
flacso.org SEO score
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 Flacso.org 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 Flacso.org 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.
flacso.org
Open Graph description is not detected on the main page of Flacso. 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: