perlick.com website review

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.

13 files are served with short cache lifetimes, so returning visitors download them again (16.4 MB).

8 third-party services load with your homepage (powerapps.com, Google Tag Manager and Facebook and others), adding 20.5 MB and 891 ms of main-thread time.

About 1.8 MB of JavaScript is downloaded but never used on this page.

website-files.com costs a phone 74 ms of main-thread work and 16.6 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.

Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.

powerapps.com costs a phone 455 ms of main-thread work and 3.0 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 long tasks block the main thread while loading, the longest for 696 ms. During a long task the page ignores taps.

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

Google Tag Manager costs a phone 120 ms of main-thread work and 325 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.

About 175 KiB of CSS is downloaded but never applied on this page.

7 images could be 155 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

65 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 23 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.

2 KiB could be saved by minifying CSS.

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

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

Your largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 96 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 21.2 MB in 178 requests on a phone: media 16.0 MB (2), scripts 4.1 MB (76) and images 560 KiB (29). Under 2 MB keeps phones on slow connections fast.

68efb67750d51933e2aed74a_A004_C001_0201O9_003.R3D.22_53_46_1 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

2 images (69 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

3 buttons have no accessible name, so screen readers announce just “button”.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Input buttons must have discernible text: 1 element on the page fails this check, rated critical by axe-core.

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.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Your title is 94 characters, so Google will cut it off around 60: “Perlick Corporation - Commercial Refrigerator and Bar Equipment Supplier - Perlick Corpor…”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 65 pages on perlick.com and 24 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.perlick.com/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 https://www.perlick.com/residential/media, https://www.perlick.com/commercial/media and https://www.perlick.com/commercial/resources/downloads, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.perlick.com/commercial/resources/faqs and https://www.perlick.com/residential/resources/faqs all use the title “FAQs”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.perlick.com/commercial, https://www.perlick.com/commercial/resources, https://www.perlick.com/commercial/resources/testimonials and https://www.perlick.com/warranty-and-support have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.perlick.com/residential and https://www.perlick.com/commercial/resources/visionaries use the same meta description. A description written for each page earns more clicks.

https://www.perlick.com/commercial/resources/visionaries has no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Cookie”).

1 image is served at too low a resolution for sharp phone screens.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 240 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 2 mores (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 9 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 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.