8 sec in total
2.9 sec
4.4 sec
658 ms
Click here to check amazing Brazil Foundation content for Brazil. Otherwise, check out these important facts you probably never knew about brazilfoundation.org
Visit brazilfoundation.orgWe analyzed Brazilfoundation.org page load time and found that the first response time was 2.9 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
brazilfoundation.org performance score
name
value
score
weighting
Value9.1 s
0/100
10%
Value23.5 s
0/100
25%
Value16.5 s
0/100
10%
Value2,590 ms
4/100
30%
Value0.157
74/100
15%
Value29.0 s
0/100
10%
2854 ms
27 ms
50 ms
50 ms
55 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 48% of them (42 requests) were addressed to the original Brazilfoundation.org, 14% (12 requests) were made to Apis.google.com and 7% (6 requests) were made to Scontent.cdninstagram.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Brazilfoundation.org.
Page size can be reduced by 787.2 kB (37%)
2.2 MB
1.4 MB
In fact, the total size of Brazilfoundation.org main page is 2.2 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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 65.3 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 12.9 kB, which is 16% 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 65.3 kB or 82% of the original size.
Potential reduce by 57.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. Brazil Foundation images are well optimized though.
Potential reduce by 318.1 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 318.1 kB or 66% of the original size.
Potential reduce by 346.1 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. Brazilfoundation.org needs all CSS files to be minified and compressed as it can save up to 346.1 kB or 89% of the original size.
Number of requests can be reduced by 44 (54%)
81
37
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Brazil Foundation. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
brazilfoundation.org
2854 ms
language-selector.css
27 ms
jquery.fancybox-1.3.4.min.css
50 ms
font-awesome.min.css
50 ms
jquery.js
55 ms
jquery-migrate.min.js
49 ms
ajax.min.js
79 ms
main.css
88 ms
ie.css
82 ms
jquery.js
112 ms
jquery.cycle.js
85 ms
init.js
110 ms
felipe.css
110 ms
css
139 ms
css
147 ms
entypo.css
130 ms
shadowbox.css
136 ms
chosen.min.css
133 ms
jquery-migrate-1.2.1.min.js
78 ms
shadowbox.js
136 ms
underscore-min.js
109 ms
backbone-min.js
135 ms
backbone.paginator.min.js
132 ms
chosen.jquery.min.js
139 ms
common.min.js
135 ms
lightbox_context.min.js
138 ms
jquery.easing-1.3.pack.js
138 ms
jquery.fancybox-1.3.4.pack.js
138 ms
nextgen_fancybox_init.min.js
138 ms
wp-embed.min.js
138 ms
sitepress.js
139 ms
wp-emoji-release.min.js
361 ms
analytics.js
607 ms
10654999_245077645832616_1187154853_n.jpg
820 ms
platform.js
706 ms
sdk.js
626 ms
widgets.js
670 ms
count.js
760 ms
sprites-s0351450472.png
402 ms
DSCN3030-1200x618.jpg
527 ms
IMG_3619-e1444850196939-1200x618.jpg
466 ms
41-C%C3%B3pia-e1441395170848-1200x618.jpg
532 ms
16-1200x618.jpg
465 ms
0065-e1441833560631-1200x618.jpg
710 ms
04-e1443565303405-1200x618.jpg
556 ms
map.png
529 ms
icons-s2798beac1e.png
556 ms
12562692_1139742039369455_436041250_o-e1457648487268-437x268.jpg
558 ms
12562692_1139742039369455_436041250_o-e1457648487268-65x65.jpg
600 ms
IMG_0114-e1457566529413-437x268.jpg
600 ms
MG_44842-e1457637334790-437x268.jpg
603 ms
outra_parada_edital2016_WEBSITE-e1446485126470-437x268.jpg
603 ms
10608093_1684543165146104_1006128123_n.jpg
707 ms
10643951_1696770767228295_259005682_n.jpg
818 ms
12826314_1685955981663617_1185654762_n.jpg
839 ms
12822326_994793093938560_606514456_n.jpg
861 ms
12822510_462883000566950_1566286445_n.jpg
860 ms
ejLRhBEorqjLDaF8s-xuTQ.ttf
553 ms
koFYE26bhT88HgRA8f4vbS3USBnSvpkopQaUR-2r7iU.ttf
624 ms
FZa_MODmDkR9DTu5jHSnSS3USBnSvpkopQaUR-2r7iU.ttf
748 ms
7M5kxD4eGxuhgFaIk95pBS3USBnSvpkopQaUR-2r7iU.ttf
747 ms
entypo.woff
597 ms
collect
128 ms
325 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
53 ms
xd_arbiter.php
263 ms
cb=gapi.loaded_0
198 ms
cb=gapi.loaded_1
181 ms
fastbutton
192 ms
fastbutton
191 ms
fastbutton
188 ms
fastbutton
186 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
119 ms
rs=AGLTcCOnajr3RJY7XpQMDAZWyUDsx4v9Qw
61 ms
postmessageRelay
127 ms
cb=gapi.loaded_0
76 ms
cb=gapi.loaded_1
69 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
33 ms
3193398744-postmessagerelay.js
77 ms
rpc:shindig_random.js
38 ms
cb=gapi.loaded_0
3 ms
share_button.php
62 ms
share_button.php
87 ms
share_button.php
86 ms
share_button.php
85 ms
jot.html
2 ms
qeKvIRsJabD.js
46 ms
LVx-xkvaJ0b.png
33 ms
brazilfoundation.org accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
brazilfoundation.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
brazilfoundation.org 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Brazilfoundation.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Brazilfoundation.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.
brazilfoundation.org
Open Graph description is not detected on the main page of Brazil Foundation. 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: