5.1 sec in total
925 ms
3.9 sec
259 ms
Click here to check amazing FEPI content for Brazil. Otherwise, check out these important facts you probably never knew about fepi.br
Visit fepi.brWe analyzed Fepi.br page load time and found that the first response time was 925 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
fepi.br performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value20.0 s
0/100
25%
Value27.2 s
0/100
10%
Value11,730 ms
0/100
30%
Value0
100/100
15%
Value26.3 s
0/100
10%
925 ms
169 ms
317 ms
335 ms
333 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 84% of them (47 requests) were addressed to the original Fepi.br, 4% (2 requests) were made to Staticxx.facebook.com and 4% (2 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Fepi.br.
Page size can be reduced by 822.9 kB (17%)
4.8 MB
4.0 MB
In fact, the total size of Fepi.br main page is 4.8 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. 55% of websites need less resources to load. Images take 4.1 MB which makes up the majority of the site volume.
Potential reduce by 19.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 3.5 kB, which is 15% 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 19.4 kB or 80% of the original size.
Potential reduce by 297.2 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. FEPI images are well optimized though.
Potential reduce by 288.3 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 288.3 kB or 67% of the original size.
Potential reduce by 218.0 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. Fepi.br needs all CSS files to be minified and compressed as it can save up to 218.0 kB or 82% of the original size.
Number of requests can be reduced by 26 (47%)
55
29
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FEPI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
fepi.br
925 ms
flexslider.css
169 ms
shadowbox.css
317 ms
style-front.css
335 ms
home.css
333 ms
jquery-1.5.2.min.js
509 ms
jquery.json.js
336 ms
jquery.base.js
336 ms
jquery.validate.min.js
472 ms
messages.js
497 ms
jquery.maskedinput-1.3.js
498 ms
jquery.flexslider-min.js
504 ms
jcarousellite_1.0.1.min.js
505 ms
jquery.jcarousel.min.js
628 ms
md5.js
662 ms
home.js
662 ms
shadowbox.js
673 ms
default.js
672 ms
logo.png
170 ms
selo.png
334 ms
redimensionar.jpg
1491 ms
redimensionar.jpg
1256 ms
redimensionar.jpg
1174 ms
redimensionar.jpg
1345 ms
redimensionar.jpg
1504 ms
redimensionar.jpg
1495 ms
redimensionar.jpg
1844 ms
redimensionar.jpg
1731 ms
redimensionar.jpg
1851 ms
redimensionar.jpg
1988 ms
redimensionar.jpg
1660 ms
redimensionar.jpg
1671 ms
redimensionar.jpg
1827 ms
redimensionar.jpg
1838 ms
redimensionar.jpg
1887 ms
redimensionar.jpg
1993 ms
redimensionar.jpg
2004 ms
redimensionar1.jpg
2009 ms
sdk.js
53 ms
SVtG3r07a3Q
103 ms
busca.png
1963 ms
mais.png
1989 ms
ico_nae.png
2097 ms
ico_nna.png
2104 ms
ico_nei.png
2117 ms
ico_not.png
2122 ms
ico_ouv.png
2130 ms
logo_savoir.png
2145 ms
redes.png
2262 ms
135 ms
xd_arbiter.php
34 ms
xd_arbiter.php
41 ms
www-embed-player-vflfNyN_r.css
60 ms
www-embed-player.js
80 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
41 ms
ad_status.js
45 ms
fepi.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.
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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
fepi.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
fepi.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fepi.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 Fepi.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.
fepi.br
Open Graph description is not detected on the main page of FEPI. 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: