Tools & Wizards About Us
itineraire.info screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

itineraire.info

Itinéraires, cartes et trafic

Page Load Speed

1.9 sec in total

First Response

199 ms

Resources Loaded

1.5 sec

Page Rendered

257 ms

itineraire.info screenshot

About Website

Welcome to itineraire.info homepage info - get ready to check Itineraire best content for France right away, or after learning these important things about itineraire.info

Trouvez le meilleur itinéraire pour votre trajet, évitez les bouchons en vérifiant l'état des routes en direct, consultez les cartes des villes.

Visit itineraire.info

Key Findings

We analyzed Itineraire.info page load time and found that the first response time was 199 ms and then it took 1.7 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

itineraire.info performance score

0

Network Requests Diagram

itineraire.info

199 ms

www.itineraire.info

273 ms

css

26 ms

88 ms

bugsnag-2.min.js

159 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 20% of them (12 requests) were addressed to the original Itineraire.info, 18% (11 requests) were made to Google.com and 15% (9 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (507 ms) belongs to the original domain Itineraire.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 63.5 kB (20%)

Content Size

314.3 kB

After Optimization

250.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Itineraire.info main page is 314.3 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. 40% of websites need less resources to load. Javascripts take 163.1 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 9.0 kB

  • Original 12.6 kB
  • After minification 10.9 kB
  • After compression 3.6 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 1.7 kB, which is 14% 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 9.0 kB or 71% of the original size.

Image Optimization

-1%

Potential reduce by 1.3 kB

  • Original 137.0 kB
  • After minification 135.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. Itineraire images are well optimized though.

JavaScript Optimization

-32%

Potential reduce by 52.3 kB

  • Original 163.1 kB
  • After minification 158.5 kB
  • After compression 110.8 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 52.3 kB or 32% of the original size.

CSS Optimization

-57%

Potential reduce by 895 B

  • Original 1.6 kB
  • After minification 1.4 kB
  • After compression 667 B

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. Itineraire.info needs all CSS files to be minified and compressed as it can save up to 895 B or 57% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (70%)

Requests Now

47

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Itineraire. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

itineraire.info

itineraire.info

199 ms

www.itineraire.info

www.itineraire.info

273 ms

css

css

26 ms

88 ms

bugsnag-2.min.js

bugsnag-2.min.js

159 ms

modernizr.custom.js

modernizr.custom.js

162 ms

adsbygoogle.js

adsbygoogle.js

7 ms

346 ms

loader.js

loader.js

403 ms

p.js

p.js

366 ms

cnil.js

cnil.js

279 ms

logo.png

logo.png

100 ms

bg-map1910.jpg

bg-map1910.jpg

507 ms

trame.png

trame.png

99 ms

ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff

ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff

84 ms

toadOcfmlt9b38dHJxOBGNbE_oMaV8t2eFeISPpzbdE.woff

toadOcfmlt9b38dHJxOBGNbE_oMaV8t2eFeISPpzbdE.woff

77 ms

toadOcfmlt9b38dHJxOBGJ6-ys_j0H4QL65VLqzI3wI.woff

toadOcfmlt9b38dHJxOBGJ6-ys_j0H4QL65VLqzI3wI.woff

77 ms

ca-pub-4765395698236376.js

ca-pub-4765395698236376.js

44 ms

zrt_lookup.html

zrt_lookup.html

54 ms

show_ads_impl.js

show_ads_impl.js

56 ms

flaticon.woff

flaticon.woff

101 ms

pla

pla

23 ms

analytics.js

analytics.js

37 ms

ads

ads

284 ms

tag.js

tag.js

130 ms

osd.js

osd.js

43 ms

ads

ads

217 ms

collect

collect

39 ms

ads.js

ads.js

84 ms

collect

collect

10 ms

conversion_async.js

conversion_async.js

14 ms

21 ms

19 ms

98 ms

96 ms

120 ms

82 ms

95 ms

79 ms

81 ms

63 ms

67 ms

60 ms

337685816173512097

337685816173512097

71 ms

abg.js

abg.js

71 ms

m_js_controller.js

m_js_controller.js

88 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

139 ms

50 ms

48 ms

css

css

182 ms

93 ms

x_button_blue2.png

x_button_blue2.png

55 ms

s

s

45 ms

print.css

print.css

112 ms

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

6 ms

favicon

favicon

55 ms

nessie_icon_thin_arrow_big_white.png

nessie_icon_thin_arrow_big_white.png

33 ms

collect

collect

14 ms

ui

ui

37 ms

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff

53 ms

SEO Factors

itineraire.info SEO score

0

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Itineraire.info can be misinterpreted by Google and other search engines. Our service has detected that French 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 Itineraire.info 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.

Social Sharing Optimization

itineraire.info

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