12.9 sec in total
86 ms
12.1 sec
759 ms
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.inWe 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.
pnrstatuscheck.in performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value5.9 s
14/100
25%
Value6.8 s
35/100
10%
Value11,840 ms
0/100
30%
Value0.024
100/100
15%
Value19.3 s
2/100
10%
86 ms
234 ms
258 ms
115 ms
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 size can be reduced by 295.7 kB (50%)
597.4 kB
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.
Potential reduce by 50.9 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.
Potential reduce by 13.8 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.
Potential reduce by 148.4 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.
Potential reduce by 82.7 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.
Number of requests can be reduced by 48 (46%)
105
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.
pnrstatuscheck.in
86 ms
www.pnrstatuscheck.in
234 ms
style.css
258 ms
Feedback.css
115 ms
jquery-1.4.2.js
301 ms
jquery.cookie.js
116 ms
Feedback.js
115 ms
show_ads.js
5 ms
sitebg.jpg
58 ms
trainIcon.png
275 ms
bookmark_add.png
274 ms
android_pnrstatus_app.png
275 ms
loading2.gif
275 ms
ajaxLoader-big.gif
278 ms
sample_ticket.png
280 ms
bookmark-delicious.gif
277 ms
bookmark-digg.gif
277 ms
bookmark-reddit.gif
278 ms
bookmark-technorati.gif
278 ms
bookmark-yahoo.gif
278 ms
facebook.png
280 ms
twitter-icon-large.png
280 ms
all.js
265 ms
ca-pub-9538283423653428.js
209 ms
zrt_lookup.html
192 ms
show_ads_impl.js
126 ms
like.php
302 ms
likebox.php
322 ms
270 ms
plusone.js
197 ms
feedbackback.jpg
132 ms
xd_arbiter.php
141 ms
xd_arbiter.php
209 ms
ads
10668 ms
start.png
117 ms
feedbackButton1.png
116 ms
ga.js
74 ms
osd.js
78 ms
comments.php
201 ms
comments.php
10450 ms
ads
10584 ms
like.php
187 ms
ads
10815 ms
likebox.php
10817 ms
__utm.gif
42 ms
qeKvIRsJabD.js
100 ms
LVx-xkvaJ0b.png
96 ms
cb=gapi.loaded_0
28 ms
cb=gapi.loaded_1
52 ms
fastbutton
119 ms
xd_arbiter.php
31 ms
postmessageRelay
10281 ms
kyEKgjk51ZE.css
22 ms
xgj7bXhJNEH.css
55 ms
q68gy-v_YMF.js
61 ms
FJmpeSpHpjS.js
53 ms
0wM5s1Khldu.js
54 ms
1bNoFZUdlYZ.js
42 ms
yBwS6rJyogl.css
35 ms
ZeuPykSxSED.css
10263 ms
LTv6ZK-5zxz.js
10335 ms
1FCa-btixu2.js
10304 ms
Oagsvfb4VWi.js
10304 ms
FyxLoiww5bU.js
10302 ms
HaMjR2eXz4B.js
10261 ms
WN2wSsLOuKy.js
10400 ms
Kt4tkgSRvHH.js
10327 ms
Q4A0UyjU8W2.js
10330 ms
cb=gapi.loaded_0
10306 ms
cb=gapi.loaded_1
10304 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
10610 ms
546559_276201272473631_1424690722_n.jpg
10673 ms
376120_169672303126529_1852155658_n.jpg
517 ms
11062711_802335983206515_6466321706144542523_n.jpg
529 ms
1929281_1569358423380862_6348285025870197965_n.jpg
530 ms
28167_126184434236012_1195166037_n.jpg
530 ms
1240657_220396111646717_9210926367814573796_n.jpg
530 ms
10414382_197714413935447_8444864237199719483_n.jpg
527 ms
10294428_1706924712859065_1804759049541591890_n.jpg
536 ms
12524039_151136601932413_6254441007182851080_n.jpg
542 ms
10553326_1541772596122669_4176083036771695001_n.jpg
534 ms
wL6VQj7Ab77.png
400 ms
s7jcwEQH7Sx.png
399 ms
3193398744-postmessagerelay.js
508 ms
rpc:shindig_random.js
396 ms
8581531730848267780
349 ms
abg.js
352 ms
m_js_controller.js
370 ms
googlelogo_color_112x36dp.png
335 ms
546559_276201272473631_1424690722_n.jpg
148 ms
12552980_997890763618123_231184112001985252_n.jpg
146 ms
1904149_1397519597218288_5193816823840829871_n.jpg
146 ms
10436691_10202422105899430_2546742906731672484_n.jpg
152 ms
12832471_427508007458679_6973620760783654427_n.jpg
151 ms
11224056_778139105630647_1225556059428276378_n.jpg
164 ms
1390750_198675790474017_79757017074313797_n.jpg
162 ms
376120_169672303126529_1852155658_n.jpg
168 ms
255584_134188549989636_8032284_n.jpg
167 ms
1450857_296523507168115_8277140076015446364_n.jpg
162 ms
fav.png
151 ms
odA9sNLrE86.jpg
128 ms
K00K-UgnsKu.png
116 ms
eR-qA8bp1RM.js
21 ms
I6-MnjEovm5.js
32 ms
pQrUxxo5oQp.js
22 ms
cb=gapi.loaded_0
40 ms
x_button_blue2.png
28 ms
s
15 ms
pnrstatuscheck.in accessibility score
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
[aria-*] attributes do not match their roles
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
Image elements do not have [alt] attributes
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
<html> element does not have a [lang] attribute
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.
pnrstatuscheck.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
pnrstatuscheck.in SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
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.
pnrstatuscheck.in
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: