Tools & Wizards About Us
rail.in screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    80% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

rail.in

Indian by Train - Railway Information and Tickets

Page Load Speed

4.8 sec in total

First Response

1.4 sec

Resources Loaded

3 sec

Page Rendered

443 ms

rail.in screenshot

About Website

Click here to check amazing Rail content for India. Otherwise, check out these important facts you probably never knew about rail.in

Rail travel information for India. Find train schedules and buy your tickets. Get help from the experts to enjoy your journey in India.

Visit rail.in

Key Findings

We analyzed Rail.in page load time and found that the first response time was 1.4 sec 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

rail.in performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

40/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.2 s

74/100

10%

Network Requests Diagram

rail.in

1350 ms

rail.in

65 ms

main.min.css

39 ms

css

31 ms

astra-addon-65d2bf6391f1d7-70924946.css

44 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 88% of them (30 requests) were addressed to the original Rail.in, 9% (3 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Rail.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 801.7 kB (43%)

Content Size

1.9 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rail.in main page is 1.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. 20% of websites need less resources to load. Javascripts take 952.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 117.8 kB

  • Original 141.7 kB
  • After minification 139.6 kB
  • After compression 23.9 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 117.8 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 2.7 kB

  • Original 707.7 kB
  • After minification 705.0 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

-67%

Potential reduce by 639.2 kB

  • Original 952.0 kB
  • After minification 933.1 kB
  • After compression 312.8 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 639.2 kB or 67% of the original size.

CSS Optimization

-82%

Potential reduce by 42.0 kB

  • Original 51.0 kB
  • After minification 42.2 kB
  • After compression 9.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.in needs all CSS files to be minified and compressed as it can save up to 42.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (86%)

Requests Now

28

After Optimization

4

  • Images
  • JavaScript
  • CSS

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 17 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

rail.in

rail.in

1350 ms

rail.in

rail.in

65 ms

main.min.css

main.min.css

39 ms

css

css

31 ms

astra-addon-65d2bf6391f1d7-70924946.css

astra-addon-65d2bf6391f1d7-70924946.css

44 ms

default.css

default.css

77 ms

frontend-lite.min.css

frontend-lite.min.css

49 ms

swiper.min.css

swiper.min.css

53 ms

post-26.css

post-26.css

49 ms

frontend-lite.min.css

frontend-lite.min.css

71 ms

post-36.css

post-36.css

78 ms

india-railway.webp

india-railway.webp

87 ms

frontend.min.js

frontend.min.js

82 ms

astra-addon-65d2bf63922767-13405383.js

astra-addon-65d2bf63922767-13405383.js

1260 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

114 ms

webpack.runtime.min.js

webpack.runtime.min.js

103 ms

jquery.min.js

jquery.min.js

122 ms

jquery-migrate.min.js

jquery-migrate.min.js

116 ms

frontend-modules.min.js

frontend-modules.min.js

123 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

140 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

138 ms

wp-polyfill.min.js

wp-polyfill.min.js

157 ms

hooks.min.js

hooks.min.js

165 ms

i18n.min.js

i18n.min.js

154 ms

frontend.min.js

frontend.min.js

173 ms

waypoints.min.js

waypoints.min.js

169 ms

core.min.js

core.min.js

186 ms

frontend.min.js

frontend.min.js

192 ms

elements-handlers.min.js

elements-handlers.min.js

207 ms

matomo.js

matomo.js

209 ms

qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaE0lMZbLXGimS.woff

qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaE0lMZbLXGimS.woff

16 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-2Y-FV0UzdYPFkaVN.woff

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-2Y-FV0UzdYPFkaVN.woff

5 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0UzdYPFkaVN.woff

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0UzdYPFkaVN.woff

11 ms

matomo.php

matomo.php

1260 ms

Accessibility Review

rail.in accessibility score

97

Accessibility Issues

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.

Best Practices

rail.in best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

rail.in 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.in 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.in 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.in

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: