6.4 sec in total
1.2 sec
4.5 sec
638 ms
Visit funag.gov.br now to see the best up-to-date FUNAG content for Brazil and also check out these interesting facts you probably never knew about funag.gov.br
Visit funag.gov.brWe analyzed Funag.gov.br page load time and found that the first response time was 1.2 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
funag.gov.br performance score
name
value
score
weighting
Value11.4 s
0/100
10%
Value23.3 s
0/100
25%
Value20.4 s
0/100
10%
Value2,520 ms
4/100
30%
Value0.132
81/100
15%
Value30.8 s
0/100
10%
1211 ms
730 ms
587 ms
295 ms
444 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 48% of them (57 requests) were addressed to the original Funag.gov.br, 18% (22 requests) were made to Static.xx.fbcdn.net and 14% (17 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Funag.gov.br.
Page size can be reduced by 899.3 kB (20%)
4.5 MB
3.6 MB
In fact, the total size of Funag.gov.br main page is 4.5 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. 75% 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 3.8 MB which makes up the majority of the site volume.
Potential reduce by 43.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. This page needs HTML code to be minified as it can gain 11.4 kB, which is 20% 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 43.4 kB or 75% of the original size.
Potential reduce by 399.5 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. FUNAG images are well optimized though.
Potential reduce by 230.5 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 230.5 kB or 63% of the original size.
Potential reduce by 225.9 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. Funag.gov.br needs all CSS files to be minified and compressed as it can save up to 225.9 kB or 85% of the original size.
Number of requests can be reduced by 47 (40%)
118
71
The browser has sent 118 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FUNAG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
1211 ms
bootstrap.min.css
730 ms
template-azul.css
587 ms
icones-bmp-azul.css
295 ms
font-awesome.min.css
444 ms
k2.css
591 ms
banner-rotativo-home.css
433 ms
owl.carousel.css
440 ms
owl.theme.css
580 ms
jquery.min.js
1023 ms
jquery-noconflict.js
595 ms
jquery-migrate.min.js
748 ms
k2.js
750 ms
banner-rotativo-home.js
749 ms
jquery-1.8.1.min.js
1076 ms
owl.carousel.js
873 ms
fontes.css
878 ms
bootstrap.min.js
602 ms
jquery.cookie.js
600 ms
template.js
760 ms
barra.js
905 ms
flag-pt.jpg
171 ms
flag-en.gif
168 ms
flag-es.gif
167 ms
sm_facebook.png
169 ms
sm_twitter.png
170 ms
sm_youtube.png
168 ms
btn_editorial_default.png
299 ms
003hom.png
1098 ms
002hhh.png
1172 ms
001.png
595 ms
CAPA6.png
615 ms
bullets-branco-verde.gif
320 ms
feriahavana.png
595 ms
repertorio.png
926 ms
_DSC0055.jpg
1173 ms
varnhagen_mini.png
743 ms
banner_informativo4.png
744 ms
004.png
1097 ms
boletim-editorial-2015.png
1097 ms
boletim-editorial-2014.png
1220 ms
migracoes.png
1180 ms
kossovo.png
1182 ms
chdd_n26.png
1339 ms
40_anos_angola.jpg
1320 ms
cadernos_ipri_02.png
1321 ms
tabaco.png
1323 ms
1139-Capa_O_Recrudescimento_do_Nacionalismo_Catalao.png
1327 ms
chdd_ingles.png
1367 ms
ipri_ingles.png
1467 ms
loja_ingles.png
1466 ms
acesso-a-informacao.png
1469 ms
brasil.png
1475 ms
opensans-400-webfont.woff
1455 ms
opensans-800-webfont.woff
1483 ms
fontawesome-webfont.woff
1590 ms
opensans-700-webfont.woff
1579 ms
widgets.js
111 ms
opensans-bold.woff
437 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
138 ms
opensans-600-webfont.woff
1461 ms
likebox.php
368 ms
syndication
95 ms
565855649817698304
245 ms
roNeOY-tz5Y.css
201 ms
UHhaxo8Cs3k.css
248 ms
dbNRhrdsQao.css
288 ms
1ssvpqNRk1L.css
349 ms
kCqR6fITdsR.css
314 ms
_rx8naC75Dy.js
398 ms
x5F9OMjKyLw.js
423 ms
ICDbTSzjQEg.js
321 ms
TTCre3391I0.js
327 ms
njO1TPvGzoR.js
357 ms
b_6HNn_J2BZ.js
362 ms
7cm7D75Y0Sf.js
434 ms
rFmE1g6Dkoz.js
492 ms
336JejShbZp.js
387 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
43 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
97 ms
uOeQOLx9_normal.png
58 ms
JoZQkLuo_normal.png
57 ms
Cb2JZaTWIAAB9Ys.jpg:small
63 ms
CbV6DMOWwAATbpH.jpg:small
60 ms
Ca8_ufFXEAAoLkc.jpg:small
61 ms
CYmYQqXW8AAFPfB.png:small
70 ms
CYicGFuWsAAgRHK.png:small
68 ms
CW2m23sWUAE3OMW.png:small
75 ms
CW2mqsQWoAADp4Y.png:small
80 ms
CWSJP1ZW4AAAuyL.png:small
78 ms
CWL0UhCWUAQ0qDc.png:small
71 ms
CWLzyu0XAAA_JLU.png:small
73 ms
CVt5JJxW4AAvMDK.jpg:small
74 ms
CVpdFDUWoAEei_J.png:small
79 ms
CUwnu6YWEAATv4E.png:small
82 ms
CUf-J8XXIAEz_x6.png:small
79 ms
CUf8MmUWoAAo0ap.png:small
80 ms
jot
25 ms
11951268_855088131207076_6237385125039943464_n.png
250 ms
11898907_855087981207091_4708287643620681518_n.png
310 ms
12805883_1730256443873550_2338192500387071299_n.jpg
510 ms
12046822_902562476489988_3165610512062992944_n.jpg
399 ms
10590605_548007545343728_5005985213136346815_n.jpg
352 ms
1476189_1383608938553751_1118375533_n.jpg
351 ms
12645170_10201362072769459_3798288185749983593_n.jpg
359 ms
12734217_930949700287585_8269830818801646315_n.jpg
390 ms
1934795_928796717169550_5152199183222784132_n.png
424 ms
12814104_932665350116020_1491422633829049889_n.jpg
462 ms
12743968_926923970690158_6098114376889521633_n.png
437 ms
12743912_925958450786710_8307274379228964350_n.png
430 ms
12742552_925959837453238_1987203430444872637_n.png
496 ms
12729108_925959840786571_8936630178012274850_n.png
462 ms
wL6VQj7Ab77.png
78 ms
s7jcwEQH7Sx.png
76 ms
QDwYpIaRyfG.png
77 ms
WC6AgLuP72p.png
78 ms
K0srxReVLKP.png
76 ms
a-ZN6WoEOje.png
77 ms
I6-MnjEovm5.js
44 ms
vlXaquuXMrr.js
39 ms
funag.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
Form elements do not have associated labels
funag.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
funag.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Funag.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 Funag.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.
funag.gov.br
Open Graph description is not detected on the main page of FUNAG. 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: