1.9 sec in total
124 ms
1.4 sec
393 ms
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.coWe 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.
prynt.co performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value2.5 s
90/100
25%
Value3.1 s
93/100
10%
Value490 ms
59/100
30%
Value0.002
100/100
15%
Value8.9 s
35/100
10%
124 ms
93 ms
160 ms
184 ms
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 size can be reduced by 558.8 kB (20%)
2.8 MB
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.
Potential reduce by 17.2 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.
Potential reduce by 23.4 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. Prynt images are well optimized though.
Potential reduce by 303.2 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.
Potential reduce by 215.0 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.
Number of requests can be reduced by 29 (53%)
55
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.
www.prynt.co
124 ms
analytics.js
93 ms
mixpanel-2-latest.min.js
160 ms
fonts.css
184 ms
mediaelementplayer.css
112 ms
manifest-2e7956db12894cb549d8bb5509a662b7.css
121 ms
jquery.min.js
141 ms
2033150112.js
350 ms
javascript.gp
552 ms
conversion_async.js
157 ms
jquery.validate.min.js
217 ms
155 ms
mediaelement-and-player.min.js
149 ms
lib-a8957d784339f6166a741dda5e55c819.js
139 ms
manifest-55aea02a4c64980c77d4dd6011c7423c.js
139 ms
i.js
154 ms
d0f75a5c89c5c3c289401eaa67dfa7ac3fbdec4d.1.js
154 ms
pix.js
41 ms
collect
93 ms
e
53 ms
55 ms
50 ms
40342EE52876D5FA0.css
57 ms
ga-audiences
46 ms
event
44 ms
fbevents.js
144 ms
usersync
150 ms
1
205 ms
rtset
199 ms
rum
214 ms
match
147 ms
header_logo-3ac26a94a8ba80d83fe02f5744ec83a9.png
111 ms
loader-2490add2901a299af3021615d4766780.gif
96 ms
home_intro-66cb74df4b2d9dfc5459d8a8b16a71f3.jpg
119 ms
home_plug-46671def9be2b9948deb155313e6dd7a.jpg
152 ms
home_share-f44e307bc916eb50f756e58b33d72b5b.jpg
185 ms
home_share_phone-9b3278f088928f8180152873f2286470.png
130 ms
home_ink-ba5c4d8b354018cb23b0735725f636a0.jpg
152 ms
home_phone_bg-46d8a7305170cb9d08f9111f4f2d6390.png
119 ms
home_phone_img-b7ff6d86989e212ef2e0ca45aec1cbc0.png
149 ms
home_more-134c4ac50586274b36d6b41c7b4824aa.png
134 ms
footer_temp-85f063f1178ece03af7c73f43b110b41.png
160 ms
footer_logo-de109e61e4030815afe03e98529dc402.png
142 ms
footer_rs-e80cec42a0b7938c1323b23444dfdd04.png
151 ms
footer_submit-041d2447cdbacec35fd2a1dec68055d7.png
152 ms
products.json
316 ms
home_share_thumb-44db384a8bd37b679acd19491cc6c653.png
131 ms
f11311783af4464c9f0854e0f82e3b2d.png
174 ms
C8wePjb6X8De76QVY=
8 ms
w+PBbKX4DMGVBZg==
8 ms
Fp+JB6JgU3Jz9YZNfhyngIcbFyU5g76RPJOx+zsEi3ueCO9l3vAaSlay4PO2s9JVshzZuCiPH5MelzI+v+F5g8fH30rxG63GQUY=
7 ms
lbK33zHQTo=
7 ms
EyTM4mfZJDHj3i5t6JCJezP4jPxQBSsS26uXrPJj+MU8HDjrCRn0DeSZzJ2f4tgcccT4b3MG15DyUoWfN52VrpKliMbF+XxY9LDUsbnNzxv8PjwWyl+AzBlQWY=
6 ms
f8LzB4+NvpfwN7vpBVg==
5 ms
4XmDx8ffSvEbrcZBRg==
5 ms
zhtdQsZIFnze9la6W1cTGxUXykPS4lPH5Dc8bPDn+VsrffMdBOg==
6 ms
8a71cc87295248d78e1a2e830ffda15d.png
260 ms
10a5c6999b2b4d07a0c2fcdbe9d26c7d.png
259 ms
channel.html
61 ms
120 ms
tap.php
43 ms
20 ms
rum
47 ms
nr-885.min.js
97 ms
Web_Shop_iPhone_White.png
11 ms
Web_Shop_iPhone_Black.png
174 ms
bd624a4ac8
103 ms
prynt.co accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
prynt.co best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
prynt.co 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 doesn't use legible font sizes
Tap targets are not sized appropriately
EN
EN
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.
prynt.co
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: