www.indianrail.gov.in/enquiry/StaticPages/StaticEnquiry.jsp?StaticPage=index.html speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 12:48 UTC. Grade D (66/100), with the screenshots, the timings and the fixes that matter.

https://www.indianrail.gov.in/enquiry/StaticPages/StaticEnquiry.jsp?StaticPage=index.html

20 October 2026 at 12:48 UTC · Free test · report pt_ca632f70ef0a

Re-test this page Test your own site

Grade

66/100

Performance64/100

Structure70/100

12 audit(s) passed, 4 need work

First byte (TTFB)1.34 smeasured from this server

Fully loaded2.83 sfirst byte + slowest asset

Requests12document + assets

Page weight311.7 KBcompressed transfer

HTML document5.4 KBgzip

ProtocolHTTP/2server not sent

Third-party196.9 KBother hosts

Where the first byte went

DNS lookup 46 ms 3%
TCP connect 316 ms 24%
Server wait 979 ms 73%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First byteslower than 93% of 4,999 pages tested here1.34 s against a median of 448 ms

Page weightlighter than 71% of 4,999 pages tested here311.7 KB against a median of 650.5 KB

Fully loadedslower than 80% of 4,999 pages tested here2.83 s against a median of 1.84 s

Requestssends fewer requests than 86% of 4,999 pages tested here12 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

The first byte took 1.34 s. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
The page transfers 311.7 KB over 12 request(s), which is lean. Javascript files are 63% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
The HTML itself arrives gzip-compressed.
It runs over HTTP/2, so the assets share a connection instead of opening one each.
63% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element took 3.32 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
Layout shift is 0.320 (good is under 0.1): something without a reserved size is loading late - an image, an ad, or a font swap.
The main thread was blocked for 353 ms, so taps and scrolling wait while scripts run.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Mobile screenshot of www.indianrail.gov.in — **Mobile** 390 × 844 · 232.0 KB · page is 1531 px tall

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint3.32 sgood is under 2.5 s

Cumulative layout shift0.320under 0.1 is stable

Total blocking time353 mslong tasks during load

First contentful paint2.23 sfirst content on screen

Browser page weight4.11 MB140 request(s), scripts included

Failed requests5blocked or unreachable

Largest contentful paint3.32 s

Needs improvementgood under 2.5 s, poor over 4 s

Cumulative layout shift0.320

Poorgood under 0.1, poor over 0.25

Total blocking time353 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 2 requests

196.9 KB 63%

Html 9 requests

109.4 KB 35%

Transfer size, compressed as sent. 12 request(s) in total, 311.7 KB across all of them.

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1340 ms. Of that, 979 ms was the server thinking and 362 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Compress text responses

high impact

10 text response(s) of 10 KB or more are sent uncompressed, and the document itself is not compressed. That is 240.6 KB of compressible text.

Fix: Turn on brotli (preferred) or gzip for text/css, javascript and text/html in the web server. This is the cheapest win available on almost any site.

Render-blocking resources

high impact

7 render-blocking resource(s) in the document head (5 script(s), 2 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Avoid extra redirects

medium impact

2 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.