5.1 sec in total
1.2 sec
3.5 sec
447 ms
Click here to check amazing Ufrr content for Brazil. Otherwise, check out these important facts you probably never knew about ufrr.br
Visit ufrr.brWe analyzed Ufrr.br page load time and found that the first response time was 1.2 sec and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
ufrr.br performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value10.9 s
0/100
25%
Value11.9 s
4/100
10%
Value17,160 ms
0/100
30%
Value0.413
24/100
15%
Value29.9 s
0/100
10%
1172 ms
341 ms
336 ms
323 ms
327 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 44% of them (47 requests) were addressed to the original Ufrr.br, 19% (20 requests) were made to Static.xx.fbcdn.net and 11% (12 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Ufrr.br.
Page size can be reduced by 769.7 kB (18%)
4.2 MB
3.4 MB
In fact, the total size of Ufrr.br main page is 4.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. 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 3.2 MB which makes up the majority of the site volume.
Potential reduce by 38.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. This page needs HTML code to be minified as it can gain 7.0 kB, which is 13% 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 38.5 kB or 73% of the original size.
Potential reduce by 45.9 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. Ufrr images are well optimized though.
Potential reduce by 258.7 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 258.7 kB or 58% of the original size.
Potential reduce by 426.7 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. Ufrr.br needs all CSS files to be minified and compressed as it can save up to 426.7 kB or 84% of the original size.
Number of requests can be reduced by 50 (51%)
99
49
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ufrr. 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 17 to 1 for CSS and as a result speed up the page load time.
ufrr.br
1172 ms
bootstrap.min.css
341 ms
template-branco.css
336 ms
icones-bmp-branco.css
323 ms
font-awesome.min.css
327 ms
k2.css
327 ms
banner-rotativo-home.css
329 ms
jquery.min.js
652 ms
jquery-noconflict.js
489 ms
jquery-migrate.min.js
490 ms
k2.js
496 ms
banner-rotativo-home.js
494 ms
agendadodia.css
495 ms
menu-usuario.css
673 ms
fontes.css
674 ms
bootstrap.min.js
689 ms
jquery.cookie.js
687 ms
template.js
688 ms
barra.js
861 ms
logo-brasao.png
175 ms
acessenossasredes.png
723 ms
sigaa_banner_final.png
1183 ms
lanawifi.JPG
838 ms
bandeiras.JPG
1167 ms
widgets.js
81 ms
flag-en.gif
165 ms
sm_facebook.png
371 ms
sm_instagram.png
338 ms
sm_twitter.png
604 ms
sm_youtube.png
602 ms
sm_flickr.png
764 ms
shadow-50.png
763 ms
bullets-branco-verde.gif
870 ms
btn_imagem_default.png
951 ms
btn_editorial_default.png
962 ms
btn_infografico_default.png
986 ms
phoca_thumb_l_coleta%20na%20estacao%20ecologica%20de%20maraca%203.jpg
1187 ms
phoca_thumb_l_buritizal.jpg
1429 ms
phoca_thumb_l_apresentacao%20cultural%20dia%20do%20secretariado.jpg
1278 ms
phoca_thumb_l_chuva%20no%20paricarana.jpg
1158 ms
phoca_thumb_l_cca%20-%20pesquisa%20com%20girrasol.jpg
1187 ms
phoca_thumb_l_coleta%20com%20raisa%20na%20estacao%20ecologica%20de%20maraca.jpg
1303 ms
phoca_thumb_l_coleta%20na%20confianca%20ii%20-%20canta%20-%20lorrane.jpg
1331 ms
acesso-a-informacao.png
1349 ms
brasil.png
1351 ms
opensans-400-webfont.woff
1398 ms
opensans-800-webfont.woff
1433 ms
fontawesome-webfont.woff
1462 ms
opensans-600-webfont.woff
1478 ms
rjAVBVCxcdo
138 ms
likebox.php
470 ms
iZv5eOP2rmw
115 ms
YfKjzIjGhkE
100 ms
ga.js
39 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
147 ms
www-embed-player-vflZsBgOl.css
69 ms
www-embed-player.js
99 ms
base.js
172 ms
opensans-bold.woff
467 ms
__utm.gif
28 ms
FbUd6dZS1Af.css
337 ms
dGJLq38YL-C.css
340 ms
f7m6HODnCDd.css
379 ms
i5_N_HL0uEJ.css
496 ms
Msuaq9yC6iC.css
504 ms
Vqr3k1iJZIS.js
494 ms
x5F9OMjKyLw.js
550 ms
ICDbTSzjQEg.js
477 ms
TTCre3391I0.js
477 ms
njO1TPvGzoR.js
566 ms
b_6HNn_J2BZ.js
548 ms
7cm7D75Y0Sf.js
576 ms
rFmE1g6Dkoz.js
627 ms
336JejShbZp.js
546 ms
syndication
228 ms
625784554759000064
337 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
95 ms
ad_status.js
172 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
140 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
141 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
31 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
98 ms
96-3KjVr_normal.jpg
164 ms
CcYdGQsW0AEEkrH.jpg:small
197 ms
CcJOl-uVAAAThGX.jpg:small
192 ms
CcJCxqIVAAAvHF-.jpg:small
198 ms
CcEoFZeWEAAuiG7.jpg:small
193 ms
CcD7btFWIAAIuyv.jpg:small
199 ms
12717385_856545481120561_102220055734010481_n.jpg
196 ms
10302022_857932314315211_6276778691622260453_n.jpg
259 ms
10409097_482315121956401_5822729247471680768_n.jpg
356 ms
1469916_1500524586918251_7238296886524338898_n.jpg
328 ms
10354686_10150004552801856_220367501106153455_n.jpg
303 ms
11666037_863478307061943_5473469257943865420_n.jpg
363 ms
10414605_536188173173767_7154768298440213567_n.jpg
494 ms
12715562_529921650512960_5889326088355207660_n.jpg
375 ms
12744700_858436900931419_1131582709717930449_n.jpg
497 ms
10400138_858436657598110_4473126017903636956_n.jpg
428 ms
10154214_859332134175229_6023041780064817130_n.jpg
457 ms
12321642_858436444264798_4994279707783885640_n.jpg
497 ms
wL6VQj7Ab77.png
91 ms
s7jcwEQH7Sx.png
94 ms
QDwYpIaRyfG.png
92 ms
a-ZN6WoEOje.png
91 ms
jot
26 ms
I6-MnjEovm5.js
39 ms
vlXaquuXMrr.js
40 ms
ufrr.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
ufrr.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
ufrr.br SEO score
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 Ufrr.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 Ufrr.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.
ufrr.br
Open Graph description is not detected on the main page of Ufrr. 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: