6.3 sec in total
550 ms
5.5 sec
266 ms
Visit fleury.com.br now to see the best up-to-date Fleury content for United States and also check out these interesting facts you probably never knew about fleury.com.br
Faça seus exames no Fleury. Equipe altamente treinada com excelência na realização de diagnósticos. São diversas soluções em medicina e saúde. Confira.
Visit fleury.com.brWe analyzed Fleury.com.br page load time and found that the first response time was 550 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.
fleury.com.br performance score
name
value
score
weighting
Value1.9 s
86/100
10%
Value3.1 s
77/100
25%
Value4.0 s
80/100
10%
Value2,510 ms
4/100
30%
Value0.128
82/100
15%
Value9.5 s
30/100
10%
550 ms
544 ms
576 ms
279 ms
456 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 62% of them (42 requests) were addressed to the original Fleury.com.br, 18% (12 requests) were made to Static.xx.fbcdn.net and 12% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 1.5 MB (64%)
2.4 MB
872.0 kB
In fact, the total size of Fleury.com.br main page is 2.4 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. 70% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 38.1 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 38.1 kB or 74% of the original size.
Potential reduce by 102.7 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, Fleury needs image optimization as it can save up to 102.7 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.1 MB
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 1.1 MB or 76% of the original size.
Potential reduce by 307.2 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. Fleury.com.br needs all CSS files to be minified and compressed as it can save up to 307.2 kB or 87% of the original size.
Number of requests can be reduced by 34 (55%)
62
28
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fleury. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
fleury.com.br
550 ms
www.fleury.com.br
544 ms
default.aspx
576 ms
functions_init.js
279 ms
controls.css
456 ms
corev4.css
605 ms
bootstrap.css
459 ms
plugins.css
493 ms
main.css
694 ms
main.css
492 ms
WebResource.axd
492 ms
blank.js
491 ms
jquery.min.js
668 ms
plugins.js
502 ms
jquery.SPServices-2014.01.min.js
437 ms
main.js
441 ms
main.js
443 ms
jquery.carouFredSel-6.2.1-packed.js
512 ms
jquery.fancybox.js
593 ms
init.js
438 ms
ScriptResource.axd
445 ms
ScriptResource.axd
345 ms
gtm.js
196 ms
HONConduct242797_s1.gif
724 ms
fleury-logo.png
398 ms
fms-banner-examesatarde.jpg
472 ms
gf-banner_tratamento_preciso_contra_cancer_02.png
653 ms
fms-banner-vuemotion.png
445 ms
fms-banner-nova-jundiai.jpg
444 ms
centro-integrado-cardiologico-neurovascular-fleury%20(1).jpg
444 ms
atendimento-movel.jpg
467 ms
imagem-destaque-home-fleury-revista-fleury-contardo.png
982 ms
likebox.php
488 ms
spr-icones.png
423 ms
fundo-slider.jpg
752 ms
spr-cantos.png
419 ms
like.php
245 ms
kyrialsansproreg-webfont.woff
273 ms
kyrialsansprolight-webfont.woff
291 ms
kyrialsansprobold-webfont.woff
488 ms
analytics.js
103 ms
p_TUZUiNrjI.css
474 ms
CkaAj0ofVuQ.css
487 ms
mm0vjjrXdxr.js
1048 ms
Ta5YnQdNSFy.js
1241 ms
XXn49zk5GnD.js
1156 ms
OwNnuMlrnxQ.js
1155 ms
zH0IPw-UmpL.js
1497 ms
LVx-xkvaJ0b.png
1103 ms
collect
76 ms
12507669_1026458620746446_3737967417570642069_n.jpg
284 ms
12065947_985742104818098_8089011134277860618_n.png
350 ms
268916_10150709525630532_6808732_n.jpg
419 ms
12744752_970090016405089_2136516946294566097_n.jpg
485 ms
12661799_1071050599581968_7662519660022675374_n.jpg
464 ms
12376339_1276074689076244_5619742668599980488_n.jpg
462 ms
12108915_1069295883082611_1031692650324394932_n.jpg
461 ms
12088114_963665670338236_1173482270153738151_n.jpg
462 ms
wL6VQj7Ab77.png
167 ms
s7jcwEQH7Sx.png
168 ms
wBg80dBy2Ra.js
69 ms
WIQcBxwlOXr.js
134 ms
core.js
169 ms
sp.core.js
140 ms
ScriptResx.ashx
190 ms
cui.js
306 ms
sp.ui.dialog.js
168 ms
sp.runtime.js
141 ms
fleury.com.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
button, link, and menuitem elements do not have accessible names.
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
[id] attributes on active, focusable elements 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
Image elements do not have [alt] attributes
Links do not have a discernible name
fleury.com.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
Missing source maps for large first-party JavaScript
fleury.com.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fleury.com.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 Fleury.com.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.
fleury.com.br
Open Graph description is not detected on the main page of Fleury. 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: