Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

api.railwayapi.com

API For Indian Railways | RailwayAPI

Page Load Speed

4.2 sec in total

First Response

533 ms

Resources Loaded

3.5 sec

Page Rendered

195 ms

api.railwayapi.com screenshot

About Website

Welcome to api.railwayapi.com homepage info - get ready to check API RailwayAPI best content for India right away, or after learning these important things about api.railwayapi.com

Fast and Advanced API for Indian Railways. Query PNR status, Seat availability, Trains between stations and much more. Get simple JSON structured responses.

Visit api.railwayapi.com

Key Findings

We analyzed Api.railwayapi.com page load time and found that the first response time was 533 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

api.railwayapi.com performance score

0

Network Requests Diagram

api.railwayapi.com

533 ms

www.railwayapi.com

505 ms

railwayapi.com

644 ms

WeDGSywrrsGe5ElqEnC6BQB6h_M.js

22 ms

bootstrap.min.css

62 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Api.railwayapi.com, 59% (17 requests) were made to Railwayapi.com and 14% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Railwayapi.com.

Page Optimization Overview & Recommendations

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

Content Size

672.1 kB

After Optimization

348.7 kB

In fact, the total size of Api.railwayapi.com main page is 672.1 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. 30% of websites need less resources to load. Javascripts take 194.2 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 104.8 kB

  • Original 154.9 kB
  • After minification 154.8 kB
  • After compression 50.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. 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 104.8 kB or 68% of the original size.

Image Optimization

-1%

Potential reduce by 1.3 kB

  • Original 171.3 kB
  • After minification 170.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. API RailwayAPI images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 92.8 kB

  • Original 194.2 kB
  • After minification 194.2 kB
  • After compression 101.3 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 92.8 kB or 48% of the original size.

CSS Optimization

-82%

Potential reduce by 124.5 kB

  • Original 151.8 kB
  • After minification 151.6 kB
  • After compression 27.3 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. Api.railwayapi.com needs all CSS files to be minified and compressed as it can save up to 124.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (45%)

Requests Now

20

After Optimization

11

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

SEO Factors

api.railwayapi.com SEO score

0

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 Api.railwayapi.com 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 Api.railwayapi.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

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