laurageller.com website review

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

poweredbyhue.app costs a phone 1.8 s of main-thread work and 1.1 MB 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.

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

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

8 third-party services load with your homepage (poweredbyhue.app, quikly.com and minmaxify.com and others), adding 4.1 MB and 6.8 s of main-thread time.

About 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

55 files are served with short cache lifetimes, so returning visitors download them again (2.0 MB).

20 long tasks block the main thread while loading, the longest for 1.1 s. During a long task the page ignores taps.

quikly.com costs a phone 955 ms of main-thread work and 225 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 849 ms of main-thread work and 958 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.

minmaxify.com costs a phone 898 ms of main-thread work and 12 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.

Google Tag Manager costs a phone 790 ms of main-thread work and 339 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 158 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 440 ms faster on a phone.

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

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

45 KiB could be saved by minifying JavaScript.

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

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors wait 643 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Your largest element takes 12.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “HP Promo 11/1-11/9”.

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

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

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

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

Real visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.1 s to 4.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.

Your homepage downloads 13.4 MB in 801 requests on a phone: scripts 5.7 MB (280), media 3.0 MB (7) and images 2.2 MB (55). Under 2 MB keeps phones on slow connections fast.

LG.com_Ultimate_Palette_Artisans_Archive_800x600_withCTA.png 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).

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

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

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

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

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

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

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

1 element has a tabindex above 0, which scrambles the keyboard order.

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

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

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

1 link has no real href, so search engines can't follow it.

The homepage links to 220 pages on laurageller.com and 0 external pages.

https://www.laurageller.com/collections/try-before-you-buy and https://www.laurageller.com/collections/best-sellers all use the title “Our Best Sellers – Laura Geller Beauty”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.laurageller.com/pages/tuscan-sun-sweepstakes and https://www.laurageller.com/collections/fragrance have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.laurageller.com/collections/try-before-you-buy and https://www.laurageller.com/collections/best-sellers use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.laurageller.com/collections/try-before-you-buy, whose canonical is https://www.laurageller.com/collections/best-sellers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.laurageller.com/collections/try-before-you-buy, https://www.laurageller.com/collections/best-sellers, https://www.laurageller.com/collections/holiday-gift-guide, https://www.laurageller.com/pages/tuscan-sun-sweepstakes, https://www.laurageller.com/collections/fragrance and https://www.laurageller.com/collections/limited-edition and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.laurageller.com/collections/try-before-you-buy, https://www.laurageller.com/collections/best-sellers, https://www.laurageller.com/collections/holiday-gift-guide, https://www.laurageller.com/pages/tuscan-sun-sweepstakes, https://www.laurageller.com/collections/fragrance and https://www.laurageller.com/collections/limited-edition and 9 others 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.

https://www.laurageller.com/collections/palettes took over 3 s to send its HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

Large scripts ship without source maps.

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

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