3.6 sec in total
272 ms
3 sec
335 ms
Click here to check amazing Rail content for India. Otherwise, check out these important facts you probably never knew about rail.in
Travel India by train. Here you find ticket prices, train schedules, travel routes and night train information.
Visit rail.inWe analyzed Rail.in page load time and found that the first response time was 272 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
rail.in performance score
name
value
score
weighting
Value1.0 s
100/100
10%
Value1.0 s
100/100
25%
Value3.6 s
87/100
10%
Value1,960 ms
8/100
30%
Value0.219
57/100
15%
Value4.1 s
86/100
10%
272 ms
25 ms
95 ms
190 ms
189 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 14% of them (12 requests) were addressed to the original Rail.in, 10% (9 requests) were made to Wego.com and 9% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (758 ms) belongs to the original domain Rail.in.
Page size can be reduced by 716.0 kB (41%)
1.8 MB
1.0 MB
In fact, the total size of Rail.in main page is 1.8 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 923.9 kB which makes up the majority of the site volume.
Potential reduce by 58.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 58.7 kB or 71% of the original size.
Potential reduce by 2.7 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.
Potential reduce by 612.6 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 612.6 kB or 66% of the original size.
Potential reduce by 42.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.
Number of requests can be reduced by 53 (65%)
81
28
The browser has sent 81 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 40 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
rail.in
272 ms
css
25 ms
output.css
95 ms
style.css
190 ms
comment-reply.min.js
189 ms
jquery.js
284 ms
jquery-ui-1.8.11.custom.min.js
193 ms
jquery.easing.1.3.js
194 ms
jquery.cycle.all.min.js
193 ms
jquery.slidemenu.js
282 ms
theme=wego
595 ms
addthis_widget.js
10 ms
bg_rail.jpg
758 ms
logo_rail.png
190 ms
Indian-Railways-300x215.png
380 ms
ajs.php
280 ms
ajs.php
366 ms
ajs.php
94 ms
ajs.php
135 ms
theme=wego
325 ms
V86VyqXbc09Sss3BPsMj16CWcynf_cDxXwCLxiixG1c.ttf
28 ms
show_ads.js
4 ms
ca-pub-8477364103489971.js
127 ms
zrt_lookup.html
139 ms
show_ads_impl.js
66 ms
piwik.js
305 ms
ads
232 ms
osd.js
21 ms
ads
245 ms
152-63b98df01e8931f5303f172d48f490a7-1405483463.css
30 ms
style-500x250.css
77 ms
152-fc11f74f6333d2a9a2211c99ea4c6d78-1354275456.js
115 ms
wgodstluzvvtcfdvzyvwvrsqyw.js
343 ms
wego.farmer.js
74 ms
0_yOXfyb1q.jpg
225 ms
a.gif
71 ms
bcs0
75 ms
creative_add_on.js
137 ms
creative_add_on.js
143 ms
bcs0
57 ms
0_yOXfyb1q.jpg
207 ms
ajs.php
108 ms
piwik.php
531 ms
powered_by.gif
30 ms
submit-medium.gif
29 ms
surly.js
43 ms
dvtp_src.js
32 ms
ajs.php
191 ms
ba.html
38 ms
dvtp_src_internal26.js
36 ms
4.gif
83 ms
2532.js
71 ms
t2tv7.html
132 ms
visit.js
157 ms
icon-calendar.gif
89 ms
300lo.json
72 ms
all.js&version=v2.0
265 ms
plusone.js
75 ms
pinit00.png
21 ms
widgets.js
20 ms
counter.5524cceca805eb4b9b2b.js
19 ms
sh.8e5f85691f9aaa082472a194.html
57 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
60 ms
shares.json
43 ms
cb=gapi.loaded_0
43 ms
cb=gapi.loaded_1
107 ms
fastbutton
162 ms
avs5639.js
44 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.de.html
30 ms
event.jpg
59 ms
postmessageRelay
63 ms
box_19_top-right.png
28 ms
ci.png
27 ms
cb=gapi.loaded_0
14 ms
cb=gapi.loaded_1
13 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
70 ms
3193398744-postmessagerelay.js
54 ms
rpc:shindig_random.js
84 ms
148 ms
xd_arbiter.php
68 ms
xd_arbiter.php
133 ms
jot
108 ms
cb=gapi.loaded_0
25 ms
ping
58 ms
like.php
123 ms
qeKvIRsJabD.js
141 ms
LVx-xkvaJ0b.png
155 ms
rail.in accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
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.
rail.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Issues were logged in the Issues panel in Chrome Devtools
rail.in SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 doesn't use legible font sizes
EN
DE
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 does not match the claimed German 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.
rail.in
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: