liquidap.com website review

14 images could be 5.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.

About 535 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.

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

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

7 third-party services load with your homepage (Squarespace, sqspcdn.com and zoominfo.com and others), adding 7.6 MB and 917 ms of main-thread time.

Squarespace costs a phone 875 ms of main-thread work and 1.5 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.

About 185 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

squarespace-cdn.com costs a phone 0 ms of main-thread work and 6.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.

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

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

Polyfills for old browsers add 104 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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.

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

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

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

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

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

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

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

Your homepage downloads 7.8 MB in 109 requests on a phone: images 6.1 MB (26), scripts 1.2 MB (49) and stylesheets 168 KiB (12). Under 2 MB keeps phones on slow connections fast.

4 images weigh 4.8 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example ezgif.com-animated-gif-maker+(4).gif at 390 px wide, shown at 121 px. Resized copies would save about 661 KiB.

4 images (4.8 MB) 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.

1 image further down the page (197 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

4 elements hidden from screen readers can still receive keyboard focus.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Headings skip levels (h1 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

Your title is only 28 characters: “Liquid Asset Partners - Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Liquid Asset Partners specializes in transforming” and “your surplus assets into value for your business.”). One clear main headline is easier for people and search engines.

Your meta description is 272 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/6321dd9843751f15822…”.

No XML sitemap at https://liquidap.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at liquidap.com/robots.txt, the first file search crawlers ask for.

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

The homepage links to 62 pages on liquidap.com and 3 external pages.

Your Organization JSON-LD is missing name, url, logo and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://liquidap.com/appraisals and https://liquidap.com/Services all use the title “Appraisals — Liquid Asset Partners”. Search engines can't tell which page to show for a search, so each competes with the others.

https://liquidap.com/appraisals, https://liquidap.com/auction, https://liquidap.com/liquidation, https://liquidap.com/finance, https://liquidap.com/projects and https://liquidap.com/medical-equipment-storefront and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://liquidap.com/Services, whose canonical is https://liquidap.com/appraisals. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://liquidap.com/appraisals, https://liquidap.com/auction, https://liquidap.com/liquidation, https://liquidap.com/finance, https://liquidap.com/projects and https://liquidap.com/about and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://liquidap.com/contact has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://liquidap.com/appraisals, https://liquidap.com/auction, https://liquidap.com/liquidation and https://liquidap.com/finance took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/6321dd9843751f1582212690/103/5c5…”.

Social proof on the homepage: 4 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no form on the homepage, so every lead has to click through to another page first.

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.

Opening the homepage sets 4 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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.