4cryo.com website review

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.2 s faster on a phone.

About 212 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

Your mobile performance score is 10. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 4.3 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Bigcommerce and others), adding 3.2 MB and 1.9 s of main-thread time.

Google CDN costs a phone 741 ms of main-thread work and 1.1 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

11 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

Google Tag Manager costs a phone 464 ms of main-thread work and 529 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Bigcommerce costs a phone 201 ms of main-thread work and 713 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

jotfor.ms costs a phone 200 ms of main-thread work and 615 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

20 long tasks block the main thread while loading, the longest for 251 ms. During a long task the page ignores taps.

The page has 1,802 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

49 KiB could be saved by minifying JavaScript.

27 KiB could be saved by minifying CSS.

10 files are served with short cache lifetimes, so returning visitors download them again (84 KiB).

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Polyfills for old browsers add 15 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 image could be 4 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

The first text or image appears after 10.0 s on a phone. Good is under 1.8 s.

Your largest element takes 18.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Liquid Nitrogen Storage Containers”.

The page becomes fully interactive after 21.2 s. Good is under 3.8 s.

The layout shifts by 0.733 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Visually, the page fills in at 10.0 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.

11 images have no width and height attributes, so the layout jumps as each one loads.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.7 MB in 115 requests on a phone: scripts 2.3 MB (49), images 385 KiB (20) and other files 379 KiB (7). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 1.05 g of CO₂e: 126.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

8 tap targets are too small or too close together to hit reliably with a finger.

ARIA commands must have an accessible name: 5 elements on the page fail this check, rated serious by axe-core.

Some list items are not inside a list.

Some lists contain elements other than list items, which screen readers announce wrongly.

All page content should be contained by landmarks: 23 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

2 visible links have no text or label, so screen readers cannot say where they go.

34 links have no real href, so search engines can't follow them.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 196 pages on 4cryo.com and 0 external pages.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

Your homepage links to /blog and /automated-freezers-ic-biomedical, which answer with an error. Visitors hit a dead end and search engines drop them.

We fetched 15 pages linked from your homepage (of 53 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343136127&tm=gtm002&Ver=2&mid=f41f0b1a-fbea-437f-8faf-28e993d3e5e3&bo=1&sid=d8a54930d63811f1948c17d357c8e5c2&vid=d8a58e00d63811f19c0beb4759ba578a&vids=1&msclkid=N&pi=9.

7 of 18 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

3 errors were logged to the browser console while the page loaded, for example “Uncaught ReferenceError: jQuery is not defined”.

13 links from your homepage to your own site are broken, for example https://4cryo.com/login.php?action=create_account (network).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

HSTS is set, but max-age is 0 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

4cryo.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

4cryo.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 489 words of visible text.

DMARC is set to p=none, so mail pretending to be 4cryo.com is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Ads (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 18 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.