love-hemp.com website review

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

14 images could be 474 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

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

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

8 third-party services load with your homepage (rechargecdn.com, Trust Pilot and b-cdn.net and others), adding 521 KiB and 242 ms of main-thread time.

About 247 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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 5.6 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 10.2 s. Good is under 3.8 s.

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

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

1 image 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' largest content (lcp) went from 1.6 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.5 MB in 245 requests on a phone: other files 783 KiB (109), images 764 KiB (18) and scripts 697 KiB (83). Under 2 MB keeps phones on slow connections fast.

5 images are downloaded at several times the size a phone draws them, for example lh-client-goal-focus.png at 487 px wide, shown at 52 px. Resized copies would save about 236 KiB.

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

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

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

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

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

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

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

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

There are 2 <h1> headlines (“Love Hemp” and “Black Friday can wait — up to 55% off selected pr…”). One clear main headline is easier for people and search engines.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 148 pages on love-hemp.com and 28 external pages.

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

https://lovehemp.com/collections/cbd-patches and https://lovehemp.com/pages/learn-hub have no meta description, so Google writes the search snippet from whatever text it finds.

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

6 of 30 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 “Cannot read properties of null (reading 'addEventListener')”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

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

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.

The homepage carries about 577 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 12 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.