Prnt.sc Lightshot — screenshot tool for Mac & Win
prnt.sc Mobile Performance
33/100
These metrics represent real-world Chrome users experience viewing prnt.sc on mobile devices. Reports are focused on loading performance and other critical factors that most affect user experience. Follow our guide to track, optimize, and improve the quality of your web pages.
User Loading Experience
First Contentful Paint
Largest Contentful Paint
Cumulative Layout Shift
First Input Delay
Metrics
Total Blocking Time4/100 1,650 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Time to Interactive8/100 14.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Cumulative Layout Shift18/100 0.482
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Speed Index36/100 6.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Largest Contentful Paint45/100 4.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
First Contentful Paint89/100 2.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Should Fix (16)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Remove unused JavaScript
Potential savings of 280 KiB
1,350 ms
Eliminate render-blocking resources
Potential savings of 1,110 ms
1,108 ms
Serve images in next-gen formats
Potential savings of 47 KiB
120 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Does not use passive listeners to improve scrolling performance
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,920 ms
Ensure text remains visible during webfont load
Avoid `document.write()`
Minimize main-thread work
10.4 s
Reduce JavaScript execution time
6.5 s
Serve static assets with an efficient cache policy
51 resources found
User Timing marks and measures
8 user timings
Avoid long main-thread tasks
20 long tasks found
Avoid chaining critical requests
5 chains found
Avoid large layout shifts
5 elements found
Largest Contentful Paint element
1 element found
Keep request counts low and transfer sizes small
170 requests • 1,558 KiB
Passed Audits (14)
Avoids an excessive DOM size
418 elements
Properly size images
Avoids enormous network payloads
Total size was 1,558 KiB
Remove unused CSS
Initial server response time was short
Root document took 420 ms
Use video formats for animated content
Minify CSS
Enable text compression
Efficiently encode images
Preload key requests
Preconnect to required origins
Avoid multiple page redirects
Potential savings of 630 ms
Defer offscreen images
Potential savings of 10 KiB
Minify JavaScript
prnt.sc Mobile SEO
54/100
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more. Run these additional validators on your site to check additional SEO best practices.
Should Fix (6)
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
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.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Document doesn't use legible font sizes
Tap targets are not sized appropriately
Passed Audits (7)
Document has a valid `hreflang`
Document avoids plugins
Page has successful HTTP status code
Links have descriptive text
robots.txt is valid
Page isn’t blocked from indexing
Document has a `<title>` element
prnt.sc Mobile Best Practices
69/100
These checks highlight opportunities to improve the overall code health of prnt.sc mobile page. Current recommendations will help to make your page fast and secure, to create a good user experience and to avoid deprecated technologies.
Should Fix (4)
User Experience
Serves images with low resolution
Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities
6 vulnerabilities detected
Does not use HTTPS
1 insecure request found
Links to cross-origin destinations are unsafe
Passed Audits (10)
Avoids requesting the notification permission on page load
No browser errors logged to the console
Displays images with correct aspect ratio
Properly defines charset
Avoids Application Cache
Avoids deprecated APIs
Avoids requesting the geolocation permission on page load
Allows users to paste into password fields
Detected JavaScript libraries
Page has the HTML doctype
prnt.sc Mobile Progressive Web App
18/100
These checks validate the aspects of a Progressive Web App. Learn more. These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Should Fix (11)
PWA Optimized
Manifest doesn't have a maskable icon
Does not set a theme color for the address bar.
Content is not sized correctly for the viewport
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Does not provide a valid `apple-touch-icon`
Is not configured for a custom splash screen
Installable
Does not register a service worker that controls page and `start_url`
Does not use HTTPS
1 insecure request found
Fast and reliable
Current page does not respond with a 200 when offline
Page load is not fast enough on mobile networks
Interactive at 14.8 s
`start_url` does not respond with a 200 when offline
Passed Audits (3)
Redirects HTTP traffic to HTTPS
Web app manifest meets the installability requirements
Contains some content when JavaScript is not available
prnt.sc Mobile Accessibility
81/100
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged. These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Should Fix (3)
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.
`<frame>` or `<iframe>` elements do not have a title
Links do not have a discernible name
Image elements do not have `[alt]` attributes
Passed Audits (14)
`<html>` element has a `[lang]` attribute
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
`[aria-hidden="true"]` elements do not contain focusable descendents
`[aria-*]` attributes are valid and not misspelled
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
Background and foreground colors have a sufficient contrast ratio
Heading elements appear in a sequentially-descending order
`<html>` element has a valid value for its `[lang]` attribute
`[aria-*]` attributes match their roles
The page contains a heading, skip link, or landmark region
`[aria-hidden="true"]` is not present on the document `<body>`
`[aria-*]` attributes have valid values
Document has a `<title>` element
`[id]` attributes on active, focusable elements are unique
Mobile Usability
68/100
These checks validate how easily a visitor can use prnt.sc on a mobile device. Test results include a list of any mobile usability problems. Mobile usability problems are issues that can affect a user that visits the page on a mobile (small screen) device, including small font sizes (which are hard to read on a small screen).
Should Fix (3)
Use legible font sizes
Configure the viewport
Size tap targets appropriately
Passed Audits (2)
Avoid plugins
Size content to viewport
Mobile Speed
67/100
These checks analyze the performance of prnt.sc on mobile devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (5)
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Leverage browser caching
Optimize images
Reduce server response time
Enable compression
Passed Audits (5)
Avoid landing page redirects
Minify CSS
Minify HTML
Minify JavaScript
Prioritize visible content
www.prnt.com
www.prnt.net
www.prnt.org
www.prnt.info
www.prnt.biz
www.prnt.us
www.prnt.mobi
www.rnt.sc
www.prnt.sc
www.ornt.sc
www.oprnt.sc
www.lrnt.sc
www.plrnt.sc
www.lprnt.sc
www.pnt.sc
www.pent.sc
www.prent.sc
www.pernt.sc
www.pdnt.sc
www.prdnt.sc
www.pdrnt.sc
www.pfnt.sc
www.prfnt.sc
www.pfrnt.sc
www.ptnt.sc
www.prtnt.sc
www.ptrnt.sc
www.prt.sc
www.prbt.sc
www.prnbt.sc
www.prbnt.sc
www.prht.sc
www.prnht.sc
www.prhnt.sc
www.prjt.sc
www.prnjt.sc
www.prjnt.sc
www.prmt.sc
www.prnmt.sc
www.prmnt.sc
www.prn.sc
www.prnr.sc
www.prntr.sc
www.prnrt.sc
www.prnf.sc
www.prntf.sc
www.prnft.sc
www.prng.sc
www.prntg.sc
www.prngt.sc
www.prny.sc
www.prnty.sc
www.prnyt.sc
www.prnt.net
www.prnt.org
www.prnt.info
www.prnt.biz
www.prnt.us
www.prnt.mobi
www.rnt.sc
www.prnt.sc
www.ornt.sc
www.oprnt.sc
www.lrnt.sc
www.plrnt.sc
www.lprnt.sc
www.pnt.sc
www.pent.sc
www.prent.sc
www.pernt.sc
www.pdnt.sc
www.prdnt.sc
www.pdrnt.sc
www.pfnt.sc
www.prfnt.sc
www.pfrnt.sc
www.ptnt.sc
www.prtnt.sc
www.ptrnt.sc
www.prt.sc
www.prbt.sc
www.prnbt.sc
www.prbnt.sc
www.prht.sc
www.prnht.sc
www.prhnt.sc
www.prjt.sc
www.prnjt.sc
www.prjnt.sc
www.prmt.sc
www.prnmt.sc
www.prmnt.sc
www.prn.sc
www.prnr.sc
www.prntr.sc
www.prnrt.sc
www.prnf.sc
www.prntf.sc
www.prnft.sc
www.prng.sc
www.prntg.sc
www.prngt.sc
www.prny.sc
www.prnty.sc
www.prnyt.sc