17.9 sec in total
1.7 sec
13.3 sec
3 sec
Welcome to fapeal.br homepage info - get ready to check FAPEAL best content for Brazil right away, or after learning these important things about fapeal.br
Visit fapeal.brWe analyzed Fapeal.br page load time and found that the first response time was 1.7 sec and then it took 16.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fapeal.br performance score
name
value
score
weighting
Value10.5 s
0/100
10%
Value15.2 s
0/100
25%
Value16.4 s
0/100
10%
Value1,600 ms
12/100
30%
Value0.019
100/100
15%
Value34.7 s
0/100
10%
1687 ms
7642 ms
114 ms
223 ms
22 ms
Our browser made a total of 156 requests to load all elements on the main page. We found that 64% of them (100 requests) were addressed to the original Fapeal.br, 6% (10 requests) were made to Api.handtalk.me and 5% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (7.6 sec) belongs to the original domain Fapeal.br.
Page size can be reduced by 1.3 MB (32%)
4.1 MB
2.8 MB
In fact, the total size of Fapeal.br main page is 4.1 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. 75% 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 2.8 MB which makes up the majority of the site volume.
Potential reduce by 67.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. 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 67.5 kB or 81% of the original size.
Potential reduce by 356.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. Obviously, FAPEAL needs image optimization as it can save up to 356.9 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 524.1 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 524.1 kB or 67% of the original size.
Potential reduce by 350.4 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. Fapeal.br needs all CSS files to be minified and compressed as it can save up to 350.4 kB or 84% of the original size.
Number of requests can be reduced by 87 (61%)
142
55
The browser has sent 142 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FAPEAL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
fapeal.br
1687 ms
www.fapeal.br
7642 ms
wp-emoji-release.min.js
114 ms
get-json-api.css
223 ms
jquery-ui.css
22 ms
form.min.css
220 ms
easingslider.min.css
221 ms
sc_our_team.css
230 ms
style.css
227 ms
sow-button-flat-263b90322f2f.css
233 ms
sow-button-atom-9a01ce061a8a.css
326 ms
style.css
328 ms
tabsy.css
330 ms
font-awesome.min.css
339 ms
style.css
460 ms
responsive.css
341 ms
font-awesome.min.css
436 ms
upw-theme-standard.min.css
437 ms
default.min.css
438 ms
rtbs_style.min.css
447 ms
www.fapeal.br
571 ms
icomoon.css
544 ms
bootstrap_frontend.min.css
557 ms
jsn-gui-frontend.css
566 ms
front_end.css
567 ms
front_end_responsive.css
570 ms
ytprefs.min.css
650 ms
wpgmza_style.css
666 ms
wpcufpn_front.css
668 ms
css
65 ms
jquery.js
780 ms
jquery-migrate.min.js
671 ms
jquery.cycle2.min.js
677 ms
jquery.cycle2.autoheight.min.js
756 ms
core.min.js
773 ms
datepicker.min.js
779 ms
underscore.min.js
782 ms
form.min.js
788 ms
jquery.easingslider.min.js
864 ms
in.js
10 ms
api.js
21 ms
jquery.fancybox-1.3.4.css
872 ms
jquery.circliful.css
788 ms
galleries-shortcodes.css
683 ms
box-shortcodes.css
687 ms
9d0dca9167a9957795d438898eebc060.css
691 ms
hc.js
759 ms
carousel.js
774 ms
sc_our_team.js
776 ms
jquery.flexslider.min.js
685 ms
rtbs.min.js
689 ms
ytprefs.min.js
693 ms
jquery.tabsy.js
753 ms
wptabsy.js
774 ms
scripts.js
680 ms
comment-reply.min.js
682 ms
bootstrap_frontend.min.js
691 ms
scrollReveal.js
687 ms
stellar.js
737 ms
fitvids.min.js
679 ms
jsn-fonticomoon.css
659 ms
jquery.fancybox-1.3.4.js
779 ms
jquery.lazyload.js
780 ms
jquery.circliful.min.js
778 ms
swiper.js
780 ms
galleries-shortcodes.js
700 ms
other-shortcodes.js
685 ms
4027fddec566f3861936ed1fb49d8b67.js
683 ms
iframe_api
80 ms
analytics.js
76 ms
home-sigfap.png
589 ms
opacity-10.png
309 ms
logomarca-fapeal25anos.png
1361 ms
s-right-s1.png
310 ms
Cartaz-Ciclo-Delmiro-160x160.jpg
313 ms
neno_canuto_20160309_1439611182-160x160.jpg
313 ms
foto-TRCILA-CABRAL-5-160x160.jpg
314 ms
Cartaz-Ciclo-Delmiro-600x300.jpg
577 ms
neno_canuto_20160309_1439611182-600x300.jpg
577 ms
resultado2-600x300.png
710 ms
fapealcomelas-01-600x300.png
715 ms
BANERS.SITE_-600x300.png
749 ms
home-dataPagamento.png
710 ms
home-prestacao.png
707 ms
home-agenda.png
792 ms
home-bdtd.png
795 ms
loading.gif
798 ms
parceiro-rnp1.jpg
813 ms
parceiro-capes.jpg
856 ms
parceiro-cnpq.jpg
902 ms
parceiro-finep.jpg
904 ms
parceiro-confap.jpg
909 ms
parceiro-ms.png
921 ms
banner-sic_EXTERNO.jpg
966 ms
banner-sic_PORTAL_ACESSO_INFORMACAO.jpg
1006 ms
banner-sic_LEI_DE_ACESSO.jpg
1013 ms
1-160x160.jpg
1019 ms
home-pop.png
441 ms
nav-arrow-next.png
440 ms
nav-arrow-prev.png
440 ms
widgets.js
267 ms
IcoMoon.svg
983 ms
fontawesome-webfont.woff
1136 ms
fontawesome-webfont.woff
1187 ms
secureAnonymousFramework
62 ms
linkid.js
18 ms
www-widgetapi.js
33 ms
like.php
459 ms
handtalk_init.js
228 ms
platform.js
225 ms
titillium-semibold-webfont.svg
1162 ms
titillium-regular-webfont.svg
1036 ms
titillium-light-webfont.svg
1162 ms
default.png
1203 ms
collect
194 ms
recaptcha__en.js
325 ms
nav-icon-inactive.png
268 ms
collect
276 ms
handtalk_init.js
249 ms
share
201 ms
sprite_connect_v14.png
192 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
197 ms
cb=gapi.loaded_0
51 ms
cb=gapi.loaded_1
68 ms
fastbutton
125 ms
postmessageRelay
115 ms
qeKvIRsJabD.js
76 ms
LVx-xkvaJ0b.png
75 ms
cb=gapi.loaded_0
38 ms
cb=gapi.loaded_1
30 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
41 ms
ga-audiences
63 ms
handtalk.min.js
29 ms
3193398744-postmessagerelay.js
59 ms
rpc:shindig_random.js
57 ms
ga.js
9 ms
handtalk.min.css
67 ms
handtalk-no-ie.min.css
71 ms
aff32705be272c7cb2e72c3e8c1fd42c9cc939d8
132 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.pt.html
61 ms
cb=gapi.loaded_0
21 ms
handtalk.min.css
17 ms
handtalk-no-ie.min.css
16 ms
logoht_off.png
32 ms
txt_acessivel.png
26 ms
tela-sistema-incompativel-tradutor-sites.png
44 ms
features_bt_like_on.png
38 ms
features_bt_unlike_on.png
45 ms
features_bt_help_on.png
44 ms
logoht_on.png
51 ms
tela-sistema-incompativel-tradutor-sites.png
22 ms
jot
74 ms
titillium-regular-webfont.woff
167 ms
titillium-semibold-webfont.woff
133 ms
titillium-light-webfont.woff
111 ms
nav-icon-active.png
119 ms
fapeal.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
fapeal.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
fapeal.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 Fapeal.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 Fapeal.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.
fapeal.br
Open Graph description is not detected on the main page of FAPEAL. 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: