3.6 sec in total
268 ms
3 sec
365 ms
Welcome to sante.gouv.fr homepage info - get ready to check Sante best content for France right away, or after learning these important things about sante.gouv.fr
Le ministère Ministère de la Santé et de la Prévention met en œuvre les politiques relatives à la solidarité, à la cohésion sociale, à la santé publique, à l'organisation du système de santé et à...
Visit sante.gouv.frWe analyzed Sante.gouv.fr page load time and found that the first response time was 268 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
sante.gouv.fr performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value12.0 s
0/100
25%
Value11.0 s
6/100
10%
Value4,120 ms
1/100
30%
Value0.013
100/100
15%
Value15.1 s
7/100
10%
268 ms
626 ms
531 ms
269 ms
184 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Sante.gouv.fr, 96% (91 requests) were made to Social-sante.gouv.fr and 1% (1 request) were made to Eregie.premier-ministre.gouv.fr. The less responsive or slowest element that took the longest time to load (920 ms) relates to the external source Social-sante.gouv.fr.
Page size can be reduced by 3.7 MB (61%)
6.1 MB
2.4 MB
In fact, the total size of Sante.gouv.fr main page is 6.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. 45% of websites need less resources to load. Javascripts take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 242.4 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 242.4 kB or 76% of the original size.
Potential reduce by 105.6 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. Sante images are well optimized though.
Potential reduce by 1.8 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.8 MB or 82% of the original size.
Potential reduce by 1.6 MB
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. Sante.gouv.fr needs all CSS files to be minified and compressed as it can save up to 1.6 MB or 80% of the original size.
Number of requests can be reduced by 60 (67%)
89
29
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sante. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
sante.gouv.fr
268 ms
social-sante.gouv.fr
626 ms
bootstrap-cssify-b18a392.css
531 ms
responsive-cssify-89eca15.css
269 ms
spip.css
184 ms
spip.list-cssify-5de74c2.css
190 ms
jquery.ui.core.css
176 ms
jquery.ui.slider.css
201 ms
jquery.ui.datepicker.css
210 ms
jquery.ui.theme.css
264 ms
colorbox.css
287 ms
barre_outils.css
295 ms
spip.php
304 ms
spip.agenda.css
352 ms
leaflet.css
375 ms
leaflet-plugins.css
386 ms
leaflet.markercluster.css
400 ms
enluminurestypo.css
439 ms
boutonstexte.css
443 ms
sommaire.css
503 ms
tab.css
504 ms
chosen.css
504 ms
spip.chosen.css
524 ms
albums.css
530 ms
html5_controls.css
538 ms
oembed.css
546 ms
jquery.js
920 ms
jquery.form.js
675 ms
jquery.autosave.js
610 ms
jquery.placeholder-label.js
618 ms
ajaxCallback.js
626 ms
jquery.cookie.js
633 ms
jquery.ui.core.js
696 ms
jquery.ui.widget.js
707 ms
jquery.ui.mouse.js
712 ms
jquery.ui.sortable.js
806 ms
jquery.ui.draggable.js
767 ms
cibc_en_bas_fond_noir.css
682 ms
jquery.ui.droppable.js
690 ms
jquery.ui.slider.js
634 ms
jquery.ui.datepicker.js
766 ms
chosen.jquery.js
765 ms
spip_chosen.js
689 ms
jquery.mousewheel.js
633 ms
flowplayer-3.2.12.min.js
622 ms
mediaspip_player.js
688 ms
mediaspip_fallback_flash.js
683 ms
jquery.colorbox.js
645 ms
spip.mediabox.js
664 ms
jquery.markitup_pour_spip.js
681 ms
jquery.previsu_spip.js
665 ms
spip.php
677 ms
boutonstexte.js
642 ms
mes_onglets.js
643 ms
links.js
605 ms
jsdyn-mediaspip_player_lang_js-cd2e693e.js
633 ms
bootstrap-collapse.js
641 ms
bootstrap-transition.js
657 ms
bootstrap-scrollspy.js
648 ms
bootstrap-tooltip.js
666 ms
bootstrap-popover.js
683 ms
bootstrap-alert.js
694 ms
1193469153@Middle1,Position1
167 ms
print.css
89 ms
siteon0.jpg
291 ms
b066ef06a1940c950f28d127e8dfca3c-b53fa.jpg
414 ms
2bb994b51aea2e2af86bdd99fd997a80-ccb80.jpg
292 ms
9de5cc5615b05effac28bff7f79efa9d-55bd5.jpg
272 ms
200964671b63548a02355ed2710f6995.jpg
116 ms
8a242e47ea162694c9c39f355b4bfaf3.png
254 ms
9f408cf678e34a2dbcfc5320a574eb04.jpg
288 ms
e67ef6a83b87dc40a3b53f97b85c27aa.jpg
312 ms
0c64151f74345f13fc16afcb8707bdb7.jpg
403 ms
2b3fc507cb0ca84dd190a2d0f487b59a.jpg
531 ms
droits-femmes.jpg
472 ms
6621458fb0e2a17b93a9569fe63148aa.jpg
480 ms
99778dc14311a0f9ac4747893da4bde8.png
775 ms
38ab22768291edddb94118dea5993feb.jpg
492 ms
3b1977af8d5cc54b330b1d83cb55617b.jpg
502 ms
d15346e056e2a93cf330b7527fc4c3b1.png
565 ms
56af522b77591ca5c964789449f91568.png
576 ms
4609f7785feab7c20fb3094b4a48de35.png
589 ms
03fbeac38224704f9db7de579b65ebea.jpg
594 ms
opensans-regular-webfont.woff
641 ms
notosans-bold-webfont.woff
682 ms
fontello.woff
612 ms
notosans-regular-webfont.woff
707 ms
1422433350
181 ms
4856fb6a9d410684cfa66340cecdea6e.png
848 ms
3f707f2f2646bbecfea779dee03c38cb.jpg
759 ms
jquery.responsiveslides.js
611 ms
fontsizeup.png
592 ms
fontsizedown.png
604 ms
spip.php
541 ms
bcg.xiti
210 ms
sante.gouv.fr 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-hidden="true"] elements contain focusable descendents
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
sante.gouv.fr 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
sante.gouv.fr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sante.gouv.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 Sante.gouv.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.
sante.gouv.fr
Open Graph description is not detected on the main page of Sante. 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: