8.2 sec in total
2.1 sec
5.9 sec
254 ms
Welcome to travelplanner.mobiliteit.lu homepage info - get ready to check Travelplanner Mobiliteit best content for Luxembourg right away, or after learning these important things about travelplanner.mobiliteit.lu
Visit travelplanner.mobiliteit.luWe analyzed Travelplanner.mobiliteit.lu page load time and found that the first response time was 2.1 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
travelplanner.mobiliteit.lu performance score
2053 ms
918 ms
444 ms
225 ms
222 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 45% of them (34 requests) were addressed to the original Travelplanner.mobiliteit.lu, 34% (26 requests) were made to Mobiliteit.lu and 9% (7 requests) were made to Api.geoportail.lu. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Mobiliteit.lu.
Page size can be reduced by 3.0 MB (77%)
3.9 MB
911.4 kB
In fact, the total size of Travelplanner.mobiliteit.lu main page is 3.9 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. 50% of websites need less resources to load. Javascripts take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 98.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 98.8 kB or 79% of the original size.
Potential reduce by 5.2 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, Travelplanner Mobiliteit needs image optimization as it can save up to 5.2 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.4 MB
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 2.4 MB or 75% of the original size.
Potential reduce by 549.6 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. Travelplanner.mobiliteit.lu needs all CSS files to be minified and compressed as it can save up to 549.6 kB or 86% of the original size.
Number of requests can be reduced by 54 (75%)
72
18
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Travelplanner Mobiliteit. 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 15 to 1 for CSS and as a result speed up the page load time.
travelplanner.mobiliteit.lu
2053 ms
fn
918 ms
hafas_default.css
444 ms
hafas_default_calendar.css
225 ms
simpleSuggest.css
222 ms
css_ymFDHu66tgcT81CcalD-PnvTndjazMlKaqo_ipWg-2o.css
1327 ms
css_MnXiytJtb186Ydycnpwpw34cuUsHaKc80ey5LiQXhSY.css
1293 ms
css_dMdQfKmcr5eec7SAcMOnT40mXUU6fqNiIpqsFUm_Q9M.css
1295 ms
css_ckGBkn5dQlxWEjjO2ZJxDlbbVUAuHp_s1ihZle91Aq4.css
1296 ms
bootstrap.css
2127 ms
css_NNboFVj-4BseHisA-FiXXhuV-nvEwlkWqHQQuJLteps.css
1297 ms
modernizr.js
1567 ms
js_gam0c92gTspMYtadSvCYU4LmcrJOl6mruic2otZm0Ic.js
1480 ms
js_uiF75tUtWsZIPud4DMk7FvzKr_zA8oqdtm3l-SnQKJ0.js
1389 ms
js_DGHNEu6WlukTgwD_uczzHEQIYq064kDPXgPUosiQE7o.js
1391 ms
js_byKrRN4MspAzubaQQKW4WKM82vxpU_ZvCCZo-776Utk.js
1851 ms
ipm4mfs.js
231 ms
hafas_standard.js
230 ms
SimpleSuggest.js
223 ms
prototype.js
308 ms
hafas_utilities.js
221 ms
hafas_standard_calendar_combined.js
446 ms
HafasHistory.js
297 ms
hafas_tp.js
555 ms
AJSMapBaseClass.js
261 ms
CCoord.js
338 ms
CShowAjaxContent.js
347 ms
CLoadAjaxContent.js
302 ms
cookies.js
330 ms
AAjaxMap.js
338 ms
AOpenLayerMap.js
348 ms
ext-all.css
396 ms
xtheme-gray.css
301 ms
api.css
298 ms
ext-base.js
314 ms
ext-all.js
871 ms
geoadmin.js
1114 ms
api.js
892 ms
COLLuxembourgMap.js
367 ms
js_paiTaEsc1HNeBS2rkLc1NrprKrFnApv70kuY8awAaTI.js
975 ms
2b14d1
22 ms
analytics.js
50 ms
travelplanner.mobiliteit.lu
190 ms
collect
11 ms
jsmap.css
225 ms
mobilite_logo.svg
263 ms
mobile-logo.svg
118 ms
VV.svg
119 ms
explose_logo@2x.png
116 ms
close-lightbox.png
120 ms
map_stop_station.png
122 ms
chbox_disabled.png
121 ms
flag_france.png
123 ms
flag_uk.png
122 ms
flag_germany.png
123 ms
ajax_load.gif
261 ms
v6kxEtb1i-9Wb1mVZNMXEK2o570GNXn1_vrzCEXE5Z3ff4YMgsMZeMJ6Mk6f5Mb.woff
240 ms
C8hO0DK_yta6YGZdWUILGFLEJJ5w5fFGU758sPbGQZGffJxMgsMZeMJ6Mk6f5Mw.woff
276 ms
fontawesome-webfont.woff
372 ms
FR.png
148 ms
EN.png
148 ms
DE.png
147 ms
icon_mapinput.png
130 ms
icon_map_real.png
130 ms
icon_arrow.png
126 ms
icon_day_earlier.png
116 ms
icon_day_later.png
141 ms
icon_day_earlier.png
139 ms
icon_day_later.png
139 ms
calendar.jpg
175 ms
footer.png
174 ms
calendar.png
182 ms
sprite.jpg
95 ms
carret.png
96 ms
piwik.js
465 ms
p.gif
123 ms
travelplanner.mobiliteit.lu SEO score
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Travelplanner.mobiliteit.lu 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 Travelplanner.mobiliteit.lu 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.
travelplanner.mobiliteit.lu
Open Graph description is not detected on the main page of Travelplanner Mobiliteit. 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: