Report Summary

  • 62

    Performance

    Renders faster than
    77% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

Page Load Speed

6.5 sec in total

First Response

802 ms

Resources Loaded

5.4 sec

Page Rendered

272 ms

pnr-status.info screenshot

About Website

Welcome to pnr-status.info homepage info - get ready to check Pnr Status best content for India right away, or after learning these important things about pnr-status.info

PNR Status is your source for Indian Railway Reservation Enquiry. Get IRCTC PNR status by Just entering your 10-digit Passenger Name Record number.

Visit pnr-status.info

Key Findings

We analyzed Pnr-status.info page load time and found that the first response time was 802 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

pnr-status.info performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

83/100

25%

SI (Speed Index)

Value2.5 s

97/100

10%

TBT (Total Blocking Time)

Value1,260 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.0 s

42/100

10%

Network Requests Diagram

pnr-status.info

802 ms

pnr-status.info

3901 ms

analytics.js

119 ms

adsbygoogle.js

66 ms

3605.js

138 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 8% of them (2 requests) were addressed to the original Pnr-status.info, 19% (5 requests) were made to Pagead2.googlesyndication.com and 19% (5 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Pnr-status.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 59.8 kB (28%)

Content Size

213.6 kB

After Optimization

153.8 kB

In fact, the total size of Pnr-status.info main page is 213.6 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 138.4 kB which makes up the majority of the site volume.

HTML Optimization

-45%

Potential reduce by 16.8 kB

  • Original 37.2 kB
  • After minification 37.0 kB
  • After compression 20.4 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 16.8 kB or 45% of the original size.

Image Optimization

-22%

Potential reduce by 8.3 kB

  • Original 38.0 kB
  • After minification 29.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. Obviously, Pnr Status needs image optimization as it can save up to 8.3 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-25%

Potential reduce by 34.7 kB

  • Original 138.4 kB
  • After minification 138.2 kB
  • After compression 103.7 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 34.7 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (64%)

Requests Now

22

After Optimization

8

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

Accessibility Review

pnr-status.info accessibility score

80

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

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

pnr-status.info best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

pnr-status.info SEO score

98

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

High

Tap targets are not sized appropriately

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 Pnr-status.info 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 Pnr-status.info 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 data is detected on the main page of Pnr Status. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: