liquimedlock.com website review

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

2 images could be 693 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.0 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Hubspot and others), adding 1.7 MB and 926 ms of main-thread time.

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

Google Tag Manager costs a phone 521 ms of main-thread work and 876 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 56 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

Shopify costs a phone 237 ms of main-thread work and 483 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.

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

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

4 KiB could be saved by minifying JavaScript.

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 21.5 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 22.5 s. Good is under 3.8 s.

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

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

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

12 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 4.1 MB in 214 requests on a phone: scripts 1.9 MB (61), images 1.1 MB (23) and other files 738 KiB (107). Under 2 MB keeps phones on slow connections fast.

hero_bg.jpg weighs 783 KiB. 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 hero_bg.jpg at 4,096 px wide, shown at 390 px. Resized copies would save about 909 KiB.

5 images further down the page (420 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

3 images (475 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 1.15 g of CO₂e: 138.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

3 images have no alt text, which hurts accessibility and image search.

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

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

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

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

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

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

There are 3 <h1> headlines (“”, “Supporting Nurses and Clinics on the Frontlines o…” and “Nurses & Clinics Rejoice.”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 63 pages on liquimedlock.com and 8 external pages.

https://liquimedlock.com/products/liquicapture-flip-dip-cup%E2%84%A2-free-sample is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://liquimedlock.com/pages/liquimedlock%E2%84%A2-methadone-bottles, https://liquimedlock.com/pages/liquicapture%E2%84%A2-flip-dip-cup, https://liquimedlock.com/pages/medlockbox, https://liquimedlock.com/collections/all-products, https://liquimedlock.com/pages/about-us and https://liquimedlock.com/pages/media and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://liquimedlock.com/pages/liquimedlock%E2%84%A2-methadone-bottles, whose canonical is https://liquimedlock.com/pages/liquimedlock%e2%84%a2-methadone-bottles. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://liquimedlock.com/collections/all-products has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

4 errors were logged to the browser console while the page loaded, for example “Unexpected token ':'”.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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: 7 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

The homepage carries about 651 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 21 cookies, 6 of them by other companies (measured from a US location before any click).

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