Report Summary

  • 75

    Performance

    Renders faster than
    84% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 78

    SEO

    Google-friendlier than
    40% of websites

Page Load Speed

1.9 sec in total

First Response

124 ms

Resources Loaded

1.4 sec

Page Rendered

393 ms

prynt.co screenshot

About Website

Click here to check amazing Prynt content for United States. Otherwise, check out these important facts you probably never knew about prynt.co

Print instant photos (and videos!) from your phone, anytime, anywhere. Just attach the Prynt Case to your phone, take a photo followed by a short video clip, and tap to print physical photos, instantl...

Visit prynt.co

Key Findings

We analyzed Prynt.co page load time and found that the first response time was 124 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

prynt.co performance score

75

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value8.9 s

35/100

10%

Network Requests Diagram

www.prynt.co

124 ms

analytics.js

93 ms

mixpanel-2-latest.min.js

160 ms

fonts.css

184 ms

mediaelementplayer.css

112 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Prynt.co, 27% (18 requests) were made to D1kk24s8modqpt.cloudfront.net and 12% (8 requests) were made to . The less responsive or slowest element that took the longest time to load (552 ms) relates to the external source Ssl.geoplugin.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 558.8 kB (20%)

Content Size

2.8 MB

After Optimization

2.3 MB

In fact, the total size of Prynt.co main page is 2.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 17.2 kB

  • Original 25.7 kB
  • After minification 24.2 kB
  • After compression 8.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 17.2 kB or 67% of the original size.

Image Optimization

-1%

Potential reduce by 23.4 kB

  • Original 1.8 MB
  • After minification 1.8 MB

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. Prynt images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 303.2 kB

  • Original 548.8 kB
  • After minification 548.8 kB
  • After compression 245.6 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 303.2 kB or 55% of the original size.

CSS Optimization

-53%

Potential reduce by 215.0 kB

  • Original 403.8 kB
  • After minification 397.4 kB
  • After compression 188.8 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. Prynt.co needs all CSS files to be minified and compressed as it can save up to 215.0 kB or 53% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (53%)

Requests Now

55

After Optimization

26

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

Accessibility Review

prynt.co accessibility score

65

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

prynt.co best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

prynt.co SEO score

78

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

High

Tap targets are not sized appropriately

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 Prynt.co 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 Prynt.co 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 Prynt. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: