3.8 sec in total
481 ms
3 sec
333 ms
Visit routekm.fr now to see the best up-to-date Routekm content and also check out these interesting facts you probably never knew about routekm.fr
Calcul de l'itinéraire routier meilleur. Vérifiez l'itinéraire complet des routes, la distance et le temps de déplacement. Imprimer la carte avec les directions de l'itinéraire.
Visit routekm.frWe analyzed Routekm.fr page load time and found that the first response time was 481 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
routekm.fr performance score
name
value
score
weighting
Value2.6 s
63/100
10%
Value6.8 s
7/100
25%
Value6.6 s
37/100
10%
Value1,470 ms
14/100
30%
Value0.351
31/100
15%
Value10.8 s
22/100
10%
481 ms
8 ms
163 ms
316 ms
165 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Routekm.fr, 28% (30 requests) were made to Maps.googleapis.com and 15% (16 requests) were made to Percorsokm.it. The less responsive or slowest element that took the longest time to load (481 ms) belongs to the original domain Routekm.fr.
Page size can be reduced by 621.2 kB (40%)
1.6 MB
939.4 kB
In fact, the total size of Routekm.fr main page is 1.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 847.9 kB which makes up the majority of the site volume.
Potential reduce by 57.7 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 57.7 kB or 81% of the original size.
Potential reduce by 10.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. Routekm images are well optimized though.
Potential reduce by 523.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 523.8 kB or 62% of the original size.
Potential reduce by 29.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. Routekm.fr needs all CSS files to be minified and compressed as it can save up to 29.3 kB or 82% of the original size.
Number of requests can be reduced by 53 (52%)
102
49
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Routekm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and as a result speed up the page load time.
www.routekm.fr
481 ms
adsbygoogle.js
8 ms
css_v2.css
163 ms
jquery.min.js
316 ms
jquery-ui-1.8.23.custom.css
165 ms
jquery-ui-1.8.23.custom.min.js
331 ms
js
86 ms
cookiechoices.js
162 ms
tripbase-fr.js
280 ms
analytics.js
32 ms
logo.png
100 ms
fr.png
99 ms
en.png
100 ms
de.png
100 ms
es.png
101 ms
it.png
99 ms
div.png
184 ms
ca-pub-2390598910486792.js
49 ms
zrt_lookup.html
51 ms
show_ads_impl.js
78 ms
start.png
156 ms
end.png
157 ms
collect
23 ms
i-info.png
132 ms
widgets.js
119 ms
platform.js
194 ms
all.js
235 ms
ads
312 ms
osd.js
56 ms
ads
353 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
208 ms
pla
29 ms
cb=gapi.loaded_0
11 ms
cb=gapi.loaded_1
34 ms
fastbutton
126 ms
postmessageRelay
111 ms
246 ms
cb=gapi.loaded_0
21 ms
cb=gapi.loaded_1
18 ms
xd_arbiter.php
211 ms
xd_arbiter.php
384 ms
White_Exterior_Locations_Red_CTA_300x250.jpg
188 ms
sbhK2lTE.js
181 ms
abg.js
186 ms
3193398744-postmessagerelay.js
163 ms
rpc:shindig_random.js
145 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
113 ms
m_js_controller.js
116 ms
cTrvNaRi.html
98 ms
cb=gapi.loaded_0
84 ms
favicon
123 ms
s
93 ms
googlelogo_color_112x36dp.png
153 ms
nessie_icon_tiamat_white.png
77 ms
x_button_blue2.png
72 ms
jot
193 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
69 ms
common.js
31 ms
util.js
62 ms
directions.js
60 ms
controls.js
60 ms
places_impl.js
57 ms
map.js
52 ms
onion.js
81 ms
openhand_8_8.cur
184 ms
AuthenticationService.Authenticate
150 ms
DirectionsService.Route
136 ms
infowindow.js
133 ms
css
177 ms
marker.js
123 ms
powered-by-google-on-white3.png
131 ms
autocomplete-icons.png
151 ms
share_button.php
130 ms
ViewportInfoService.GetViewportInfo
222 ms
stats.js
143 ms
transparent.png
96 ms
google4.png
50 ms
mapcnt6.png
53 ms
sv5.png
51 ms
tmapctrl.png
42 ms
cb_scout5.png
42 ms
tmapctrl4.png
41 ms
imgs8.png
46 ms
05-jfvEi0Bv.js
398 ms
LVx-xkvaJ0b.png
464 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
28 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
125 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
126 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
125 ms
vt
46 ms
vt
34 ms
vt
30 ms
vt
31 ms
vt
44 ms
vt
45 ms
vt
33 ms
vt
44 ms
vt
53 ms
vt
52 ms
vt
45 ms
vt
54 ms
vt
51 ms
vt
52 ms
vt
54 ms
vt
106 ms
ads
241 ms
ESA-Evergreen_Man_Brown_300x250.jpg
72 ms
routekm.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
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
routekm.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
routekm.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
Tap targets are not sized appropriately
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Routekm.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 Routekm.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.
routekm.fr
Open Graph data is detected on the main page of Routekm. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: