lostartistrylash.com website review

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

About 897 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.

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

8 third-party services load with your homepage (Klaviyo, Shopify and Google Tag Manager and others), adding 1.7 MB and 539 ms of main-thread time.

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

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

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

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

Heroku costs a phone 21 ms of main-thread work and 413 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.

188 KiB could be saved by minifying JavaScript.

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

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

1 image could be 74 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

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

Your largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “TOP SELLING GLUES”. Most of its time is element render delay (2.5 s).

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 113 ms to 124 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.7 MB in 231 requests on a phone: scripts 1.6 MB (99), images 931 KiB (20) and other files 778 KiB (95). Under 2 MB keeps phones on slow connections fast.

free_education_mobile.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).

1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Elements with visible text labels do not have matching accessible names. (1 element).

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

Structured data found (BreadcrumbList, HealthAndBeautyBusiness, Organization and WebSite) but with 1 problem, for example “WebSite: url is not an absolute URL ("lostartistrylash.com")”.

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

The homepage links to 137 pages on lostartistrylash.com and 14 external pages.

There is no https://lostartistrylash.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://lostartistrylash.com/collections/untamed-liquids has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://lostartistrylash.com/products/soft-anime-spikes, whose canonical is https://lostartistrylash.com/products/anime-collection. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://lostartistrylash.com/products/ultra-dark-short-stem-premade-lash-fans, https://lostartistrylash.com/products/angel-premade-lashes, https://lostartistrylash.com/products/light-brown-short-stem-pre-fan-lashes and https://lostartistrylash.com/products/coloured-mid-stem-premade-lash-fans have no <h1> headline, so visitors and search engines get no clear main topic.

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

13 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-app.sealsubscriptions.com/shopify/public/css/style.css?shop=lostartistrylash.m…”.

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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