pipekit.co.uk website review

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

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

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

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

8 third-party services load with your homepage (YouTube, Shopify and Jivochat and others), adding 2.6 MB and 1.2 s of main-thread time.

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

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

YouTube costs a phone 408 ms of main-thread work and 1.1 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.

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

Jivochat costs a phone 175 ms of main-thread work and 375 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 165 KiB of CSS is downloaded but never applied on this page.

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

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

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

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

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.

3 KiB could be saved by minifying CSS.

2 KiB could be saved by minifying JavaScript.

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

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

Your largest element takes 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

Your homepage downloads 4.5 MB in 321 requests on a phone: scripts 2.7 MB (108), other files 921 KiB (135) and images 371 KiB (25). Under 2 MB keeps phones on slow connections fast.

3 images (95 KiB) 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.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 70 characters, so Google will cut it off around 60: “Pipekit Ltd | Pipework Solutions | Drainage Systems | Pipes | Fittings”.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 876 pages on pipekit.co.uk and 7 external pages.

Your homepage links to https://www.pipekit.co.uk/collections/georg-fischer-pvc-u-imperial, which answers with an error. Visitors hit a dead end and search engines drop it.

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

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

https://www.pipekit.co.uk/pages/trade-application and https://www.pipekit.co.uk/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.pipekit.co.uk/pages/delivery, https://www.pipekit.co.uk/pages/trade-application, https://www.pipekit.co.uk/customer_authentication/redirect, https://www.pipekit.co.uk/collections/pressure-plastics, https://www.pipekit.co.uk/collections/pvc-pipe-and-fittings and https://www.pipekit.co.uk/collections/effast-pvc-u-pipe-fittings and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Cookie”).

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.

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.

The homepage has only about 195 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and LinkedIn Insight and 2 mores (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 13 cookies, 1 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 41 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.