closerpets.co.uk website review

About 1.4 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.

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

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

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

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

14 images could be 751 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

ContentSquare costs a phone 432 ms of main-thread work and 185 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.

POWr costs a phone 324 ms of main-thread work and 77 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.

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

Yotpo costs a phone 215 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.

powrcdn.com costs a phone 174 ms of main-thread work and 609 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.

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

About 206 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.

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

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

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

11 KiB JavaScript is shipped twice across bundles.

6 KiB could be saved by minifying JavaScript.

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

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

For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.

14 images have no width and height attributes, so the layout jumps as each one loads.

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

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

Your homepage downloads 6.7 MB in 355 requests on a phone: scripts 2.7 MB (125), images 1.8 MB (27) and other files 1.5 MB (160). Under 2 MB keeps phones on slow connections fast.

Mobile_Banners_steel_etc_2f0656de-3abe-4754-87af-4b33b398d29 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.89 g of CO₂e: 227.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

1 dropdown has no label.

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

4 tap targets are too small or too close together to hit reliably with a finger.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

4 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Elements with visible text labels do not have matching accessible names. (2 elements).

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

1 link has no real href, so search engines can't follow it.

The homepage links to 167 pages on closerpets.co.uk and 16 external pages.

https://closerpets.co.uk/collections/cat-products, https://closerpets.co.uk/collections/fish-products and https://closerpets.co.uk/collections/cat-feeders took over 3 s to send their HTML from our server.

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

4 images failed to load on a phone, for example https://public-images.judge.me/judgeme/medals-v2-2025-rebranding/tran/gold.svg?auto=format.

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

9 of 37 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 2 deprecated browser APIs that will stop working in future browsers (“webkitRequestAnimationFrame is vendor-specific. Please use the standard requestAnimationFrame inste…”).

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

Large scripts ship without source maps.

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.

Social proof on the homepage: 132 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

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 921 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 24 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 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.