2.3 sec in total
117 ms
1.3 sec
888 ms
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 117 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
femama.org.br performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value9.8 s
0/100
25%
Value11.0 s
6/100
10%
Value2,700 ms
3/100
30%
Value0
100/100
15%
Value22.0 s
1/100
10%
117 ms
40 ms
248 ms
146 ms
223 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 80% of them (78 requests) were addressed to the original Femama.org.br, 6% (6 requests) were made to C0.wp.com and 3% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (761 ms) relates to the external source D335luupugsy2.cloudfront.net.
Page size can be reduced by 272.2 kB (18%)
1.5 MB
1.3 MB
In fact, the total size of Femama.org.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. 80% 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 1.0 MB which makes up the majority of the site volume.
Potential reduce by 180.8 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 180.8 kB or 82% of the original size.
Potential reduce by 90.1 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. FEMAMA images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 47 (55%)
86
39
The browser has sent 86 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 45 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
femama.org.br
117 ms
40 ms
fbevents.js
248 ms
b58d48d1b7cc8198510101d84dff68fa.css
146 ms
sbi-styles.min.css
223 ms
bxslider.min.css
214 ms
jquery.min.js
230 ms
jquery-migrate.min.js
230 ms
jquery-1.12.4.min.js
300 ms
jquery.multi-select.min.js
225 ms
css
276 ms
17453b21-215b-4278-ba90-9d17a84edcba-loader.js
761 ms
rbtools.min.js
218 ms
rs6.min.js
273 ms
swiper.min.js
270 ms
bxslider.min.js
239 ms
jquery.isotope.min.js
270 ms
jquery.validate.min.js
272 ms
jquery.magnific-popup.min.js
272 ms
remodal.min.js
272 ms
infinite-scroll.pkgd.min.js
281 ms
jquery.curtail.min.js
282 ms
chosen.jquery.min.js
282 ms
chosen-config.min.js
283 ms
api.js
269 ms
scripts.min.js
283 ms
hello-frontend.min.js
292 ms
frontend-script.js
293 ms
widget-scripts.js
313 ms
pixel-cat.min.js
293 ms
video.js
314 ms
jquery.smartmenus.min.js
314 ms
imagesloaded.min.js
222 ms
api.js
282 ms
webpack-pro.runtime.min.js
314 ms
webpack.runtime.min.js
315 ms
frontend-modules.min.js
315 ms
hooks.min.js
234 ms
i18n.min.js
236 ms
frontend.min.js
381 ms
waypoints.min.js
315 ms
core.min.js
268 ms
frontend.min.js
379 ms
preloaded-elements-handlers.min.js
380 ms
animate-circle.min.js
382 ms
elementor.js
380 ms
lazyload.min.js
381 ms
gtm.js
171 ms
gtm.js
185 ms
sbi-sprite.png
158 ms
dummy.png
159 ms
bg-a-femama.png
92 ms
bg-depoimentos.png
90 ms
bg-noticias.png
90 ms
bg-parceiros.png
89 ms
font
48 ms
Rand-Bold.woff
46 ms
fa-regular-400.woff
183 ms
fa-solid-900.woff
182 ms
font
47 ms
Rand-Medium-1.woff
45 ms
font
275 ms
Rand-Regular.woff
45 ms
Rand-Black-1.woff
46 ms
eicons.woff
47 ms
fa-brands-400.woff
47 ms
recaptcha__en.js
171 ms
logotipo-femama-horizontal.png
59 ms
logotipo-femama-original.png
91 ms
61fa151836585-150x150.jpg
91 ms
61e4a92b11699-150x150.jpg
92 ms
61e4a4f66ee2b-150x150.jpeg
94 ms
6177fe9379e91-e1646251298548-150x150.jpg
93 ms
613ba51b3caa4-150x150.jpg
93 ms
606b8cc438a46-150x150.webp
91 ms
post-site-34-1-768x384.png
91 ms
post-site-33-768x384.png
94 ms
post-site-32-768x384.png
96 ms
post-site-31-768x384.png
95 ms
icone-respeito.png
95 ms
parceiro_Prancheta-1-copia-13.png
96 ms
parceiro_Prancheta-1-copia-2.png
97 ms
LOGO-CBI-768x438.png
98 ms
parceiro_Prancheta-1-copia-17.png
96 ms
Libbs_Logo-Institucional_Verde_SemAssinatura_RGB-768x403.png
97 ms
parceiro_Prancheta-1-copia-24.png
97 ms
parceiro_Prancheta-1-copia-11.png
98 ms
parceiro_Prancheta-1-copia-7.png
113 ms
umbro-logo-1-e1665087817107-768x498.png
113 ms
biomm.png
115 ms
parceiro_Prancheta-1-copia-22.png
115 ms
WhatsApp-Image-2023-10-10-at-09.58.32.jpeg
113 ms
WhatsApp-Image-2024-02-22-at-16.25.01.jpeg
116 ms
Dakiyama_Takeda_Red_DIGITAL-1-768x426.png
117 ms
GILEAD_ONCOLOGY_Horiz_RGB_012022-1-768x201.png
120 ms
logotipo-branca-femama.png
115 ms
bundle.js
248 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
Page has valid source maps
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: