nortonbarrie.com website review

8 images could be 326 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Shopify, productessentials.app and Klarna and others), adding 967 KiB and 716 ms of main-thread time.

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

About 438 KiB of JavaScript is downloaded but never used on this page.

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

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

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

11 long tasks block the main thread while loading, the longest for 172 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 could be saved by minifying JavaScript.

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

11 KiB JavaScript is shipped twice across bundles.

6 KiB could be saved by minifying CSS.

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 9.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

Sandbanks-desktop-banner-AW26.jpg weighs 499 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.4 MB in 197 requests on a phone: scripts 1.1 MB (59), images 1.0 MB (13) and other files 847 KiB (100). Under 2 MB keeps phones on slow connections fast.

4 images (182 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.

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

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

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

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

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

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

The homepage links to 563 pages on nortonbarrie.com and 4 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://www.nortonbarrie.co.uk/en-us/collections/new-in and https://www.nortonbarrie.co.uk/collections/new-in all use the title “New In - Designer Fashion - Norton Barrie”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.nortonbarrie.co.uk/en-us/collections/mens-new/gender_men has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.nortonbarrie.co.uk/en-us/collections/new-in, https://www.nortonbarrie.co.uk/collections/new-in, https://www.nortonbarrie.co.uk/en-us/collections/new-in/gender_womens and https://www.nortonbarrie.co.uk/collections/new-in/gender_womens use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.nortonbarrie.co.uk/collections/new-in, whose canonical is https://www.nortonbarrie.co.uk/en-us/collections/new-in. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.nortonbarrie.co.uk/en-us/collections/new-in, https://www.nortonbarrie.co.uk/collections/new-in, https://www.nortonbarrie.co.uk/en-us/collections/new-in-shirts, https://www.nortonbarrie.co.uk/en-us/collections/new-in-knitwear, https://www.nortonbarrie.co.uk/en-us/collections/new-in-hoodies-sweatshirts and https://www.nortonbarrie.co.uk/en-us/collections/new-in-jeans 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 167 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=211023905&Ver=2&mid=22bc0226-41d9-4e86-9871-55bed89f03b2&bo=1&sid=b2dcbe60ddf111f1ac1e695ee53fb090&vid=b2dcef50ddf111f19be5d59d1328293a&vids=1&msclkid=N&pi=918639831&l.

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

6 errors were logged to the browser console while the page loaded, for example “Failed to fetch”.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 868 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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