5.7 sec in total
56 ms
2.5 sec
3.1 sec
Visit femama.org.br now to see the best up-to-date FEMAMA content for Brazil and also check out these interesting facts you probably never knew about femama.org.br
Desde a fundação, a FEMAMA luta nacionalmente por mudanças em políticas públicas que garantam melhor acesso e qualidade no diagnóstico e no tratamento do câncer de mama para a população.
Visit femama.org.brWe analyzed Femama.org.br page load time and found that the first response time was 56 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
femama.org.br performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value8.6 s
1/100
25%
Value27.7 s
0/100
10%
Value45,770 ms
0/100
30%
Value0
100/100
15%
Value62.0 s
0/100
10%
56 ms
319 ms
156 ms
366 ms
299 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 64% of them (87 requests) were addressed to the original Femama.org.br, 13% (18 requests) were made to Fonts.gstatic.com and 6% (8 requests) were made to C0.wp.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source D335luupugsy2.cloudfront.net.
Page size can be reduced by 272.0 kB (27%)
1.0 MB
730.3 kB
In fact, the total size of Femama.org.br main page is 1.0 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. 85% 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 652.8 kB which makes up the majority of the site volume.
Potential reduce by 201.3 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 201.3 kB or 83% of the original size.
Potential reduce by 70.4 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, FEMAMA needs image optimization as it can save up to 70.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 279 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 0 B
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. Femama.org.br has all CSS files already compressed.
Number of requests can be reduced by 57 (54%)
106
49
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FEMAMA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 55 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
56 ms
fbevents.js
319 ms
57e66fa87a99f79148ec114077541625.css
156 ms
css
366 ms
bxslider.min.css
299 ms
jquery.min.js
376 ms
jquery-migrate.min.js
364 ms
jquery-1.12.4.min.js
441 ms
jquery.multi-select.min.js
339 ms
17453b21-215b-4278-ba90-9d17a84edcba-loader.js
1608 ms
rbtools.min.js
330 ms
rs6.min.js
430 ms
swiper.min.js
363 ms
bxslider.min.js
402 ms
jquery.isotope.min.js
363 ms
jquery.validate.min.js
459 ms
jquery.magnific-popup.min.js
456 ms
remodal.min.js
565 ms
infinite-scroll.pkgd.min.js
564 ms
jquery.curtail.min.js
564 ms
chosen.jquery.min.js
564 ms
chosen-config.min.js
565 ms
api.js
563 ms
scripts.min.js
569 ms
hello-frontend.min.js
565 ms
pixel-cat.min.js
565 ms
video.js
565 ms
bdt-uikit.min.js
595 ms
webpack.runtime.min.js
566 ms
frontend-modules.min.js
568 ms
waypoints.min.js
567 ms
core.min.js
449 ms
frontend.min.js
593 ms
ep-search.min.js
593 ms
jquery.smartmenus.min.js
592 ms
ep-static-carousel.min.js
591 ms
imagesloaded.min.js
451 ms
api.js
575 ms
helper.min.js
591 ms
webpack-pro.runtime.min.js
893 ms
regenerator-runtime.min.js
556 ms
wp-polyfill.min.js
449 ms
hooks.min.js
556 ms
i18n.min.js
554 ms
frontend.min.js
877 ms
elements-handlers.min.js
893 ms
lazyload.min.js
892 ms
wp-emoji-release.min.js
631 ms
gtm.js
1162 ms
gtm.js
1303 ms
dummy.png
446 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
1009 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
1020 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
1016 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
1016 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
1011 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
1014 ms
Rand-Bold.woff
516 ms
fa-regular-400.woff
517 ms
fa-solid-900.woff
945 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
1014 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
1018 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
1021 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
1019 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
1018 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
1020 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
1137 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
1016 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
1136 ms
Rand-Medium-1.woff
508 ms
bg-depoimentos.png
1232 ms
bg-a-femama.png
709 ms
bg-noticias.png
694 ms
bg-parceiros.png
700 ms
Rand-Regular.woff
359 ms
Rand-Black-1.woff
357 ms
element-pack.ttf
356 ms
eicons.woff
487 ms
fa-brands-400.woff
484 ms
recaptcha__en.js
446 ms
logotipo-femama-horizontal.png
207 ms
logotipo-femama-original.png
84 ms
61fa151836585-150x150.jpg
206 ms
61e4a92b11699-150x150.jpg
207 ms
61e4a4f66ee2b-150x150.jpeg
210 ms
6177fe9379e91-e1646251298548-150x150.jpg
212 ms
613ba51b3caa4-150x150.jpg
211 ms
606b8cc438a46-150x150.webp
211 ms
Artigo-pik3ca-FEMAMA-768x480.jpg
212 ms
Desktop-1-e1664567040690-768x412.jpg
214 ms
FullSizeRender-768x576.jpeg
213 ms
foto-capa--768x432.png
214 ms
pexels-thirdman-7659464-768x512.jpg
213 ms
icone-respeito.png
218 ms
parceiro_Prancheta-1.png
214 ms
parceiro_Prancheta-1-copia-2.png
214 ms
parceiro_Prancheta-1-copia-3.png
215 ms
parceiro_Prancheta-1-copia-4.png
216 ms
parceiro_Prancheta-1-copia-5.png
214 ms
parceiro_Prancheta-1-copia-6.png
218 ms
parceiro_Prancheta-1-copia-7.png
216 ms
parceiro_Prancheta-1-copia-8.png
216 ms
parceiro_Prancheta-1-copia-9.png
217 ms
parceiro_Prancheta-1-copia-10.png
222 ms
parceiro_Prancheta-1-copia-11.png
217 ms
parceiro_Prancheta-1-copia-12.png
218 ms
parceiro_Prancheta-1-copia-13.png
219 ms
parceiro_Prancheta-1-copia-14.png
155 ms
parceiro_Prancheta-1-copia-15.png
157 ms
parceiro_Prancheta-1-copia-16.png
150 ms
parceiro_Prancheta-1-copia-17.png
151 ms
parceiro_Prancheta-1-copia-18.png
148 ms
parceiro_Prancheta-1-copia-19.png
150 ms
parceiro_Prancheta-1-copia-20.png
147 ms
parceiro_Prancheta-1-copia-21.png
143 ms
bundle.js
188 ms
parceiro_Prancheta-1-copia-22.png
161 ms
parceiro_Prancheta-1-copia-23.png
182 ms
parceiro_Prancheta-1-copia-24.png
181 ms
parceiro_Prancheta-1-copia.png
180 ms
logotipo-branca-femama.png
180 ms
anchor
59 ms
analytics.js
19 ms
875264636166495
107 ms
styles__ltr.css
16 ms
recaptcha__en.js
19 ms
collect
80 ms
webworker.js
44 ms
logo_48.png
30 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
41 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
42 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
43 ms
recaptcha__en.js
52 ms
rdstation-popup.min.js
42 ms
rd-js-integration.min.js
106 ms
femama.org.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
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
femama.org.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
femama.org.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
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 Femama.org.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 Femama.org.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.
femama.org.br
Open Graph data is detected on the main page of FEMAMA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: