licksleeve.uk website review

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

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 1.4 MB and 1.4 s of main-thread time.

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

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

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

Facebook costs a phone 250 ms of main-thread work and 226 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.

Klaviyo costs a phone 156 ms of main-thread work and 308 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.

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

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.

5 KiB could be saved by minifying JavaScript.

Your largest element takes 29.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “INNOVATING BETTER PET RECOVERY Fear-free, stress-free, alte…”.

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

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

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

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

9 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 6.4 MB in 263 requests on a phone: images 2.8 MB (27), scripts 2.0 MB (103) and other files 801 KiB (100). Under 2 MB keeps phones on slow connections fast.

2 images weigh 2.4 MB together. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example 85df968aa3118985feeca76b3e6ed519.webp at 4,096 px wide, shown at 350 px. Resized copies would save about 2.0 MB.

4 images (3.0 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.

5 images further down the page (1.7 MB) 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 1.81 g of CO₂e: 217.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

6 elements use ARIA attributes their role does not allow, which confuses screen readers.

20 elements have a tabindex above 0, which scrambles the keyboard order.

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

Some list items are not inside a list.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Elements with visible text labels do not have matching accessible names. (1 element).

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is 86 characters, so Google will cut it off around 60: “Lick Sleeve Official UK Site: Wearable Dog Leg Protection – United Kingdom Lick Sleeve”.

There are 2 <h1> headlines (“Innovating Better Pet Recovery” and “Find the Right Solution for Your Pet”). One clear main headline is easier for people and search engines.

Structured data found (LocalBusiness, Organization, Product and VideoObject) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("={search_term_string}")”.

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

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

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 55 pages on licksleeve.uk and 10 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) 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://licksleeve.uk/blogs/news/how-to-know-if-your-dogs-leg-is-broken-or-sprained and https://licksleeve.uk/blogs/news all use the title “Read the Latest Dog Articles | Lick Sleeve Official UK Site – United …”. Search engines can't tell which page to show for a search, so each competes with the others.

https://licksleeve.uk/pages/faq, https://licksleeve.uk/pages/lick-sleeve-science, https://licksleeve.uk/pages/contact-us, https://licksleeve.uk/pages/shop and https://licksleeve.uk/blogs/news 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://licksleeve.uk/blogs/news/detecting-treating-canine-achilles-tendon-ruptures, whose canonical is https://licksleeve.uk/blogs/newstecting-treating-canine-achilles-tendon-ruptures. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://licksleeve.uk/pages/faq and https://licksleeve.uk/pages/our-story have no <h1> headline, so visitors and search engines get no clear main topic.

https://licksleeve.uk/blogs/news/how-to-read-a-dogs-body-language-deciphering-canine-non-verbal-cues took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=355028761&Ver=2&mid=3e597975-6fc2-40e2-8e10-9707bc5249eb&bo=3&sid=b01ac3c0dd7e11f19ddc09ce07655c77&vid=b01b1830dd7e11f1936f6d5caa4f93ca&vids=0&msclkid=N&pi=918639831&l.

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Social proof on the homepage: a star rating. 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 form on the homepage, so every lead has to click through to another page first.

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 692 words of visible text.

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