cliphairtrade.com website review

The page goes through 1 redirect before it starts loading, costing about 6.2 s. Link and advertise the final URL directly.

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

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

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

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

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

8 third-party services load with your homepage (Shopify, Yotpo and Hubspot and others), adding 1.9 MB and 1.6 s of main-thread time.

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

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

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

Yotpo costs a phone 189 ms of main-thread work and 311 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.

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

18 KiB could be saved by minifying JavaScript.

19 KiB JavaScript is shipped twice across bundles.

1 image could be 10 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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 15.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Cliphair has been supporting salons and professional hairdr…”.

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

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

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

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

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

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.7 MB in 652 requests on a phone: scripts 2.3 MB (200), other files 1.5 MB (297) and images 411 KiB (45). Under 2 MB keeps phones on slow connections fast.

trade-enquiries-register-mobile.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

The robots meta tag says “noindex,nofollow”: Google is told not to list this page at all.

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

The homepage links to 424 pages on cliphairtrade.com and 20 external pages.

https://cliphairtrade.com/collections/all, https://cliphairtrade.com/products/cliphair-silky-hair-spray, https://cliphairtrade.com/products/cliphair-heat-spray, https://cliphairtrade.com/products/hair-extension-hanger-and-carrier-bag, https://cliphairtrade.com/products/hair-extension-holder and https://cliphairtrade.com/pages/hair-extensions-shipping-delivery are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://cliphairtrade.com/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.

https://cliphairtrade.com/collections/all, https://cliphairtrade.com/products/quench-the-thirst-deep-moisture-shampoo, https://cliphairtrade.com/products/quench-the-thirst-deep-moisture-conditioner, https://cliphairtrade.com/products/quench-the-thirst-deep-conditioning-hair-mask, https://cliphairtrade.com/products/cliphair-silky-hair-spray and https://cliphairtrade.com/products/cliphair-heat-spray and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

A form field blocks pasting, which frustrates password managers and people on phones.

1 image is served at too low a resolution for sharp phone screens.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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.

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

Before a visitor clicks anything, the page loads HubSpot, Klaviyo 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 35 cookies, 7 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 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.