3.3 sec in total
110 ms
2.8 sec
421 ms
Click here to check amazing FEDY content. Otherwise, check out these important facts you probably never knew about fedy.org.co
Esta es la pagina oficial de la Fundación Empresarial para el Desarrollo de Yumbo
Visit fedy.org.coWe analyzed Fedy.org.co page load time and found that the first response time was 110 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
fedy.org.co performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value19.7 s
0/100
25%
Value12.0 s
4/100
10%
Value560 ms
53/100
30%
Value0.227
55/100
15%
Value15.4 s
7/100
10%
110 ms
39 ms
36 ms
38 ms
52 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 76% of them (104 requests) were addressed to the original Fedy.org.co, 5% (7 requests) were made to Blogblog.com and 4% (6 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Fedy.org.co.
Page size can be reduced by 1.3 MB (31%)
4.3 MB
2.9 MB
In fact, the total size of Fedy.org.co main page is 4.3 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. 70% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 19.5 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 19.5 kB or 77% of the original size.
Potential reduce by 241.1 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. FEDY images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 65% of the original size.
Potential reduce by 44.4 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. Fedy.org.co needs all CSS files to be minified and compressed as it can save up to 44.4 kB or 73% of the original size.
Number of requests can be reduced by 71 (53%)
135
64
The browser has sent 135 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FEDY. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
fedy.org.co
110 ms
reset.css
39 ms
style.css
36 ms
template.css
38 ms
menu.css
52 ms
swfobject.js
75 ms
jquery.js
140 ms
x5engine.js
125 ms
x5cartengine.js
101 ms
l10n.js
87 ms
x5settings.js
101 ms
index.css
168 ms
style.css
123 ms
jquery-1.9.1.min.js
186 ms
scriptgates.js
165 ms
widgets.js
129 ms
jquery.js
180 ms
interface.js
181 ms
style.css
178 ms
bg.png
210 ms
index.html
89 ms
notas-recientes_25.html
150 ms
top.png
126 ms
index_h.png
83 ms
la-fedy.png
84 ms
ejes-de-trabajo.png
82 ms
noticias-1.png
84 ms
galeria-fotografica--.png
85 ms
contactenos.png
84 ms
separador_f22ioi1q_18834z2g.png
101 ms
logo_8boytpm8.png
101 ms
5_3f387r50.png
111 ms
5_t_3f387r50.png
105 ms
5_tl_3f387r50.png
106 ms
5_tr_3f387r50.png
127 ms
5_l_3f387r50.png
144 ms
5_r_3f387r50.png
169 ms
5_b_3f387r50.png
168 ms
5_bl_3f387r50.png
168 ms
5_br_3f387r50.png
168 ms
noticiasII.png
200 ms
noticias.png
217 ms
socialico-2_thumb.png
202 ms
socialico-1_thumb.png
202 ms
codigo.png
1346 ms
transparent.png
218 ms
banner.jpg
1350 ms
1.png
1346 ms
2.png
1350 ms
3.png
1349 ms
4.png
1352 ms
5.png
1355 ms
6.png
1351 ms
7.png
1347 ms
8.png
1351 ms
all.js
1330 ms
ga.js
40 ms
9.png
1286 ms
10.png
1284 ms
style.css
1281 ms
jquery.js
1290 ms
wowslider.js
1283 ms
script.js
1283 ms
15.png
1284 ms
11.png
1284 ms
__utm.gif
16 ms
12.png
1269 ms
16.png
1269 ms
13.png
1269 ms
14.png
1277 ms
5.png
1276 ms
5_t.png
1273 ms
5_tl.png
1258 ms
5_tr.png
1256 ms
3375562265-css_bundle_v2.css
58 ms
authorization.css
108 ms
jquery.js
35 ms
jquery-mousewheel.js
45 ms
common.js
72 ms
lang__es.js
55 ms
classic.js
68 ms
gadgets.js
62 ms
comments.js
78 ms
3731899860-widgets.js
96 ms
plusone.js
1211 ms
5_l.png
1240 ms
5_r.png
1215 ms
5_b.png
1216 ms
5_bl.png
1216 ms
5_br.png
1214 ms
dock-bg.gif
1184 ms
bottom.png
1182 ms
ejes-de-trabajo_h.png
1181 ms
contactenos_h.png
1168 ms
la-fedy_h.png
1167 ms
noticias-1_h.png
101 ms
proyectos_h.png
101 ms
galeria-fotografica--_h.png
99 ms
sub.png
98 ms
sub_h.png
98 ms
sub_f.png
97 ms
sub_f_h.png
96 ms
sub_l.png
96 ms
sub_l_h.png
94 ms
sub_m.png
94 ms
sub_m_h.png
94 ms
imLoad.gif
93 ms
imClose.png
93 ms
technorati.png
91 ms
imagen_8.jpg
320 ms
mulalolobo.jpg
321 ms
imagen_7.jpg
181 ms
imagen_4.jpg
212 ms
bullet.png
117 ms
imagen_8.jpg
142 ms
mulalolobo.jpg
189 ms
imagen_7.jpg
192 ms
imagen_4.jpg
260 ms
cb=gapi.loaded_0
54 ms
arrows.png
172 ms
121 ms
xd_arbiter.php
227 ms
xd_arbiter.php
435 ms
fedyyumbo.blogspot.com
113 ms
default
127 ms
fedyyumbo.blogspot.com
70 ms
print.css
53 ms
portada.png
36 ms
fastbutton
86 ms
tweet_button.html
53 ms
like.php
115 ms
rs=AGLTcCNM-48YL59d_yswpJ-6bM96iifCIg
12 ms
like.php
137 ms
cb=gapi.loaded_0
20 ms
cb=gapi.loaded_1
28 ms
qeKvIRsJabD.js
481 ms
LVx-xkvaJ0b.png
544 ms
fedy.org.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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
fedy.org.co best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
fedy.org.co SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Fedy.org.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 Fedy.org.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.
fedy.org.co
Open Graph description is not detected on the main page of FEDY. 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: