Tools & Wizards About Us
recensement.insee.fr screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

recensement.insee.fr

Les résultats des recensements de la population | Insee

Page Load Speed

2.3 sec in total

First Response

368 ms

Resources Loaded

1.8 sec

Page Rendered

137 ms

recensement.insee.fr screenshot

About Website

Click here to check amazing Recensement Insee content for France. Otherwise, check out these important facts you probably never knew about recensement.insee.fr

Visit recensement.insee.fr

Key Findings

We analyzed Recensement.insee.fr page load time and found that the first response time was 368 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

recensement.insee.fr performance score

0

Network Requests Diagram

default.asp

368 ms

insee.css

160 ms

jquery-latest.js

251 ms

jquery.ui.core.min.js

168 ms

jquery.ui.widget.min.js

166 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that all of those requests were addressed to Recensement.insee.fr and no external sources were called. The less responsive or slowest element that took the longest time to load (482 ms) relates to the external source Insee.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 241.4 kB (65%)

Content Size

371.9 kB

After Optimization

130.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Recensement.insee.fr main page is 371.9 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. 15% of websites need less resources to load. Javascripts take 215.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 15.7 kB

  • Original 20.0 kB
  • After minification 18.5 kB
  • After compression 4.3 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 15.7 kB or 79% of the original size.

Image Optimization

-14%

Potential reduce by 7.5 kB

  • Original 53.9 kB
  • After minification 46.4 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, Recensement 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.

JavaScript Optimization

-70%

Potential reduce by 151.2 kB

  • Original 215.2 kB
  • After minification 184.2 kB
  • After compression 64.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 151.2 kB or 70% of the original size.

CSS Optimization

-81%

Potential reduce by 67.0 kB

  • Original 82.8 kB
  • After minification 65.2 kB
  • After compression 15.8 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. Recensement.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.

Requests Breakdown

Number of requests can be reduced by 51 (77%)

Requests Now

66

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Recensement 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.

Network Requests Diagram

default.asp

default.asp

368 ms

insee.css

insee.css

160 ms

jquery-latest.js

jquery-latest.js

251 ms

jquery.ui.core.min.js

jquery.ui.core.min.js

168 ms

jquery.ui.widget.min.js

jquery.ui.widget.min.js

166 ms

jquery.ui.mouse.min.js

jquery.ui.mouse.min.js

176 ms

jquery.ui.slider.min.js

jquery.ui.slider.min.js

177 ms

jquery.ui.position.min.js

jquery.ui.position.min.js

240 ms

jquery.ui.menu.min.js

jquery.ui.menu.min.js

248 ms

jquery.ui.autocomplete.min.js

jquery.ui.autocomplete.min.js

249 ms

date.inc.js

date.inc.js

262 ms

j_slider_graph.js

j_slider_graph.js

263 ms

j_commun.js

j_commun.js

320 ms

j_url.js

j_url.js

329 ms

j_arbo.js

j_arbo.js

330 ms

j_autocomplete_ui.js

j_autocomplete_ui.js

332 ms

j_prerempli.js

j_prerempli.js

348 ms

j_infobulle.js

j_infobulle.js

350 ms

j_map_regions.js

j_map_regions.js

401 ms

j_menu_onglets.js

j_menu_onglets.js

410 ms

j_carousel.js

j_carousel.js

410 ms

j_carte_multi.js

j_carte_multi.js

413 ms

j_multi_figures.js

j_multi_figures.js

434 ms

j_lanceur.js

j_lanceur.js

435 ms

style.css

style.css

482 ms

commun.css

commun.css

348 ms

arbre.css

arbre.css

347 ms

google.css

google.css

352 ms

j_styles.css

j_styles.css

376 ms

impression.css

impression.css

383 ms

j_arbo.css

j_arbo.css

87 ms

j_form_text.css

j_form_text.css

87 ms

ac_autocomplete.css

ac_autocomplete.css

85 ms

j_diapo.css

j_diapo.css

85 ms

j_carousel.css

j_carousel.css

90 ms

j_slider_graph.css

j_slider_graph.css

91 ms

j_autocomplete.css

j_autocomplete.css

167 ms

jquery.ui.autocomplete.min.css

jquery.ui.autocomplete.min.css

167 ms

jquery.ui.core.min.css

jquery.ui.core.min.css

170 ms

jquery.ui.menu.min.css

jquery.ui.menu.min.css

168 ms

jquery.ui.theme.min.css

jquery.ui.theme.min.css

178 ms

jquery.ui.slider.min.css

jquery.ui.slider.min.css

179 ms

j_select_boutons.css

j_select_boutons.css

248 ms

logo_insee.png

logo_insee.png

95 ms

j_prerempli.js

j_prerempli.js

87 ms

getpageinfo.js

getpageinfo.js

88 ms

loupe.gif

loupe.gif

86 ms

google_home.png

google_home.png

90 ms

sousligne-rouge-h3.gif

sousligne-rouge-h3.gif

91 ms

menu-gauche-1.png

menu-gauche-1.png

144 ms

menu-gauche-2.png

menu-gauche-2.png

159 ms

picto_titre_rouge.gif

picto_titre_rouge.gif

158 ms

picto_soustitre_gris.gif

picto_soustitre_gris.gif

167 ms

puce_lien.gif

puce_lien.gif

176 ms

deco-menu-bas.png

deco-menu-bas.png

178 ms

puce_liste.gif

puce_liste.gif

225 ms

lettres.png

lettres.png

240 ms

avis.png

avis.png

242 ms

rss.png

rss.png

249 ms

twitter.png

twitter.png

263 ms

slideshare.png

slideshare.png

266 ms

sse.png

sse.png

308 ms

edutheque.png

edutheque.png

322 ms

logo-statapprendre.jpg

logo-statapprendre.jpg

324 ms

logoquetelet-petit.png

logoquetelet-petit.png

331 ms

logo-casd-bas-page.png

logo-casd-bas-page.png

350 ms

data-gouv.png

data-gouv.png

354 ms

SEO Factors

recensement.insee.fr SEO score

0

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Recensement.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 Recensement.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.

Social Sharing Optimization

recensement.insee.fr

Open Graph description is not detected on the main page of Recensement 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: