moltenbeauty.com website review

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

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

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

8 third-party services load with your homepage (gokwik.co, Google Tag Manager and Shopify and others), adding 1.2 MB and 358 ms of main-thread time.

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

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

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

gokwik.co costs a phone 141 ms of main-thread work and 506 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.

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

11 images could be 231 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

12 KiB JavaScript is shipped twice across bundles.

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

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

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

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 56.3 MB in 299 requests on a phone: media 52.8 MB (3), images 1.4 MB (62) and scripts 987 KiB (57). Under 2 MB keeps phones on slow connections fast.

1 image (64 KiB) is 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.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

[role="img"] and [role="image"] elements must have alternative text: 5 elements on the page fail this check, rated serious by axe-core.

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

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

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

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

Structured data found (Organization and WebSite) but with 8 problems, for example “ld+json block 3 is not valid JSON (Bad control character in string literal in JSON at position )”.

3 links have no real href, so search engines can't follow them.

Your <h1> is empty.

The homepage links to 90 pages on moltenbeauty.com and 5 external pages.

https://www.moltenbeauty.com/collections/all, https://www.moltenbeauty.com/collections/skincare, https://www.moltenbeauty.com/collections/makeup, https://www.moltenbeauty.com/pages/concern, https://www.moltenbeauty.com/collections/bestsellers and https://www.moltenbeauty.com/pages/offers and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.moltenbeauty.com/products/molten-beauty-airy-blur-blush-drops and https://www.moltenbeauty.com/products/velvet-blur-lip-and-cheek-tint use the same meta description. A description written for each page earns more clicks.

https://www.moltenbeauty.com/pages/concern has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.moltenbeauty.com/pages/concern and https://www.moltenbeauty.com/pages/offers have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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