Tools & Wizards About Us
rail.ninja screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    81% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

rail.ninja

Book High-Speed Trains Around the World with Rail.Ninja

Page Load Speed

1.4 sec in total

First Response

55 ms

Resources Loaded

1.1 sec

Page Rendered

246 ms

rail.ninja screenshot

About Website

Visit rail.ninja now to see the best up-to-date Rail content for United States and also check out these interesting facts you probably never knew about rail.ninja

Find and book your high-speed train tickets online with Rail.Ninja! Purchase e-tickets with preferred payment methods for trains worldwide like Vienna Budapest train tickets, Vienna Prague trains, Lis...

Visit rail.ninja

Key Findings

We analyzed Rail.ninja page load time and found that the first response time was 55 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

rail.ninja performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

68/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value8.9 s

35/100

10%

Network Requests Diagram

rail.ninja

55 ms

rail.ninja

453 ms

css_xqUpFXiJTKBLpIQMMNXsaWEiGSpPKvkTbLhliLk-2RM.css

34 ms

css_E0XcDZHbHqsgLzwAPHRXUWJHZyX5v9r_Lih3nBZxBb0.css

50 ms

logo.svg

39 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 92% of them (22 requests) were addressed to the original Rail.ninja, 4% (1 request) were made to Static.cloudflareinsights.com and 4% (1 request) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (506 ms) belongs to the original domain Rail.ninja.

Page Optimization Overview & Recommendations

Page size can be reduced by 731.5 kB (77%)

Content Size

950.5 kB

After Optimization

219.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rail.ninja main page is 950.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. HTML takes 798.1 kB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 731.5 kB

  • Original 798.1 kB
  • After minification 793.2 kB
  • After compression 66.6 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 731.5 kB or 92% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 45.5 kB
  • After minification 45.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. Rail images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 5.9 kB
  • After minification 5.9 kB
  • After compression 5.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 101.0 kB
  • After minification 101.0 kB
  • After compression 101.0 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. Rail.ninja has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

20

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rail.ninja

rail.ninja

55 ms

rail.ninja

rail.ninja

453 ms

css_xqUpFXiJTKBLpIQMMNXsaWEiGSpPKvkTbLhliLk-2RM.css

css_xqUpFXiJTKBLpIQMMNXsaWEiGSpPKvkTbLhliLk-2RM.css

34 ms

css_E0XcDZHbHqsgLzwAPHRXUWJHZyX5v9r_Lih3nBZxBb0.css

css_E0XcDZHbHqsgLzwAPHRXUWJHZyX5v9r_Lih3nBZxBb0.css

50 ms

logo.svg

logo.svg

39 ms

right-arrow-orange.svg

right-arrow-orange.svg

55 ms

right-arrow.svg

right-arrow.svg

53 ms

rocket-loader.min.js

rocket-loader.min.js

19 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

75 ms

Arrow.svg

Arrow.svg

36 ms

setting-icon.svg

setting-icon.svg

180 ms

flags.svg

flags.svg

48 ms

RN_bg_banner_2.jpg

RN_bg_banner_2.jpg

42 ms

app-store-2.png

app-store-2.png

328 ms

google-play-2.png

google-play-2.png

184 ms

Lock.svg

Lock.svg

59 ms

rnqr.png

rnqr.png

407 ms

app_store-2.svg

app_store-2.svg

67 ms

google_play-2.svg

google_play-2.svg

80 ms

Arrow.svg

Arrow.svg

88 ms

railninja.png

railninja.png

506 ms

bicubik-regular.woff2

bicubik-regular.woff2

19 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

36 ms

modernizr.min.js

modernizr.min.js

23 ms

Accessibility Review

rail.ninja accessibility score

67

Accessibility Issues

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

Buttons do not have an accessible name

High

Form elements do not have associated labels

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Heading elements are not in a sequentially-descending order

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

ARIA IDs are not unique

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

rail.ninja best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

rail.ninja SEO score

100

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

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

rail.ninja

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