3.9 sec in total
246 ms
3.4 sec
219 ms
Welcome to fhf.fr homepage info - get ready to check FHF best content for France right away, or after learning these important things about fhf.fr
Site officiel de la Fédération Hospitalière de France (FHF) - créée en 1924, la FHF réunit plus de 1 000 établissements publics de santé (hôpitaux).
Visit fhf.frWe analyzed Fhf.fr page load time and found that the first response time was 246 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
fhf.fr performance score
name
value
score
weighting
Value6.0 s
3/100
10%
Value15.0 s
0/100
25%
Value7.7 s
24/100
10%
Value610 ms
49/100
30%
Value0
100/100
15%
Value11.9 s
17/100
10%
246 ms
954 ms
347 ms
242 ms
244 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 75% of them (77 requests) were addressed to the original Fhf.fr, 13% (13 requests) were made to Pbs.twimg.com and 4% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Fhf.fr.
Page size can be reduced by 748.9 kB (41%)
1.8 MB
1.1 MB
In fact, the total size of Fhf.fr main page is 1.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. 40% of websites need less resources to load. Images take 845.0 kB which makes up the majority of the site volume.
Potential reduce by 87.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. This page needs HTML code to be minified as it can gain 24.8 kB, which is 23% 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 87.5 kB or 80% of the original size.
Potential reduce by 47.0 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. FHF images are well optimized though.
Potential reduce by 391.0 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 391.0 kB or 67% of the original size.
Potential reduce by 223.5 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. Fhf.fr needs all CSS files to be minified and compressed as it can save up to 223.5 kB or 85% of the original size.
Number of requests can be reduced by 82 (82%)
100
18
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FHF. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
fhf.fr
246 ms
www.fhf.fr
954 ms
style.css
347 ms
style_refonte.css
242 ms
jquery.lightbox.css
244 ms
jquery.fancybox.css
240 ms
screen.css
242 ms
jqtransform.css
242 ms
eznovacookieconsent.css
320 ms
bloc-adherent.php
444 ms
addthis_widget.js
10 ms
jquery-1.6.2.min.js
557 ms
jquery.jqtransform.js
437 ms
easySlider1.7.js
437 ms
jquery.lightbox-0.5.js
472 ms
jquery.fancybox.pack.js
497 ms
fhf.js
575 ms
eznovacookieconsent.js
487 ms
logo.png
554 ms
Paris-Healthcare-Week_reference.jpg
711 ms
id_pub.png
573 ms
btn_actualite_on.png
682 ms
btn_annuaire_off.png
713 ms
btn_offre_emploi_off.png
713 ms
btn_appel_marche_off.png
713 ms
btn_enregion_off.png
714 ms
btn_forum_off.png
819 ms
btn_adherent_off.png
871 ms
icone_la_une.png
794 ms
Guide-Laicite-et-gestion-du-fait-religieux-dans-les-EPS_vignette_alune.jpg
880 ms
communique-presse_vignette_alune.jpg
880 ms
picto_actu.gif
874 ms
widgets.js
97 ms
fond_page.gif
599 ms
fond_header.gif
621 ms
border-pub.gif
597 ms
ombre-espace_adherents.png
597 ms
bg_menu_bleu.jpg
695 ms
separateur_ssmenu.png
697 ms
picto_adh.gif
698 ms
fond_content.gif
766 ms
agenda.gif
704 ms
visuel_agenda.png
738 ms
puce.png
757 ms
chiffre.png
758 ms
NewLogo_TRIO_PHW_large.png
840 ms
bg_right.gif
811 ms
btn_a-.gif
792 ms
btn_a+.gif
841 ms
analytics.js
22 ms
btn_imprime.gif
748 ms
btn_share.gif
731 ms
collect
12 ms
btn_rss.gif
870 ms
search.png
864 ms
lettre1.png
808 ms
lettre2.png
815 ms
300lo.json
48 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
133 ms
RA2014_vignette_pub.jpg
881 ms
sh.7c7179124ea24ac6ba46caac.html
43 ms
Couverture_vignette_pub.jpg
883 ms
750_vignette_pub.jpg
840 ms
568_vignette_pub.jpg
810 ms
logo_hopital-fr_block_link.png
811 ms
logo-mdr.fr_block_link.png
836 ms
Logo-SPH_large.png
1051 ms
mini_logo.png
1046 ms
syndication
104 ms
519058207335919616
233 ms
hope_logo.png
966 ms
IHF_logo.png
944 ms
picto_rss.gif
817 ms
recherche.png
833 ms
separateur.png
887 ms
btn_valider.png
987 ms
fond_footer.png
889 ms
fleche_gris.png
891 ms
sep_last_list.png
889 ms
bg_ident.png
872 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
30 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
95 ms
i5FYupv0_normal.jpg
127 ms
t0hhGKKK_normal.jpg
149 ms
pu7wdSbC_normal.jpg
182 ms
IIupAI9b_normal.jpg
215 ms
CcXi2thWEAA_DQb.jpg:small
262 ms
CcEgx-_WIAAxJ2D.jpg:small
255 ms
CcEautTW8AA3Lul.jpg:small
243 ms
CcDAM-cW0AAlilw.jpg:small
240 ms
Cb49MTOW4AAep8s.jpg:small
246 ms
Cbz5lyqWAAEnY_4.png:small
376 ms
CbkI2sBUAAEKxpX.png:small
315 ms
Cbe9ONdW4AAN1kw.png:small
325 ms
CbbV-gzWEAEBjQ_.jpg:small
299 ms
picto_valider.png
870 ms
bg_numero.png
875 ms
bg_numero_gris.png
869 ms
left_tooltip.png
838 ms
jot
27 ms
mobil.css
162 ms
print.css
83 ms
fhf.fr 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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
fhf.fr 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
Page has valid source maps
fhf.fr 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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fhf.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Fhf.fr 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.
fhf.fr
Open Graph description is not detected on the main page of FHF. 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: