8.1 sec in total
589 ms
6.3 sec
1.2 sec
Click here to check amazing FAVI content for Brazil. Otherwise, check out these important facts you probably never knew about favi.br
Conheça a FAVI - Associação Vitoriana de Ensino Superior | IESFAVI | Ensino Superior. A FAVI (IESFAVI) possui diversos cursos de graduação e tecnológicos autorizados e reconhecidos pelo MEC que são of...
Visit favi.brWe analyzed Favi.br page load time and found that the first response time was 589 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
favi.br performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value14.4 s
0/100
25%
Value10.3 s
8/100
10%
Value3,040 ms
2/100
30%
Value0.51
15/100
15%
Value12.9 s
13/100
10%
589 ms
630 ms
312 ms
566 ms
588 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 33% of them (18 requests) were addressed to the original Favi.br, 22% (12 requests) were made to Api.unip.br and 13% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Api.unip.br.
Page size can be reduced by 49.2 kB (7%)
749.8 kB
700.6 kB
In fact, the total size of Favi.br main page is 749.8 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. 60% of websites need less resources to load. Images take 569.2 kB which makes up the majority of the site volume.
Potential reduce by 21.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 21.6 kB or 75% of the original size.
Potential reduce by 27 B
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. FAVI images are well optimized though.
Potential reduce by 10.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 10.5 kB or 11% of the original size.
Potential reduce by 17.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. Favi.br needs all CSS files to be minified and compressed as it can save up to 17.1 kB or 28% of the original size.
Number of requests can be reduced by 22 (52%)
42
20
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FAVI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
favi.br
589 ms
favi.br
630 ms
bootstrap.min.css
312 ms
estilo.min.css
566 ms
navbar.min.css
588 ms
cookieconsent.min.css
617 ms
fontawesome5.min.css
871 ms
css
69 ms
loader.css
886 ms
jquery.min.js
1023 ms
cookieconsent.min.js
705 ms
estilos_customizados.css
900 ms
centralBanner.js
929 ms
jquery-3.2.1.min.js
87 ms
bootstrap.min.js
703 ms
main.js
712 ms
central-sistemas.js
949 ms
mascara.min.js
994 ms
toastr.min.js
1149 ms
gtm.js
171 ms
logo.png
244 ms
logo_menu.png
254 ms
logo_rodape.png
239 ms
mapa.png
1453 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
1445 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
1522 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
1521 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
1521 ms
S6uyw4BMUTPHjx4wWw.ttf
1514 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
1533 ms
S6u9w4BMUTPHh50XSwiPHA.ttf
1509 ms
fa-solid-900.woff
1432 ms
fa-regular-400.woff
1430 ms
js
1186 ms
analytics.js
1494 ms
dbf1c384-bcff-4200-b380-1b228a8bbf5a.js
1568 ms
fa-brands-400.woff
1570 ms
conversion_async.js
1474 ms
2a78e72b-7017-467f-ac90-d4525a89eb88.png
1374 ms
3fc253be-8125-43fc-b6e5-1b3785bab48e.jpg
1207 ms
87622aa1-cff0-4f26-a893-caac7729dc0b.jpg
1349 ms
7547580a-ff6a-4ef8-937e-6c0ffd986140.jpg
1224 ms
427f7cd3-b103-403a-bb28-70e35b249e65.jpg
1222 ms
7c37f1ee-7a3f-4e6f-98b8-8592727a32d7.jpg
1235 ms
8f4c1cd2-aa9a-4142-9986-8633c26447d0.jpg
2057 ms
00201977-c636-48c7-8fe9-ad434fa26a50.jpg
1933 ms
b2d54e85-58d8-4c12-a8fd-d8f8d479f10e.jpg
2089 ms
c92a86fa-7182-4ef5-a006-6adc84b2c365.jpg
2137 ms
d4e7b147-23cd-47bf-a693-0b384c303199.jpg
2220 ms
d5c4a57c-ab68-4208-abf1-b74351186d94.jpg
2072 ms
125 ms
collect
51 ms
ilabspush.min.js
66 ms
32 ms
favi.br accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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 IDs are not unique
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
favi.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
Page has valid source maps
favi.br SEO score
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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Favi.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 Favi.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.
favi.br
Open Graph data is detected on the main page of FAVI. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: