5 sec in total
859 ms
3.9 sec
331 ms
Visit cace.org.ar now to see the best up-to-date CACE content for Argentina and also check out these interesting facts you probably never knew about cace.org.ar
Visit cace.org.arWe analyzed Cace.org.ar page load time and found that the first response time was 859 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
cace.org.ar performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value11.3 s
0/100
25%
Value9.7 s
11/100
10%
Value4,120 ms
1/100
30%
Value0.643
9/100
15%
Value12.7 s
13/100
10%
859 ms
167 ms
332 ms
330 ms
326 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 60% of them (59 requests) were addressed to the original Cace.org.ar, 11% (11 requests) were made to Apis.google.com and 7% (7 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Cace.org.ar.
Page size can be reduced by 356.0 kB (38%)
933.8 kB
577.8 kB
In fact, the total size of Cace.org.ar main page is 933.8 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. 65% of websites need less resources to load. Images take 479.0 kB which makes up the majority of the site volume.
Potential reduce by 91.4 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 91.4 kB or 86% of the original size.
Potential reduce by 27.6 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. CACE images are well optimized though.
Potential reduce by 174.8 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 174.8 kB or 63% of the original size.
Potential reduce by 62.2 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. Cace.org.ar needs all CSS files to be minified and compressed as it can save up to 62.2 kB or 86% of the original size.
Number of requests can be reduced by 56 (60%)
94
38
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CACE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.cace.org.ar
859 ms
style.css
167 ms
styles.css
332 ms
uamAdmin.css
330 ms
uamLoginForm.css
326 ms
l10n.js
326 ms
swfobject.js
336 ms
jquery.js
498 ms
jquery.tools.min.js
487 ms
functions.js
488 ms
jquery.cycle.js
491 ms
jquery-ui-1.8.11.custom.min.js
488 ms
jquery.scrollTo-min.js
517 ms
plusone.js
97 ms
in.js
35 ms
widgets.js
7 ms
jquery.form.js
660 ms
scripts.js
659 ms
cb=gapi.loaded_0
24 ms
whitepaper.png
513 ms
background.jpg
246 ms
logo.png
245 ms
banner-beneficios21.jpg
831 ms
bannerAsociate.jpg
571 ms
Banner-Home-D%C3%ADa-de-Internet.jpg
622 ms
iconoNovedades.png
309 ms
Nys-244x118.jpg
424 ms
imagenDefault.gif
427 ms
iconoComunicadosHome.png
510 ms
Logo-para-web-chiquito-jpg-234-60x50-113.jpg
568 ms
seo-express-grande.png
571 ms
ga.js
49 ms
all.js
91 ms
backgroundPage.jpg
1152 ms
btnFacebookHeader.png
757 ms
btnTwitterHeader.png
757 ms
btnYouTubeHeader.png
758 ms
btnLinkedinHeader.png
779 ms
btnGoogleHeader.png
889 ms
btnSearch.png
891 ms
navmenu.png
893 ms
backgroundBtnBanner.gif
942 ms
postDate.png
984 ms
avantgarde-medium-webfont.woff
1201 ms
avantgarde-bold-webfont.woff
1047 ms
secureAnonymousFramework
48 ms
__utm.gif
27 ms
sprite_connect_v14.png
61 ms
backgroundBtnComunicados.gif
970 ms
209 ms
xd_arbiter.php
115 ms
xd_arbiter.php
227 ms
btnPrevComunicados.gif
969 ms
btnNextComunicados.gif
1024 ms
arrowComunicadosList.gif
1086 ms
backgroundAgendaSidebar.jpg
1087 ms
iconoEventosSidebar.png
1125 ms
backgroundBtnAgenda.gif
1171 ms
iconoAgenda.png
1183 ms
backgroundHeadingLaborales.png
1231 ms
backgroundBtnLaborales.gif
1240 ms
backgroundFooter.gif
1240 ms
avantgarde-book-webfont.woff
1282 ms
btnFacebookFooter.png
1327 ms
analytics.js
94 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
96 ms
ping
144 ms
cb=gapi.loaded_1
45 ms
fastbutton
170 ms
fastbutton
221 ms
fastbutton
225 ms
fastbutton
233 ms
btnTwitterFooter.png
1256 ms
btnYouTubeFooter.png
1291 ms
collect
17 ms
postmessageRelay
91 ms
tweet_button.6a78875565a912489e9aef879c881358.es.html
27 ms
btnLinkedinFooter.png
1245 ms
like.php
135 ms
api.js
30 ms
core:rpc:shindig.random:shindig.sha1.js
122 ms
2536007149-postmessagerelay.js
116 ms
rs=AGLTcCNqicBbTRy2Ny4TeyhsrBuZucE7Kg
15 ms
cb=gapi.loaded_0
66 ms
cb=gapi.loaded_1
79 ms
btnGoogleFooter.png
1128 ms
like.php
102 ms
backgroundSliderBanner.png
1167 ms
like.php
134 ms
like.php
161 ms
like.php
206 ms
qbEHJxuVK5u.js
185 ms
LVx-xkvaJ0b.png
166 ms
ajax-loader.gif
1133 ms
btnSliderComunicados.gif
1097 ms
qbEHJxuVK5u.js
112 ms
qbEHJxuVK5u.js
156 ms
jot.html
3 ms
cace.org.ar 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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
cace.org.ar 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
cace.org.ar SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cace.org.ar 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 Cace.org.ar 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.
cace.org.ar
Open Graph description is not detected on the main page of CACE. 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: