Tools & Wizards About Us
pnr-status.net screenshot

Report Summary

  • 90

    Performance

    Renders faster than
    91% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

pnr-status.net

Page Load Speed

638 ms in total

First Response

182 ms

Resources Loaded

455 ms

Page Rendered

1 ms

pnr-status.net screenshot

About Website

Click here to check amazing Pnr Status content. Otherwise, check out these important facts you probably never knew about pnr-status.net

Visit pnr-status.net

Key Findings

We analyzed Pnr-status.net page load time and found that the first response time was 182 ms and then it took 456 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

pnr-status.net performance score

90

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.9 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.9 s

100/100

25%

SI (Speed Index)

Value1.6 s

100/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.212

59/100

15%

TTI (Time to Interactive)

Value3.0 s

96/100

10%

Network Requests Diagram

pnr-status.net

182 ms

suspendedpage.cgi

108 ms

fwdssp.com

160 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that 67% of them (2 requests) were addressed to the original Pnr-status.net, 33% (1 request) were made to Fwdssp.com. The less responsive or slowest element that took the longest time to load (182 ms) belongs to the original domain Pnr-status.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 198 B (40%)

Content Size

489 B

After Optimization

291 B

  • HTML

In fact, the total size of Pnr-status.net main page is 489 B. This result falls within a big category (top 100 000) of medium weight web pages. Only a small number of websites need less resources to load. HTML takes 489 B which makes up the majority of the site volume.

HTML Optimization

-40%

Potential reduce by 198 B

  • Original 489 B
  • After minification 421 B
  • After compression 291 B

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 68 B, which is 14% 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 198 B or 40% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

  • AJAX

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pnr Status. According to our analytics all requests are already optimized.

Network Requests Diagram

pnr-status.net

pnr-status.net

182 ms

suspendedpage.cgi

suspendedpage.cgi

108 ms

fwdssp.com

fwdssp.com

160 ms

Accessibility Review

pnr-status.net accessibility score

63

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.

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

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.net best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

pnr-status.net SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pnr-status.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Pnr-status.net 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

pnr-status.net

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