Tools & Wizards About Us
railtime.be screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

railtime.be

SNCB official website - Buy your train tickets online

Page Load Speed

3.7 sec in total

First Response

277 ms

Resources Loaded

2.8 sec

Page Rendered

670 ms

railtime.be screenshot

About Website

Welcome to railtime.be homepage info - get ready to check Railtime best content for Belgium right away, or after learning these important things about railtime.be

Find your tickets for rail travel in Belgium with our planning tool. Book it online and avoid queueing in stations. It’s easy, fast and secure!

Visit railtime.be

Key Findings

We analyzed Railtime.be page load time and found that the first response time was 277 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

railtime.be performance score

0

Network Requests Diagram

www.belgianrail.be

277 ms

Splash.aspx

350 ms

245 ms

444 ms

860 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that all of those requests were addressed to Railtime.be and no external sources were called. The less responsive or slowest element that took the longest time to load (974 ms) relates to the external source Belgianrail.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 583.8 kB (48%)

Content Size

1.2 MB

After Optimization

625.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Railtime.be main page is 1.2 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. Only 5% of websites need less resources to load. Javascripts take 486.0 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 9.0 kB

  • Original 12.5 kB
  • After minification 9.6 kB
  • After compression 3.5 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 2.9 kB, which is 23% 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 9.0 kB or 72% of the original size.

Image Optimization

-2%

Potential reduce by 8.7 kB

  • Original 448.2 kB
  • After minification 439.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. Railtime images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 342.8 kB

  • Original 486.0 kB
  • After minification 486.0 kB
  • After compression 143.2 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 342.8 kB or 71% of the original size.

CSS Optimization

-85%

Potential reduce by 223.4 kB

  • Original 262.8 kB
  • After minification 244.5 kB
  • After compression 39.4 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. Railtime.be needs all CSS files to be minified and compressed as it can save up to 223.4 kB or 85% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

9

After Optimization

9

  • Images
  • JavaScript
  • CSS

The browser has sent 9 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Railtime. According to our analytics all requests are already optimized.

Network Requests Diagram

www.belgianrail.be

www.belgianrail.be

277 ms

Splash.aspx

Splash.aspx

350 ms

245 ms

444 ms

860 ms

244 ms

splash.ashx

splash.ashx

974 ms

splash-mask.png

splash-mask.png

410 ms

sprite-logos.png

sprite-logos.png

408 ms

sprite_splash_b.png

sprite_splash_b.png

451 ms

sprite_splash_c.png

sprite_splash_c.png

331 ms

SEO Factors

railtime.be SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Railtime.be can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Railtime.be 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

railtime.be

Open Graph description is not detected on the main page of Railtime. 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: