5.5 sec in total
184 ms
5 sec
343 ms
Click here to check amazing Thalys content. Otherwise, check out these important facts you probably never knew about thalys.nl
Reserveer uw treintickets naar Parijs, Brussel, Amsterdam en Keulen rechtstreeks via Thalys.com en profiteer van de beste tarieven!
Visit thalys.nlWe analyzed Thalys.nl page load time and found that the first response time was 184 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
thalys.nl performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value4.9 s
29/100
25%
Value14.5 s
1/100
10%
Value19,160 ms
0/100
30%
Value0.186
66/100
15%
Value29.8 s
0/100
10%
184 ms
716 ms
126 ms
83 ms
167 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Thalys.nl, 3% (4 requests) were made to Config1.veinteractive.com and 1% (2 requests) were made to Dev.visualwebsiteoptimizer.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Thalys.com.
Page size can be reduced by 1.5 MB (55%)
2.7 MB
1.2 MB
In fact, the total size of Thalys.nl main page is 2.7 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. 55% of websites need less resources to load. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 66.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 66.7 kB or 82% of the original size.
Potential reduce by 65.3 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. Thalys images are well optimized though.
Potential reduce by 1.2 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 1.2 MB or 76% of the original size.
Potential reduce by 205.9 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. Thalys.nl needs all CSS files to be minified and compressed as it can save up to 205.9 kB or 86% of the original size.
Number of requests can be reduced by 69 (52%)
132
63
The browser has sent 132 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thalys. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
nl
184 ms
nl
716 ms
tc_abtest.js
126 ms
reset.css
83 ms
common.css
167 ms
common-xx-nl.css
255 ms
booking-light.css
340 ms
booking-light-xx-nl.css
409 ms
uniform.default.css
420 ms
calendar.css
441 ms
formulaire.css
446 ms
map.css
450 ms
map-xx-nl.css
475 ms
home.css
489 ms
home-xx-nl.css
498 ms
home-nl-nl.css
526 ms
home.css
531 ms
boutons-forms-nl.css
535 ms
boutons-forms.css
565 ms
jquery_all.min.js
843 ms
popin.js
577 ms
jquery.maskedinput.min.js
611 ms
jquery-ui.datepicker.nl.js
618 ms
constantes.js.php
621 ms
labels.js.php
665 ms
common.js.php
659 ms
common.js
785 ms
conciergerie.js
704 ms
bookingPopin.js.php
707 ms
bookingPopin.js
737 ms
bookingLight.js.php
750 ms
bookingLight.js
792 ms
bookingLightV2.js
794 ms
home.js
816 ms
map.js.php
842 ms
map.js
871 ms
tc_thalys.js
155 ms
clobs.js
989 ms
j.php
34 ms
booking-light.css
722 ms
v.gif
3 ms
bg_grey_95.png
828 ms
info.png
826 ms
btn-bg-rouge.png
828 ms
close.png
825 ms
bienvenue_nl.png
828 ms
bg.jpg
825 ms
bg_conteneur_ombre.png
910 ms
facebook.png
930 ms
twitter.png
920 ms
youtube.png
910 ms
home.png
1007 ms
btn_thalys_account.png
918 ms
header_print.gif
994 ms
home.png
989 ms
nav-shadow.png
1016 ms
title-line.gif
1015 ms
bg-span.gif
1024 ms
white-arrow.png
1078 ms
info_trafic_banner.png
1079 ms
pa_bxl_20160119_nl_nl.jpg
1524 ms
pa_bxl_20160119_nl_nl.jpg
1275 ms
bons_plans_foot2016_global_nl.jpg
1629 ms
bons_plans_foot2016_global_nl.jpg
1210 ms
jeu_concours_gateau_20160303_global_nl.jpg
1550 ms
jeu_concours_gateau_20160303_global_nl.jpg
1313 ms
vignette-infotrafic-big.png
1304 ms
orange-flag.png
1365 ms
vignette_home_bg.png
1397 ms
panel_avis_thalys_global_nl.jpg
1395 ms
newsletter.jpg
1453 ms
btn_footer_envoyer.jpg
1474 ms
bkg_toolbox.png
1490 ms
green_flag.png
1539 ms
red_flag.png
1555 ms
analytics.js
835 ms
tag.js
976 ms
activity;src=1345729;type=thaly492;cat=thaly530;ord=769294379
856 ms
ld.js
854 ms
conversion.js
830 ms
line-red.png
1548 ms
1085 ms
www.thalys.com
1517 ms
line.png
805 ms
dot.png
807 ms
dot_eurostar.png
814 ms
plane.png
858 ms
182bbf8a0fb4.js
65 ms
map_trace_element_base.png
874 ms
map_trace_element_neige_inactif.png
808 ms
map_trace_element_soleil_inactif.png
802 ms
map_trace_element_londres.png
803 ms
map_trace_element_kolnairport.png
857 ms
collect
57 ms
map_trace_element_roissy.png
863 ms
pixel
33 ms
event
356 ms
ga-audiences
54 ms
map_trace_element_maastricht.png
811 ms
map_trace_element_nlddh.png
811 ms
bullet-inactive.png
795 ms
acolade-gauche.png
855 ms
capture-apps-4.6.0.js
7 ms
airport.png
855 ms
bullet.png
844 ms
iframeStorage.html
131 ms
acolade-top.png
808 ms
new_offers.png
812 ms
iframeStorage.js
6 ms
green_flag.png
696 ms
red_flag.png
685 ms
bg-box-info.png
646 ms
bkg-calculer.jpg
645 ms
hit.xiti
394 ms
bkg-reserver.jpg
610 ms
train.jpg
583 ms
voiture.jpg
597 ms
avion.jpg
577 ms
responsable.jpg
567 ms
appsmanagerinit
229 ms
bg_bottom_ombre.png
562 ms
footer_print.png
538 ms
logo_thalys_footer.png
526 ms
railteam.png
534 ms
sprite.png
633 ms
spacer.gif
536 ms
map_trace_element_neige_actif.png
523 ms
map_trace_element_soleil_actif.png
521 ms
bg-btn-flag.jpg
526 ms
nlama.jpg
627 ms
bg-box-info-top.png
566 ms
print.css
85 ms
coll.aspx
567 ms
btn_desktop_dutch_right_big.png
62 ms
dis.aspx
389 ms
thalys.nl 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
[role]s do not have all required [aria-*] attributes
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
Image elements do not have [alt] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
thalys.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
thalys.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
NL
NL
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thalys.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Thalys.nl 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.
thalys.nl
Open Graph description is not detected on the main page of Thalys. 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: