lavaart.com website review

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

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

alia-prod.com costs a phone 1.1 s of main-thread work and 282 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

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

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

cloudfront.net costs a phone 378 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.

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

Snapchat costs a phone 295 ms of main-thread work and 63 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 258 ms. During a long task the page ignores taps.

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

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

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

29 KiB could be saved by minifying JavaScript.

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

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

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

Your largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (3.1 s).

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

The first text or image appears after 2.0 s on a phone. Good is under 1.8 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 286 requests on a phone: scripts 1.6 MB (94), images 1.4 MB (79) and other files 649 KiB (72). Under 2 MB keeps phones on slow connections fast.

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

ARIA commands must have an accessible name: 7 elements on the page fail this check, rated serious by axe-core.

Links must have discernible text: 7 elements on the page fail this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 3 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.

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

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 lavaart.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 and https://lavaart.com/pages/about 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.

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 16 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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.