4.2 sec in total
372 ms
3.3 sec
601 ms
Click here to check amazing Princeton Cryo content. Otherwise, check out these important facts you probably never knew about princetoncryo.com
PrincetonCryo is the leading supplier of cryogenic supplies, equipment and storage systems throughout the US and Canada with over 30 years in the industry. Unparalleled customer service.
Visit princetoncryo.comWe analyzed Princetoncryo.com page load time and found that the first response time was 372 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
princetoncryo.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value16.3 s
0/100
25%
Value7.4 s
27/100
10%
Value660 ms
45/100
30%
Value0
100/100
15%
Value19.1 s
3/100
10%
372 ms
244 ms
235 ms
43 ms
59 ms
Our browser made a total of 177 requests to load all elements on the main page. We found that 86% of them (153 requests) were addressed to the original Princetoncryo.com, 6% (11 requests) were made to Fonts.gstatic.com and 2% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (463 ms) belongs to the original domain Princetoncryo.com.
Page size can be reduced by 672.3 kB (31%)
2.2 MB
1.5 MB
In fact, the total size of Princetoncryo.com main page is 2.2 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. 65% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 134.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 134.2 kB or 86% of the original size.
Potential reduce by 514.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. Obviously, Princeton Cryo needs image optimization as it can save up to 514.4 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 21.1 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. This website has mostly compressed JavaScripts.
Potential reduce by 2.6 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. Princetoncryo.com has all CSS files already compressed.
Number of requests can be reduced by 130 (83%)
157
27
The browser has sent 157 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Princeton Cryo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 118 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
372 ms
74986faa08b576c93fa8281e104324e9.min.css
244 ms
styles-l.min.css
235 ms
css
43 ms
css
59 ms
css
63 ms
css
66 ms
bootstrap.optimized.min.css
219 ms
animate.optimized.css
220 ms
type1.css
222 ms
custom.css
305 ms
design_default.css
296 ms
settings_default.css
295 ms
font-awesome.min.css
40 ms
d5217a3fca6706efb20d423626b8cac8.min.js
362 ms
js
71 ms
approve_plugin_loader_alternate.php
59 ms
badge_180x55.jpg
294 ms
PRINCETONCRYO_RGB_75x295.png
172 ms
shopping-cart-icon.png
171 ms
YDS-10L_2.jpg
463 ms
PRINCETONCRYO_RGB.png
173 ms
download.jpg
172 ms
medical-cryongenic-supllies.jpg
172 ms
loader-1.gif
173 ms
online-cryogenic-supplies.jpg
189 ms
gtm.js
160 ms
feather_icons.png
125 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
59 ms
opensans-400.woff
119 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
74 ms
opensans-300.woff
120 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
104 ms
opensans-600.woff
120 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
147 ms
opensans-700.woff
119 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
148 ms
porto-icons.woff
147 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exQ.ttf
147 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf
148 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWV4exQ.ttf
148 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf
147 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf
149 ms
fa-solid-900.woff
207 ms
fa-regular-400.woff
219 ms
fa-brands-400.woff
219 ms
UqyNK9UOIntux_czAvDQx_ZcHqZXBNQzdcD8.ttf
148 ms
approve_core.js
50 ms
approve_plugin.js
123 ms
eyJpdiI6IlBFeFRHQkd3Z2RJZllTYm51OXZQWlE9PSIsInZhbHVlIjoiS2J4aW1qUVhzMzhHSXVZa0hOWWtWQT09IiwibWFjIjoiMjE3ZTQ0NDJjOGRjMTBlZDc1MTc1ZjU2MGQ4YTJiOTVhOWYzOWQ4YzhlNGI0ODhmNDI2NjdlODNkYzM2MmI3MCJ9
197 ms
eyJpdiI6IlBFeFRHQkd3Z2RJZllTYm51OXZQWlE9PSIsInZhbHVlIjoiS2J4aW1qUVhzMzhHSXVZa0hOWWtWQT09IiwibWFjIjoiMjE3ZTQ0NDJjOGRjMTBlZDc1MTc1ZjU2MGQ4YTJiOTVhOWYzOWQ4YzhlNGI0ODhmNDI2NjdlODNkYzM2MmI3MCJ9
269 ms
jquery.min.js
195 ms
common.min.js
156 ms
dataPost.min.js
231 ms
bootstrap.min.js
236 ms
app.min.js
238 ms
form-key-provider.min.js
237 ms
mage-translation-dictionary.min.js
254 ms
theme.min.js
299 ms
sw_megamenu.min.js
304 ms
weltpixel_persistentlayer.min.js
304 ms
weltpixel_gtm.min.js
306 ms
customer-data.min.js
306 ms
domReady.min.js
177 ms
jquery-mixin.min.js
187 ms
slick.min.js
189 ms
template.min.js
159 ms
confirm.min.js
159 ms
widget.min.js
159 ms
main.min.js
172 ms
bootstrap.min.js
216 ms
types.min.js
222 ms
layout.min.js
224 ms
text.min.js
205 ms
smart-keyboard-handler.min.js
155 ms
mage.min.js
173 ms
jquery.lazyload.min.js
218 ms
underscore.min.js
229 ms
local.min.js
228 ms
registry.min.js
234 ms
knockout.min.js
270 ms
section-config.min.js
244 ms
url.min.js
288 ms
storage.min.js
300 ms
storage-wrapper.min.js
302 ms
wrapper.min.js
243 ms
translate.min.js
304 ms
modal.min.js
303 ms
version.min.js
299 ms
scripts.min.js
283 ms
knockout-es5.min.js
241 ms
engine.min.js
264 ms
bootstrap.min.js
265 ms
observable_array.min.js
278 ms
bound-nodes.min.js
291 ms
main.min.js
298 ms
js-translation.json
305 ms
console-logger.min.js
301 ms
events.min.js
239 ms
js.storage.min.js
197 ms
modal-popup.html
112 ms
modal-slide.html
129 ms
modal-custom.html
133 ms
key-codes.min.js
132 ms
core.min.js
139 ms
z-index.min.js
170 ms
rego_b_326_12t6.jpg
186 ms
01612165_1.jpg
199 ms
01612165.jpg
206 ms
01612124.jpg
205 ms
01612169.jpg
212 ms
10c446666pmse-web_1.jpg
246 ms
10c446666pmse-web.jpg
265 ms
05c446666pmse-web.jpg
272 ms
knockout-repeat.min.js
269 ms
knockout-fast-foreach.min.js
271 ms
observable_source.min.js
275 ms
renderer.min.js
311 ms
resizable.min.js
327 ms
i18n.min.js
333 ms
scope.min.js
341 ms
range.min.js
345 ms
mage-init.min.js
348 ms
keyboard.min.js
384 ms
optgroup.min.js
400 ms
after-render.min.js
406 ms
autoselect.min.js
414 ms
datepicker.min.js
419 ms
outer_click.min.js
421 ms
fadeVisible.min.js
457 ms
collapsible.min.js
458 ms
staticChecked.min.js
452 ms
simple-checked.min.js
452 ms
bind-html.min.js
456 ms
tooltip.min.js
450 ms
color-picker.min.js
457 ms
arrays.min.js
454 ms
compare.min.js
446 ms
misc.min.js
450 ms
objects.min.js
456 ms
strings.min.js
449 ms
template.min.js
458 ms
logger.min.js
449 ms
entry-factory.min.js
444 ms
console-output-handler.min.js
447 ms
formatter.min.js
455 ms
message-pool.min.js
450 ms
levels-pool.min.js
453 ms
logger-utils.min.js
446 ms
jquery.cookie.min.js
445 ms
data.min.js
446 ms
disable-selection.min.js
454 ms
focusable.min.js
451 ms
form.min.js
454 ms
ie.min.js
446 ms
keycode.min.js
445 ms
labels.min.js
446 ms
jquery-patch.min.js
455 ms
plugin.min.js
451 ms
safe-active-element.min.js
454 ms
safe-blur.min.js
447 ms
scroll-parent.min.js
446 ms
tabbable.min.js
446 ms
unique-id.min.js
455 ms
class.min.js
456 ms
loader.min.js
454 ms
async.min.js
446 ms
tooltip.html
432 ms
spectrum.min.js
406 ms
tinycolor.min.js
415 ms
entry.min.js
316 ms
moment.min.js
360 ms
cookie-wrapper.min.js
293 ms
dom-observer.min.js
79 ms
bindings.min.js
91 ms
js.cookie.min.js
76 ms
print.min.css
77 ms
princetoncryo.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role]s do not have all required [aria-*] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
princetoncryo.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
princetoncryo.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 uses 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 Princetoncryo.com 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 Princetoncryo.com 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.
princetoncryo.com
Open Graph description is not detected on the main page of Princeton Cryo. 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: