2.6 sec in total
474 ms
2 sec
138 ms
Visit indicespro.insee.fr now to see the best up-to-date Indicespro Insee content for France and also check out these interesting facts you probably never knew about indicespro.insee.fr
Recherchez vos statistiques par thème, niveau géographique, catégorie ou collection
Visit indicespro.insee.frWe analyzed Indicespro.insee.fr page load time and found that the first response time was 474 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 40% of websites can load faster.
indicespro.insee.fr performance score
474 ms
187 ms
286 ms
191 ms
192 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that all of those requests were addressed to Indicespro.insee.fr and no external sources were called. The less responsive or slowest element that took the longest time to load (560 ms) relates to the external source Insee.fr.
Page size can be reduced by 238.5 kB (65%)
368.8 kB
130.3 kB
In fact, the total size of Indicespro.insee.fr main page is 368.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Javascripts take 215.2 kB which makes up the majority of the site volume.
Potential reduce by 12.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 12.8 kB or 76% of the original size.
Potential reduce by 7.5 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, Indicespro Insee needs image optimization as it can save up to 7.5 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 151.2 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 151.2 kB or 70% of the original size.
Potential reduce by 67.0 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. Indicespro.insee.fr needs all CSS files to be minified and compressed as it can save up to 67.0 kB or 81% of the original size.
Number of requests can be reduced by 50 (77%)
65
15
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Indicespro Insee. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
default.asp
474 ms
insee.css
187 ms
jquery-latest.js
286 ms
jquery.ui.core.min.js
191 ms
jquery.ui.widget.min.js
192 ms
jquery.ui.mouse.min.js
199 ms
jquery.ui.slider.min.js
200 ms
jquery.ui.position.min.js
281 ms
jquery.ui.menu.min.js
286 ms
jquery.ui.autocomplete.min.js
287 ms
date.inc.js
298 ms
j_slider_graph.js
300 ms
j_commun.js
374 ms
j_url.js
378 ms
j_arbo.js
380 ms
j_autocomplete_ui.js
380 ms
j_prerempli.js
395 ms
j_infobulle.js
398 ms
j_map_regions.js
466 ms
j_menu_onglets.js
470 ms
j_carousel.js
471 ms
j_carte_multi.js
474 ms
j_multi_figures.js
495 ms
j_lanceur.js
497 ms
style.css
560 ms
commun.css
389 ms
arbre.css
389 ms
google.css
392 ms
j_styles.css
420 ms
impression.css
431 ms
j_arbo.css
103 ms
j_form_text.css
107 ms
ac_autocomplete.css
104 ms
j_diapo.css
103 ms
j_carousel.css
108 ms
j_slider_graph.css
104 ms
j_autocomplete.css
194 ms
jquery.ui.autocomplete.min.css
195 ms
jquery.ui.core.min.css
197 ms
jquery.ui.menu.min.css
197 ms
jquery.ui.theme.min.css
203 ms
jquery.ui.slider.min.css
204 ms
j_select_boutons.css
286 ms
logo_insee.png
99 ms
j_prerempli.js
102 ms
getpageinfo.js
98 ms
loupe.gif
98 ms
google_home.png
102 ms
sousligne-rouge-h3.gif
97 ms
menu-gauche-1.png
163 ms
menu-gauche-2.png
182 ms
picto_titre_rouge.gif
190 ms
puce_lien.gif
191 ms
puce_liste.gif
192 ms
deco-menu-bas.png
202 ms
lettres.png
257 ms
avis.png
276 ms
rss.png
288 ms
twitter.png
284 ms
slideshare.png
286 ms
sse.png
302 ms
edutheque.png
352 ms
logo-statapprendre.jpg
371 ms
logoquetelet-petit.png
380 ms
logo-casd-bas-page.png
381 ms
data-gouv.png
388 ms
indicespro.insee.fr SEO score
FR
FR
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Indicespro.insee.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 Indicespro.insee.fr main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
indicespro.insee.fr
Open Graph description is not detected on the main page of Indicespro Insee. 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: