hallby.co.uk website review

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

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

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

17 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

8 third-party services load with your homepage (iubenda, Shopify and Google Tag Manager and others), adding 4.9 MB and 1.1 s of main-thread time.

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

About 680 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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

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

iubenda costs a phone 446 ms of main-thread work and 125 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.

Google Tag Manager costs a phone 238 ms of main-thread work and 333 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.

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

54 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 7 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.

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

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

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

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

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

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 18.0 MB in 462 requests on a phone: media 10.9 MB (4), images 3.3 MB (33) and scripts 2.0 MB (186). Under 2 MB keeps phones on slow connections fast.

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

3 images are downloaded at several times the size a phone draws them, for example 50th.jpg at 3,333 px wide, shown at 44 px. Resized copies would save about 1.7 MB.

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

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

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

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

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

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

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

The homepage links to 96 pages on hallby.co.uk and 3 external pages.

https://hallby.co.uk/collections/gifts-for-her, https://hallby.co.uk/collections/gifts-for-him, https://hallby.co.uk/collections/gifts-for-mum and https://hallby.co.uk/collections/gifts-for-dad have no meta description, so Google writes the search snippet from whatever text it finds.

https://hallby.co.uk/collections/all-boxes, https://hallby.co.uk/collections/birthday-1, https://hallby.co.uk/collections/christmas, https://hallby.co.uk/collections/congratulations-1, https://hallby.co.uk/collections/parents-pregnancy-and-new-baby and https://hallby.co.uk/collections/self-care and 4 others took over 3 s to send their HTML from our server.

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

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

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 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 1,074 words of visible text.

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

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

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