5.2 sec in total
775 ms
4.2 sec
237 ms
Click here to check amazing Face content for Brazil. Otherwise, check out these important facts you probably never knew about face.br
Visit face.brWe analyzed Face.br page load time and found that the first response time was 775 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
face.br performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value20.6 s
0/100
25%
Value15.2 s
1/100
10%
Value7,910 ms
0/100
30%
Value0.278
44/100
15%
Value23.4 s
1/100
10%
775 ms
829 ms
307 ms
394 ms
402 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Face.br, 67% (51 requests) were made to Uniuv.edu.br and 13% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Uniuv.edu.br.
Page size can be reduced by 168.4 kB (24%)
699.4 kB
531.1 kB
In fact, the total size of Face.br main page is 699.4 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. 35% of websites need less resources to load. Images take 472.8 kB which makes up the majority of the site volume.
Potential reduce by 26.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. 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 26.6 kB or 77% of the original size.
Potential reduce by 24.8 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. Face images are well optimized though.
Potential reduce by 94.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 94.8 kB or 58% of the original size.
Potential reduce by 22.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. Face.br needs all CSS files to be minified and compressed as it can save up to 22.1 kB or 78% of the original size.
Number of requests can be reduced by 31 (42%)
74
43
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Face. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
face.br
775 ms
www.uniuv.edu.br
829 ms
base.css
307 ms
central.css
394 ms
jquery.reject.css
402 ms
home.css
555 ms
nivo-slider.css
394 ms
jquery.min.js
931 ms
jquery.reject.min.js
460 ms
jquery.simplemodal.min.js
705 ms
geral.js
554 ms
jquery.nivo.slider.pack.js
721 ms
jquery.caroufredsel-4.5.2-packed.js
768 ms
all.js
270 ms
bg3.png
158 ms
bg1.png
178 ms
base_sprites.png
636 ms
bg-header-2015.jpg
683 ms
logo-uniuv-nova.png
359 ms
bg_menu1.jpg
179 ms
bg_menu3.png
315 ms
bg_menu5.jpg
340 ms
bg_menu2.jpg
336 ms
loading.gif
467 ms
banner_pipa.jpg
1181 ms
uniuv-2016-01.jpg
668 ms
home_sprites.png
1474 ms
redim_foto.php
709 ms
video000195.jpg
790 ms
videotrap_play.png
828 ms
videotrap_tit.png
843 ms
video000194p.jpg
865 ms
video000193p.jpg
989 ms
video000192p.jpg
990 ms
video000191p.jpg
1001 ms
video000190p.jpg
1032 ms
curso000007p.jpg
1106 ms
curso000004p.jpg
1157 ms
curso000016p.jpg
1162 ms
curso000009p.jpg
1183 ms
curso000018p.jpg
1263 ms
curso000010p.jpg
1323 ms
curso000012p.jpg
1325 ms
curso000002p.jpg
1340 ms
curso000003p.jpg
1335 ms
curso000022p.jpg
1421 ms
curso000008p.jpg
1484 ms
curso000014p.jpg
1481 ms
curso000001p.jpg
1489 ms
ga.js
46 ms
curso000019p.jpg
1470 ms
118 ms
__utm.gif
38 ms
xd_arbiter.php
220 ms
xd_arbiter.php
438 ms
curso000011p.jpg
1425 ms
like_box.php
136 ms
arrows.png
1459 ms
bullets.png
1468 ms
410ucuAGgaJ.css
286 ms
tSbl8xBI27R.css
354 ms
q68gy-v_YMF.js
491 ms
FJmpeSpHpjS.js
623 ms
0wM5s1Khldu.js
488 ms
1bNoFZUdlYZ.js
489 ms
1000028_966902853375557_5213993308639977796_n.jpg
317 ms
12803123_965992710133238_4764542754269671137_n.png
385 ms
10012513_943207122441866_6458877393627267702_n.jpg
454 ms
11846633_867761523312002_7984235897717976887_n.jpg
519 ms
1505129_501543763366929_9145065695133732549_n.jpg
593 ms
12360366_782296958548398_2619299791249138665_n.jpg
579 ms
1936257_513704745421149_3432121758607018737_n.jpg
705 ms
wL6VQj7Ab77.png
81 ms
s7jcwEQH7Sx.png
80 ms
I6-MnjEovm5.js
69 ms
pQrUxxo5oQp.js
73 ms
face.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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
face.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
face.br 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
PT
N/A
WINDOWS-1252
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Face.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Face.br main page’s claimed encoding is windows-1252. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
face.br
Open Graph description is not detected on the main page of Face. 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: