Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 48

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

pnrstatuscheck.in

PNR Status : Check PNR Status | Indian Railway Passenger reservation Enquiry | pnr enquiry | railway pnr status | Online PNR Status | railway PNR |sta...

Page Load Speed

12.9 sec in total

First Response

86 ms

Resources Loaded

12.1 sec

Page Rendered

759 ms

pnrstatuscheck.in screenshot

About Website

Visit pnrstatuscheck.in now to see the best up-to-date PNR Status Check content for India and also check out these interesting facts you probably never knew about pnrstatuscheck.in

Online PNR status check from South Central Railways(Indian railways) for complete rail pnr status.IRCTC pnr status can be checked here to get the status change alerts and predict your ticket confirmat...

Visit pnrstatuscheck.in

Key Findings

We analyzed Pnrstatuscheck.in page load time and found that the first response time was 86 ms and then it took 12.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

pnrstatuscheck.in performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value11,840 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value19.3 s

2/100

10%

Network Requests Diagram

pnrstatuscheck.in

86 ms

www.pnrstatuscheck.in

234 ms

style.css

258 ms

Feedback.css

115 ms

jquery-1.4.2.js

301 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 22% of them (24 requests) were addressed to the original Pnrstatuscheck.in, 23% (25 requests) were made to Static.xx.fbcdn.net and 19% (20 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (10.8 sec) relates to the external source Facebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 295.7 kB (50%)

Content Size

597.4 kB

After Optimization

301.6 kB

In fact, the total size of Pnrstatuscheck.in main page is 597.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 221.1 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 50.9 kB

  • Original 65.1 kB
  • After minification 54.3 kB
  • After compression 14.2 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. This page needs HTML code to be minified as it can gain 10.8 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 50.9 kB or 78% of the original size.

Image Optimization

-6%

Potential reduce by 13.8 kB

  • Original 221.1 kB
  • After minification 207.3 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. PNR Status Check images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 148.4 kB

  • Original 214.2 kB
  • After minification 146.3 kB
  • After compression 65.9 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 148.4 kB or 69% of the original size.

CSS Optimization

-85%

Potential reduce by 82.7 kB

  • Original 96.9 kB
  • After minification 79.0 kB
  • After compression 14.2 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. Pnrstatuscheck.in needs all CSS files to be minified and compressed as it can save up to 82.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (46%)

Requests Now

105

After Optimization

57

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

Accessibility Review

pnrstatuscheck.in accessibility score

48

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

Page has valid source maps

SEO Factors

pnrstatuscheck.in SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pnrstatuscheck.in can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Pnrstatuscheck.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

Open Graph data is detected on the main page of PNR Status Check. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: