2.4 sec in total
385 ms
1.9 sec
192 ms
Visit itineraire-metro.fr now to see the best up-to-date Itineraire Metro content for France and also check out these interesting facts you probably never knew about itineraire-metro.fr
Recherche d'itinéraires en métro à Paris : Calcul rapide du meilleur trajet entre deux stations de métro ou de RER parisien. L'itinéraire trouvé s'affiche sur un plan ...
Visit itineraire-metro.frWe analyzed Itineraire-metro.fr page load time and found that the first response time was 385 ms and then it took 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.
itineraire-metro.fr performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value4.7 s
32/100
25%
Value6.1 s
45/100
10%
Value2,260 ms
6/100
30%
Value0.335
34/100
15%
Value12.1 s
16/100
10%
385 ms
40 ms
123 ms
10 ms
177 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 14% of them (9 requests) were addressed to the original Itineraire-metro.fr, 13% (8 requests) were made to Apis.google.com and 13% (8 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (575 ms) relates to the external source Staticxx.facebook.com.
Page size can be reduced by 62.0 kB (36%)
169.9 kB
107.9 kB
In fact, the total size of Itineraire-metro.fr main page is 169.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. 65% of websites need less resources to load. Javascripts take 104.4 kB which makes up the majority of the site volume.
Potential reduce by 24.9 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 24.9 kB or 77% of the original size.
Potential reduce by 308 B
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 Metro images are well optimized though.
Potential reduce by 16.5 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 16.5 kB or 16% of the original size.
Potential reduce by 20.3 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. Itineraire-metro.fr needs all CSS files to be minified and compressed as it can save up to 20.3 kB or 80% of the original size.
Number of requests can be reduced by 36 (64%)
56
20
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Itineraire Metro. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
itineraire-metro.fr
385 ms
ga.js
40 ms
widgets.js
123 ms
adsbygoogle.js
10 ms
platform.js
177 ms
all.js
310 ms
jquery-ui-1.10.4.custom.min.css
116 ms
jquery-1.9.1.min.js
20 ms
jquery-ui.min.js
22 ms
fonctions.js
210 ms
autocompletion_depart.js
211 ms
autocompletion_destination.js
211 ms
english.jpg
244 ms
deutsch.jpg
211 ms
ca-pub-1923843564326275.js
106 ms
zrt_lookup.html
51 ms
show_ads_impl.js
57 ms
__utm.gif
15 ms
collect
112 ms
ads
272 ms
osd.js
36 ms
ga-audiences
116 ms
ads
278 ms
cb=gapi.loaded_0
95 ms
cb=gapi.loaded_1
126 ms
fastbutton
191 ms
style1304.css
158 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
161 ms
ui-bg_inset-hard_100_fcfdfd_1x100.png
127 ms
ads
204 ms
279 ms
postmessageRelay
119 ms
xd_arbiter.php
326 ms
xd_arbiter.php
575 ms
suggestion_autolayout_V2_7.css
101 ms
suggestion_autolayout_V2_7.js
101 ms
layout_engine.js
153 ms
abg.js
227 ms
rs=AGLTcCPQjKo4igjqiAXqpITWlOY1Z_pwKQ
20 ms
tweet_button.6a78875565a912489e9aef879c881358.fr.html
179 ms
cb=gapi.loaded_0
169 ms
cb=gapi.loaded_1
97 ms
grlryt2bdKIyfMSOhzd1eA.woff
272 ms
css
226 ms
api.js
154 ms
core:rpc:shindig.random:shindig.sha1.js
240 ms
2536007149-postmessagerelay.js
221 ms
m_js_controller.js
189 ms
googlelogo_color_112x36dp.png
138 ms
6933574313795811046
86 ms
s
77 ms
x_button_blue2.png
68 ms
favicon
89 ms
nessie_icon_tiamat_white.png
46 ms
favicon
101 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
24 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
4 ms
ui
24 ms
like.php
58 ms
like.php
75 ms
jot.html
27 ms
R-A8WEDAygL.js
494 ms
LVx-xkvaJ0b.png
556 ms
itineraire-metro.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-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
itineraire-metro.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
itineraire-metro.fr SEO score
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
ISO-8859-15
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Itineraire-metro.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 Itineraire-metro.fr main page’s claimed encoding is iso-8859-15. 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.
itineraire-metro.fr
Open Graph description is not detected on the main page of Itineraire Metro. 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: