radiantlamourlocks.com website review

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

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

5 images could be 3.1 MB 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.

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

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

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

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

8 third-party services load with your homepage (Klaviyo, Shopify and Bugsnag and others), adding 654 KiB and 277 ms of main-thread time.

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

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

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

About 10 KiB of CSS is downloaded but never applied on this page.

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.

5 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

Your largest element takes 13.1 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 8.7 s (Speed Index). Good is under 3.4 s.

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

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

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 6.1 MB in 329 requests on a phone: images 4.0 MB (18), other files 1.1 MB (206) and scripts 759 KiB (82). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example shutterstock_350965784.jpg at 5,446 px wide, shown at 353 px. Resized copies would save about 3.2 MB.

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

shutterstock_1675292743.jpg 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.74 g of CO₂e: 208.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Form elements should have a visible label: 14 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.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

There are 5 <h1> headlines (“Elegance in Every Extension”, “Unleash your Radiance” and “Unveil your most radiant self!”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 88 pages on radiantlamourlocks.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.radiantlamourlocks.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.radiantlamourlocks.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.radiantlamourlocks.com/collections/all, https://www.radiantlamourlocks.com/pages/about-radiant-lamour-locks, https://www.radiantlamourlocks.com/pages/contact, https://www.radiantlamourlocks.com/customer_authentication/redirect and https://www.radiantlamourlocks.com/pages/how-to-take-care-of-your-hair have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.radiantlamourlocks.com/products/wavy-virgin-machine-hair-weft and https://www.radiantlamourlocks.com/products/wavy-colored-virgin-hair-wefts use the same meta description. A description written for each page earns more clicks.

https://www.radiantlamourlocks.com/collections/all, https://www.radiantlamourlocks.com/products/wavy-virgin-machine-hair-weft, https://www.radiantlamourlocks.com/products/straight-virgin-machine-weft-hair-extensions, https://www.radiantlamourlocks.com/products/curly-virgin-weft-hair, https://www.radiantlamourlocks.com/products/tight-curly-virgin-weft and https://www.radiantlamourlocks.com/products/loose-natural-curly-virgin-wefts and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

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 carries about 856 words of visible text.

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