sorelleuk.com website review

17 images could be 1.4 MB 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.

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

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

8 third-party services load with your homepage (Klaviyo, Google Tag Manager and Klarna and others), adding 1.3 MB and 528 ms of main-thread time.

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

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

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

Klaviyo costs a phone 130 ms of main-thread work and 327 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.

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

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

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

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 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 8.9 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 19.8 s. Good is under 3.8 s.

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

8 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 78 ms to 88 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.6 MB in 268 requests on a phone: images 1.9 MB (19), scripts 1.6 MB (96) and other files 866 KiB (133). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example 2_d83aac72-084d-495e-8d6a-af34644b06a6_1300x.png at 1,080 px wide, shown at 195 px. Resized copies would save about 924 KiB.

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

ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

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

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Headings should not be empty: 6 elements on the page fail this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

The homepage links to 81 pages on sorelleuk.com and 2 external pages.

https://sorelleuk.com/a/wishlist and https://sorelleuk.com/collections/trending have no meta description, so Google writes the search snippet from whatever text it finds.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://assets.smartwishlist.webmarked.net/static/v6/css/smartwishlist.min.css?20200409' f…”.

Requests the notification permission on page load.

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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage has only about 188 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.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo 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 25 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 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.