Tools & Wizards About Us
viarail.com screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

viarail.com

VIA Rail Canada: Train travel in Canada

Page Load Speed

1.5 sec in total

First Response

47 ms

Resources Loaded

999 ms

Page Rendered

480 ms

viarail.com screenshot

About Website

Visit viarail.com now to see the best up-to-date VIA Rail content for Canada and also check out these interesting facts you probably never knew about viarail.com

Book now and discover all the benefits of travelling by train with VIA Rail. Take advantage of our best offers and enjoy a unique travel experience.

Visit viarail.com

Key Findings

We analyzed Viarail.com page load time and found that the first response time was 47 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

viarail.com performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value40.0 s

0/100

25%

SI (Speed Index)

Value15.5 s

0/100

10%

TBT (Total Blocking Time)

Value3,840 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.276

44/100

15%

TTI (Time to Interactive)

Value38.9 s

0/100

10%

Network Requests Diagram

viarail.com

47 ms

viarail.ca

79 ms

www.viarail.ca

112 ms

fr

41 ms

ajax-progress.module.css

29 ms

Our browser made a total of 134 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Viarail.com, 94% (126 requests) were made to Viarail.ca and 1% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (510 ms) relates to the external source Viarail.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (44%)

Content Size

4.3 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Viarail.com main page is 4.3 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. 65% of websites need less resources to load. Javascripts take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 277.6 kB

  • Original 320.8 kB
  • After minification 285.8 kB
  • After compression 43.1 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 34.9 kB, which is 11% 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 277.6 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 4.1 kB

  • Original 1.6 MB
  • After minification 1.6 MB

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. VIA Rail images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 1.6 MB

  • Original 2.3 MB
  • After minification 2.2 MB
  • After compression 679.0 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 1.6 MB or 70% of the original size.

CSS Optimization

-16%

Potential reduce by 25.9 kB

  • Original 164.6 kB
  • After minification 163.2 kB
  • After compression 138.7 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. Viarail.com needs all CSS files to be minified and compressed as it can save up to 25.9 kB or 16% of the original size.

Requests Breakdown

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

Requests Now

128

After Optimization

39

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

viarail.com

viarail.com

47 ms

viarail.ca

viarail.ca

79 ms

www.viarail.ca

www.viarail.ca

112 ms

fr

fr

41 ms

ajax-progress.module.css

ajax-progress.module.css

29 ms

align.module.css

align.module.css

44 ms

autocomplete-loading.module.css

autocomplete-loading.module.css

47 ms

fieldgroup.module.css

fieldgroup.module.css

47 ms

container-inline.module.css

container-inline.module.css

50 ms

clearfix.module.css

clearfix.module.css

48 ms

details.module.css

details.module.css

49 ms

hidden.module.css

hidden.module.css

59 ms

item-list.module.css

item-list.module.css

60 ms

js.module.css

js.module.css

61 ms

nowrap.module.css

nowrap.module.css

65 ms

position-container.module.css

position-container.module.css

65 ms

progress.module.css

progress.module.css

63 ms

reset-appearance.module.css

reset-appearance.module.css

73 ms

resize.module.css

resize.module.css

74 ms

sticky-header.module.css

sticky-header.module.css

75 ms

system-status-counter.css

system-status-counter.css

80 ms

system-status-report-counters.css

system-status-report-counters.css

80 ms

system-status-report-general-info.css

system-status-report-general-info.css

80 ms

tabledrag.module.css

tabledrag.module.css

87 ms

tablesort.module.css

tablesort.module.css

88 ms

tree-child.module.css

tree-child.module.css

89 ms

core.css

core.css

95 ms

datepicker.css

datepicker.css

94 ms

accordion.css

accordion.css

95 ms

menu.css

menu.css

100 ms

selectmenu.css

selectmenu.css

101 ms

autocomplete.css

autocomplete.css

103 ms

controlgroup.css

controlgroup.css

110 ms

checkboxradio.css

checkboxradio.css

109 ms

button.css

button.css

107 ms

draggable.css

draggable.css

115 ms

resizable.css

resizable.css

114 ms

dialog.css

dialog.css

116 ms

tabs.css

tabs.css

123 ms

crowdriff.js

crowdriff.js

70 ms

eu_cookie_compliance.bare.css

eu_cookie_compliance.bare.css

115 ms

theme.css

theme.css

106 ms

extlink.css

extlink.css

96 ms

bundle-page_paragraph.css

bundle-page_paragraph.css

99 ms

bundle-front.css

bundle-front.css

96 ms

bundle-base.css

bundle-base.css

135 ms

bundle-a_ltw_front_booking_engine.css

bundle-a_ltw_front_booking_engine.css

107 ms

bundle-a_ltw_front_travelling_today.css

bundle-a_ltw_front_travelling_today.css

108 ms

bundle-a_ltw_front_offers.css

bundle-a_ltw_front_offers.css

102 ms

jquery.min.js

jquery.min.js

183 ms

fr_Sf_jkaHFz7ECpeXrIxefJjoepd6PhnPLorWTa1qc-Mo.js

fr_Sf_jkaHFz7ECpeXrIxefJjoepd6PhnPLorWTa1qc-Mo.js

102 ms

drupalSettingsLoader.js

drupalSettingsLoader.js

100 ms

drupal.js

drupal.js

101 ms

drupal.init.js

drupal.init.js

103 ms

once.min.js

once.min.js

103 ms

version-min.js

version-min.js

106 ms

data-min.js

data-min.js

105 ms

disable-selection-min.js

disable-selection-min.js

160 ms

focusable-min.js

focusable-min.js

192 ms

form-min.js

form-min.js

193 ms

ie-min.js

ie-min.js

187 ms

keycode-min.js

keycode-min.js

187 ms

labels-min.js

labels-min.js

187 ms

plugin-min.js

plugin-min.js

183 ms

safe-active-element-min.js

safe-active-element-min.js

182 ms

safe-blur-min.js

safe-blur-min.js

183 ms

scroll-parent-min.js

scroll-parent-min.js

181 ms

tabbable-min.js

tabbable-min.js

179 ms

unique-id-min.js

unique-id-min.js

178 ms

datepicker-min.js

datepicker-min.js

174 ms

widget-min.js

widget-min.js

174 ms

accordion-min.js

accordion-min.js

174 ms

position-min.js

position-min.js

172 ms

menu-min.js

menu-min.js

172 ms

form-reset-mixin-min.js

form-reset-mixin-min.js

167 ms

selectmenu-min.js

selectmenu-min.js

164 ms

autocomplete-min.js

autocomplete-min.js

164 ms

controlgroup-min.js

controlgroup-min.js

213 ms

checkboxradio-min.js

checkboxradio-min.js

209 ms

button-min.js

button-min.js

204 ms

mouse-min.js

mouse-min.js

193 ms

draggable-min.js

draggable-min.js

190 ms

resizable-min.js

resizable-min.js

188 ms

dialog-min.js

dialog-min.js

190 ms

tabs-min.js

tabs-min.js

188 ms

locale.js

locale.js

187 ms

main.js

main.js

510 ms

extlink.js

extlink.js

185 ms

js.cookie.min.js

js.cookie.min.js

257 ms

eu_cookie_compliance.min.js

eu_cookie_compliance.min.js

254 ms

bundle-page_paragraph.js

bundle-page_paragraph.js

393 ms

ga.js

ga.js

182 ms

gtm.js

gtm.js

232 ms

icon-profil.svg

icon-profil.svg

162 ms

ontario_and_quebec.jpg

ontario_and_quebec.jpg

244 ms

the_great_western_way.jpg

the_great_western_way.jpg

201 ms

the_maritime_way.jpg

the_maritime_way.jpg

162 ms

the_adventure_routes.jpg

the_adventure_routes.jpg

200 ms

blog-logo-fr.svg

blog-logo-fr.svg

200 ms

ville-blog.svg

ville-blog.svg

200 ms

img-meilleurs-tarfis_0.jpg

img-meilleurs-tarfis_0.jpg

202 ms

promo_DT_fr.png

promo_DT_fr.png

202 ms

siege-spacieux.svg

siege-spacieux.svg

207 ms

nouveau.png

nouveau.png

208 ms

icon-tickets.svg

icon-tickets.svg

208 ms

bag-large.svg

bag-large.svg

227 ms

image_sieges.svg

image_sieges.svg

227 ms

icon-siege-spacieux.svg

icon-siege-spacieux.svg

228 ms

home-idea-toronto.jpg

home-idea-toronto.jpg

233 ms

home-idea-ottawa.jpg

home-idea-ottawa.jpg

233 ms

home-idea-montreal-3.jpg

home-idea-montreal-3.jpg

232 ms

icon_round_newsletter.svg

icon_round_newsletter.svg

233 ms

facebook.svg

facebook.svg

256 ms

twitter.svg

twitter.svg

202 ms

instagram.svg

instagram.svg

207 ms

youtube.svg

youtube.svg

208 ms

hero-home-desktop.jpg

hero-home-desktop.jpg

258 ms

hero-home-mobile2.jpg

hero-home-mobile2.jpg

234 ms

home-experience-1.jpg

home-experience-1.jpg

215 ms

home-experience-2-nf.jpeg

home-experience-2-nf.jpeg

214 ms

home-experience-2.jpg

home-experience-2.jpg

230 ms

home-tuile2-escapade.jpg

home-tuile2-escapade.jpg

250 ms

home-tuile3-business.jpg

home-tuile3-business.jpg

273 ms

home-tuile1-lowestfare.jpg

home-tuile1-lowestfare.jpg

218 ms

img-home-nouvelleflotte-2.jpg

img-home-nouvelleflotte-2.jpg

167 ms

annual-report-fr.jpg

annual-report-fr.jpg

231 ms

accessibility.jpg

accessibility.jpg

183 ms

home-newsletter-left.jpg

home-newsletter-left.jpg

184 ms

__utm.gif

__utm.gif

21 ms

home-newsletter-right.jpg

home-newsletter-right.jpg

159 ms

collect

collect

36 ms

ga-audiences

ga-audiences

92 ms

iframe_api

iframe_api

44 ms

style.print.css

style.print.css

18 ms

Accessibility Review

viarail.com accessibility score

79

Accessibility Issues

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

High

[role]s are not contained by their required parent element

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

viarail.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

viarail.com SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Viarail.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed French language. Our system also found out that Viarail.com 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

viarail.com

Open Graph data is detected on the main page of VIA Rail. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: