cherishlewis.com website review

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

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

8 third-party services load with your homepage (Shopify, Hexton and minmaxify.com and others), adding 2.9 MB and 728 ms of main-thread time.

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

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

Shopify costs a phone 352 ms of main-thread work and 950 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 3.9 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Hexton costs a phone 115 ms of main-thread work and 1.3 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.

cloudfront.net costs a phone 58 ms of main-thread work and 322 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.

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

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

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

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

22 KiB could be saved by minifying JavaScript.

9 KiB could be saved by minifying CSS.

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 12.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Cherish Lewis Love, Blossom & Cherish - Pet Treasures, Flor…”.

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

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

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

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-11-07, real Chrome visitors' tap response (inp) went from 101 ms to 99 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.7 MB in 389 requests on a phone: images 3.1 MB (54), scripts 3.0 MB (170) and other files 985 KiB (138). Under 2 MB keeps phones on slow connections fast.

15 images are downloaded at several times the size a phone draws them, for example 2223ADD1-43D2-473E-B5B8-3B0625BEA7FF_1024x1024.jpg at 768 px wide, shown at 140 px. Resized copies would save about 1.6 MB.

35 images further down the page (2.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (187 KiB) is 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 2.17 g of CO₂e: 260.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Inline text spacing must be adjustable with custom stylesheets: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

1 element hidden from screen readers can still receive keyboard focus.

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

There are 9 <h1> headlines (“<img src="//cherishlewis.co.uk/cdn/shop/files/IMG…”, “Love, Blossom & Cherish” and “Pet Treasures, Floral Wonders,”). One clear main headline is easier for people and search engines.

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

The homepage links to 222 pages on cherishlewis.com and 5 external pages.

https://cherishlewis.co.uk/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://cherishlewis.co.uk/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://cherishlewis.co.uk/customer_authentication/redirect and https://cherishlewis.co.uk/collections/appliances-cherish-lewis have no meta description, so Google writes the search snippet from whatever text it finds.

https://cherishlewis.co.uk/customer_authentication/redirect, https://cherishlewis.co.uk/collections/food-preparation-storage-cherish-lewis and https://cherishlewis.co.uk/collections/cleaning-supplies-cherish-lewis-uk have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'global_config')”.

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

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 1,213 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok 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 21 cookies, 1 of them by other companies (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 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.