14.5 sec in total
4.1 sec
10 sec
363 ms
Click here to check amazing FAPEMIG content for Brazil. Otherwise, check out these important facts you probably never knew about fapemig.br
Sítio eletrônico da Fundação de Amparo à Pesquisa do estado de Minas Gerais - FAPEMIG
Visit fapemig.brWe analyzed Fapemig.br page load time and found that the first response time was 4.1 sec and then it took 10.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fapemig.br performance score
name
value
score
weighting
Value6.0 s
3/100
10%
Value22.1 s
0/100
25%
Value10.4 s
8/100
10%
Value1,190 ms
21/100
30%
Value0.081
94/100
15%
Value18.3 s
3/100
10%
4082 ms
307 ms
22 ms
486 ms
326 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 73% of them (35 requests) were addressed to the original Fapemig.br, 8% (4 requests) were made to Google-analytics.com and 6% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Fapemig.br.
Page size can be reduced by 836.5 kB (55%)
1.5 MB
695.9 kB
In fact, the total size of Fapemig.br main page is 1.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. 35% of websites need less resources to load. Images take 621.7 kB which makes up the majority of the site volume.
Potential reduce by 34.9 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 5.5 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 34.9 kB or 83% of the original size.
Potential reduce by 158.3 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. Obviously, FAPEMIG needs image optimization as it can save up to 158.3 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 267.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 267.5 kB or 62% of the original size.
Potential reduce by 375.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. Fapemig.br needs all CSS files to be minified and compressed as it can save up to 375.7 kB or 86% of the original size.
Number of requests can be reduced by 25 (57%)
44
19
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FAPEMIG. 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 11 to 1 for CSS and as a result speed up the page load time.
www.fapemig.br
4082 ms
acessibilidade.js
307 ms
urchin.js
22 ms
style.css
486 ms
stylesheet.css
326 ms
tubepress.css
332 ms
app.css
333 ms
page-list.css
397 ms
uamAdmin.css
460 ms
uamLoginForm.css
500 ms
jquery.js
1014 ms
jquery-migrate.min.js
500 ms
tubepress.js
569 ms
swfobject.js
21 ms
jquery.tools.min.js
616 ms
functions.js
648 ms
jquery-1.4.2.min.js
986 ms
coin-slider-4-wp.css.php
1981 ms
coin-slider.min.js
741 ms
orbit-1.2.3.css
771 ms
jquery.orbit-1.2.3.min.js
810 ms
enviar_email.jpg
765 ms
banner_institucional_2015.gif
928 ms
mapa.jpg
1472 ms
science2.jpg
1262 ms
vaga.jpg
1325 ms
mosquitos.jpg
1195 ms
conselho-curador-23-02-20161.jpg
1235 ms
MFC+63-150x198.jpg
1366 ms
__utm.gif
10 ms
ga.js
11 ms
__utm.gif
11 ms
contraste.css
173 ms
gov.png
173 ms
bgs.png
405 ms
loading.gif
173 ms
8bllQvSorJM
111 ms
blog.png
158 ms
revista-fapemig-min.JPG
1727 ms
botoes.png
443 ms
capes-60-anos.jpg
360 ms
www-embed-player-vflZsBgOl.css
62 ms
www-embed-player.js
84 ms
base.js
156 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
41 ms
ad_status.js
40 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
84 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
92 ms
fapemig.br 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
[role]s are not contained by their required parent element
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
fapemig.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
Page has valid source maps
fapemig.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
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fapemig.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 Fapemig.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.
fapemig.br
Open Graph description is not detected on the main page of FAPEMIG. 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: