16.6 sec in total
590 ms
13.6 sec
2.4 sec
Click here to check amazing CAPES content for Brazil. Otherwise, check out these important facts you probably never knew about capes.gov.br
Visit capes.gov.brWe analyzed Capes.gov.br page load time and found that the first response time was 590 ms and then it took 16 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
capes.gov.br performance score
name
value
score
weighting
Value11.9 s
0/100
10%
Value29.2 s
0/100
25%
Value24.4 s
0/100
10%
Value6,020 ms
0/100
30%
Value0.162
72/100
15%
Value48.0 s
0/100
10%
590 ms
487 ms
306 ms
298 ms
453 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Capes.gov.br, 70% (75 requests) were made to Www.gov.br and 9% (10 requests) were made to Youtube-nocookie.com. The less responsive or slowest element that took the longest time to load (9.5 sec) relates to the external source Www.gov.br.
Page size can be reduced by 1.8 MB (14%)
12.6 MB
10.8 MB
In fact, the total size of Capes.gov.br main page is 12.6 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 11.7 MB which makes up the majority of the site volume.
Potential reduce by 199.6 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. This page needs HTML code to be minified as it can gain 68.3 kB, which is 30% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 199.6 kB or 87% of the original size.
Potential reduce by 1.6 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, CAPES needs image optimization as it can save up to 1.6 MB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.6 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. This website has mostly compressed JavaScripts.
Potential reduce by 3.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. Capes.gov.br has all CSS files already compressed.
Number of requests can be reduced by 44 (49%)
89
45
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CAPES. 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 17 to 1 for CSS and as a result speed up the page load time.
capes.gov.br
590 ms
capes.gov.br
487 ms
pt-br
306 ms
reset-cachekey-e226e975ee723bf250b74fe89064d3d9.css
298 ms
base-cachekey-2a90c324377320eed0d532bbaeb1e170.css
453 ms
resourceplone.app.jquerytools.dateinput-cachekey-8570c1ba9db9f70c671ff63cfbfd6488.css
460 ms
resourceplone.formwidget.datetimestyles-cachekey-a5c51aaca2ab07d6373b2e467a319f19.css
461 ms
jquery.autocomplete-cachekey-1214e9ca0b2bb0b9ddad5ccbd8063b8a.css
464 ms
embedder-cachekey-dcd902e20e3bed3e880457b95eba6bc8.css
464 ms
resourcecollective.pollscsscollective.polls-cachekey-36fcd17efc0cd776a93df5eaa2173e68.css
466 ms
resourcepas.plugins.loginunicologinunico-cachekey-b6cbda8aeee75ea28b51443884947eb5.css
600 ms
swiper.min.css
33 ms
resourcelgpd.plugindsgov.min-cachekey-cda05370e1cc3178f0a9178b76ff3df3.css
912 ms
resourcegovbr.policycanais-cachekey-3e605998ce9d002dc6c94f4db226f6f9.css
603 ms
govbr.recom.9e3eea160cd9e43452ac.js
604 ms
resourceplone.app.jquery-cachekey-87ddd070f52d4c068134b3331e2462e0.js
758 ms
resourcegovbr.policyfolder_contents-cachekey-c916920b889ee95433b9eafbd2db6d7a.js
604 ms
resourcegovbr.policycookiebar_1_3_55-cachekey-9529928e6671810d926f5595e7c15bce.js
750 ms
resourcegovbr.policyapplication_cookiebar_1_3_55-cachekey-80000cbc9c7bd9d924b7ecbd1e6bad62.js
752 ms
collective.js.jqueryui.custom.min-cachekey-4c13849fd06e54f01e86eb337c263a6d.js
1357 ms
resourceplone.formwidget.recurrencejquery.tmpl-beta1-cachekey-52e47d0ac0e9bc79db509a21de69be6d.js
1061 ms
resourcecollective.js.bootstrapjsbootstrap.min-cachekey-466b6f00d3646e51ab963c524da5a81f.js
901 ms
resourcecollective.coverjsmain-cachekey-077a59dc1f86aa5f60f573126f8ca520.js
1054 ms
resourcebrasil.gov.tilesvendorjquery.jplayer.min-cachekey-47a62a0b1cbc6ae229da4a4c033aa79e.js
956 ms
resourcedropdown-menu-cachekey-fa132abc4c9168734de7b50deecff22b.js
1051 ms
swiper.min.js
33 ms
resourcelgpd.pluginchangeCookieImage-cachekey-8fe95c37c6685e43efe88497b526e3c1.js
1059 ms
resourcelgpd.pluginblock_cookies-cachekey-3e25e468896079cca6c61971a491165e.js
1063 ms
resourcegovbr.policyclipboard.min-cachekey-38d97299c31b58d95eafc0ff3aa712d1.js
1201 ms
themegovbr.institucionaljslistar_autoridades_eagenda-cachekey-5f350bce54884dedfc10e73fd95986ff.js
1205 ms
brasilgovagenda-720c34e.css
1210 ms
brasilgovagenda-720c34e.js
1473 ms
brasilgovportal-ee510e4.css
1213 ms
brasilgovportal-ee510e4.js
1352 ms
brasilgovtiles-7d5753d.css
1446 ms
brasilgovtiles-7d5753d.js
1516 ms
all.css
34 ms
sso-status-bar.js
1474 ms
govbrtheme-71a7413.css
1959 ms
lgpd_cookie_handling_1_3_87.js
1366 ms
vlibras-plugin.js
471 ms
govbrtheme-71a7413.js
1928 ms
vlibras-plugin.js
19 ms
govbr-logo-large.png
392 ms
f1190f93-f8c5-40e3-a9ba-e2a3e6e3742c.jpeg
1237 ms
4cad55db-5914-4313-9c49-20c902229833.png
2908 ms
6dccd0b2-08ff-4179-9c70-0e7901d7a25c.png
2966 ms
692cadc4-1b5f-4d67-9e77-3f092ac1ef2f.png
3196 ms
47cecd6a-748a-4c3a-ad51-5cd742528868.png
2879 ms
c2145181-2d98-479f-9cf5-280b502a8618.png
1004 ms
2056772e-7c8b-447b-8b55-7bf3631568e2.png
1138 ms
dc7e5078-9267-4959-ade0-dd72f4316f78.jpeg
1237 ms
07d32cb3-c770-4ad3-8e99-22f828caef90.jpeg
9500 ms
e0e7a799-d0ac-4a5c-8a01-6238fb3fadca.jpeg
2747 ms
b2126ee9-45bc-4dc6-929d-c314727a40c5.jpeg
2904 ms
5ffa2d2c-0041-4f87-894e-777b60b16e59.jpeg
3042 ms
ea5bc44e-8fbf-4ca8-8777-ec4029a68205.jpeg
3070 ms
8d5ec44c-54b2-4a18-8114-cef0de3c8130.jpeg
3073 ms
82f76d14-921e-400f-b8df-3be5136db065.jpeg
3129 ms
1a77d932-205a-4d9e-a25f-c0d64b252c85.png
3351 ms
36d38fd4-622d-4fb8-8b3a-f987da9e19ae.jpeg
3221 ms
80891c21-d779-4771-9b39-572dc0929808.jpeg
3234 ms
8d5dc95c-82a0-4725-ae16-a27ea1360f15.jpeg
3318 ms
975d0a8f-466e-4c29-b843-f9ff6acae704.jpeg
3358 ms
dd1c9a9e-f128-46cb-b507-18335b07c5ec.png
3386 ms
3ef3401a-73e0-47ee-824b-90e36d81b732.jpeg
3396 ms
e575a4ac-9b82-42e9-ab3c-d510ed1b334c.jpeg
3446 ms
487aafed-fbb3-46e6-b092-7ca1555a3a6f.jpeg
3514 ms
c2285ea8-5930-4b39-99db-9fa36d6d444c.jpeg
3512 ms
Banner_APO_Desktop.jpg
3851 ms
Banner_APO_Mobile.jpg
3730 ms
Oqzy2Q4TNNQ
370 ms
9JWyyC47AsY
414 ms
0e_lNIP3B1g
496 ms
rawline-400.woff
3558 ms
rawline-500.woff
3627 ms
rawline-300.woff
3651 ms
rawline-200.woff
3710 ms
rawline-100.woff
3778 ms
rawline-600.woff
3777 ms
rawline-700.woff
3831 ms
rawline-800.woff
3867 ms
fa-solid-900.ttf
346 ms
fa-regular-400.ttf
350 ms
fa-brands-400.ttf
256 ms
update.min.js
157 ms
rawline-900.woff
3579 ms
www-player.css
51 ms
www-embed-player.js
81 ms
base.js
153 ms
update.show.min.js
277 ms
jRYISRuM9q7e_xyYaLp_fsq3qnLjbNevd8JDa-bOkpI.js
176 ms
embed.js
123 ms
govbr.png
2900 ms
Create
558 ms
Create
560 ms
Create
565 ms
spinner.gif
2859 ms
f.png
509 ms
KFOmCnqEu92Fr1Mu4mxM.woff
302 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
303 ms
GenerateIT
265 ms
GenerateIT
263 ms
GenerateIT
92 ms
log_event
61 ms
log_event
29 ms
log_event
25 ms
capes.gov.br 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
Links do not have a discernible name
capes.gov.br 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
Missing source maps for large first-party JavaScript
capes.gov.br 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
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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Capes.gov.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Capes.gov.br 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.
capes.gov.br
Open Graph description is not detected on the main page of CAPES. 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: