unitywholesale.co.uk website review

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.6 s.

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

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

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

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

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

8 third-party services load with your homepage (tailwindcss.com, JSDelivr CDN and Shopify and others), adding 330 KiB and 315 ms of main-thread time.

About 37 KiB of JavaScript is downloaded but never used 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.

5 KiB could be saved by minifying JavaScript.

1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).

Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This is a strict B2B portal. By proceeding, you confirm you…”. Most of its time is element render delay (2.5 s).

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

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

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

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

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 4.5 MB in 185 requests on a phone: images 3.6 MB (120), other files 533 KiB (30) and scripts 343 KiB (27). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example app-preview-4.jpg at 966 px wide, shown at 186 px. Resized copies would save about 43 KiB.

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

1 image (54 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 1.28 g of CO₂e: 154.0 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.

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

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

Your page has no <title>, so Google has to invent the blue link in search results.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“UNITY” and “TRUST”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 152 pages on unitywholesale.co.uk and 0 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://unitywholesale.co.uk/products/cloudz-hemp-paper-king-size-wide, https://unitywholesale.co.uk/products/cloudz-white-paper-king-size-wide, https://unitywholesale.co.uk/products/cloudz-mix-paper-king-size-with-side-lock, https://unitywholesale.co.uk/products/cloudz-rainbow-paper-king-size-with-side-lock, https://unitywholesale.co.uk/products/cloudz-brown-paper-king-size-with-side-lock and https://unitywholesale.co.uk/collections/cloudz and 9 others have no <title>, so Google invents the link text in results.

https://unitywholesale.co.uk/products/cloudz-hemp-paper-king-size-wide, https://unitywholesale.co.uk/products/cloudz-white-paper-king-size-wide, https://unitywholesale.co.uk/products/cloudz-mix-paper-king-size-with-side-lock, https://unitywholesale.co.uk/products/cloudz-rainbow-paper-king-size-with-side-lock, https://unitywholesale.co.uk/products/cloudz-brown-paper-king-size-with-side-lock and https://unitywholesale.co.uk/collections/cloudz and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://unitywholesale.co.uk/products/6s-pack-single took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://unitywholesale.co.uk/cdn/shop/files/app-preview-pricing.jpg?v=1159.

2 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 ()”.

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

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.

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

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

Opening the homepage sets 5 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.