lavaartcosmetics.com website review

About 568 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.

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

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

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

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

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

8 third-party services load with your homepage (alia-prod.com, cloudfront.net and Shopify and others), adding 1.5 MB and 442 ms of main-thread time.

29 KiB could be saved by minifying JavaScript.

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

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

cloudfront.net costs a phone 123 ms of main-thread work and 507 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 67 ms of main-thread work and 433 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 58 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

12 KiB could be saved by minifying CSS.

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

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

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

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

5 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 173 ms to 166 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.9 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.2 MB in 310 requests on a phone: scripts 1.6 MB (93), images 1.4 MB (77) and other files 871 KiB (107). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 1.18 g of CO₂e: 141.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

7 tap targets are too small or too close together to hit reliably with a finger.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h2 → h5), 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 title is 90 characters, so Google will cut it off around 60: “Lava Art Cosmetic – Nature's finest ingredients blended into cosmetic – Lava Art Cosmetics”.

The homepage links to 73 pages on lavaartcosmetics.com and 9 external pages.

https://lavaart.com/products/glow-foundation is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://lavaart.com/collections/all, https://lavaart.com/pages/about, https://lavaart.com/pages/faq, https://lavaart.com/blogs/news and https://lavaart.com/pages/colour-quiz have no meta description, so Google writes the search snippet from whatever text it finds.

https://lavaart.com/products/perfect-cover-compact-foundation and https://lavaart.com/products/glow-foundation use the same meta description. A description written for each page earns more clicks.

https://lavaart.com/pages/color-match, https://lavaart.com/pages/about, https://lavaart.com/pages/faq, https://lavaart.com/no, https://lavaart.com/sv and https://lavaart.com/pages/colour-quiz have no <h1> headline, so visitors and search engines get no clear main topic.

https://lavaart.com/pages/color-match, https://lavaart.com/pages/about, https://lavaart.com/pages/faq, https://lavaart.com/blogs/news, https://lavaart.com/no and https://lavaart.com/sv took over 3 s to send their HTML from our server.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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 500 ()”.

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.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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