onlycurlslondon.com website review

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

Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (Shopify, alia-prod.com and Klaviyo and others), adding 1.8 MB and 1.4 s of main-thread time.

15 images could be 258 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

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

alia-prod.com costs a phone 352 ms of main-thread work and 324 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.

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

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

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

60 KiB JavaScript is shipped twice across bundles.

19 KiB could be saved by minifying CSS.

9 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.

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

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

Your largest element takes 7.1 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 760 ms in total while the page loads. Good is under 200 ms.

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

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

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 32.4 MB in 435 requests on a phone: media 27.6 MB (10), scripts 1.9 MB (178) and images 1.1 MB (38). Under 2 MB keeps phones on slow connections fast.

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

Elements must only use permitted ARIA attributes: 16 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 16 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

Your canonical URL points to onlycurls.com, not onlycurlslondon.com, so Google may credit that host instead.

There are 4 <h1> headlines (“Frizz-free, defined curls”, “without the guesswork.” and “Your perfect curl match? Let's find it.”). One clear main headline is easier for people and search engines.

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://onlycurls.com)”.

The homepage links to 271 pages on onlycurlslondon.com and 18 external pages.

Your homepage links to https://onlycurlslondon.com/products/build-your-bundle, which answers with an error. Visitors hit a dead end and search engines drop it.

https://onlycurlslondon.com/collections/only-curls-satin-lined-beanie-hats and https://onlycurlslondon.com/collections/little-curls-kids-satin-lined-beanie-hats all use the title “Satin Lined Beanie Hats | Beanie with Satin Lining | Only Curls”. Search engines can't tell which page to show for a search, so each competes with the others.

https://onlycurlslondon.com/pages/gift-guide has no meta description, so Google writes the search snippet from whatever text it finds.

https://onlycurlslondon.com/collections/bundles/starter and https://onlycurlslondon.com/collections/bundles use the same meta description. A description written for each page earns more clicks.

https://onlycurlslondon.com/collections/curly-hair-products, https://onlycurlslondon.com/collections/bundles/starter, https://onlycurlslondon.com/collections/little-curls, https://onlycurlslondon.com/collections/accessories, https://onlycurlslondon.com/collections/only-curls-satin-lined-beanie-hats and https://onlycurlslondon.com/pages/gift-guide 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 97 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://files.alia-prod.com/OCLinearLogo1248x.png-1753797385741.

2 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://whoami.leafsignal.app/' from origin 'https://onlycurlslondon.com' has been blocked by CORS …”.

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.

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 777 words of visible text.

Before a visitor clicks anything, the page loads Klaviyo and Microsoft Clarity (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 13 cookies, 2 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 54 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.