Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

prnt.sc

Lightshot — screenshot tool for Mac & Win

Page Load Speed

88 ms in total

First Response

32 ms

Resources Loaded

56 ms

Page Rendered

0 ms

About Website

Welcome to prnt.sc homepage info - get ready to check Prnt best content for India right away, or after learning these important things about prnt.sc

Visit prnt.sc

Key Findings

We analyzed Prnt.sc page load time and found that the first response time was 32 ms and then it took 56 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. This domain responded with an error, which can significantly jeopardize Prnt.sc rating and web reputation

Performance Metrics

prnt.sc performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

66/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.474

18/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

prnt.sc

32 ms

v1

22 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that all of those requests were addressed to Prnt.sc and no external sources were called. The less responsive or slowest element that took the longest time to load (32 ms) belongs to the original domain Prnt.sc.

Page Optimization Overview & Recommendations

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

Content Size

532.8 kB

After Optimization

268.4 kB

In fact, the total size of Prnt.sc main page is 532.8 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. Only 5% of websites need less resources to load. Javascripts take 373.7 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 8.4 kB

  • Original 13.9 kB
  • After minification 13.9 kB
  • After compression 5.5 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 8.4 kB or 61% of the original size.

Image Optimization

-13%

Potential reduce by 11.2 kB

  • Original 87.8 kB
  • After minification 76.6 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, Prnt needs image optimization as it can save up to 11.2 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-53%

Potential reduce by 196.4 kB

  • Original 373.7 kB
  • After minification 372.6 kB
  • After compression 177.3 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 196.4 kB or 53% of the original size.

CSS Optimization

-84%

Potential reduce by 48.3 kB

  • Original 57.4 kB
  • After minification 57.4 kB
  • After compression 9.1 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. Prnt.sc needs all CSS files to be minified and compressed as it can save up to 48.3 kB or 84% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

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

Accessibility Review

prnt.sc accessibility score

75

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

prnt.sc 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

prnt.sc SEO score

54

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

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 Prnt.sc 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 Prnt.sc 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 description is not detected on the main page of Prnt. 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: