lillieandpine.com website review

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

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

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

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

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

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

8 third-party services load with your homepage (Google CDN, Shopify and notify-me.io and others), adding 2.2 MB and 426 ms of main-thread time.

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

Shopify costs a phone 156 ms of main-thread work and 1.4 MB 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.

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

Google CDN costs a phone 181 ms of main-thread work and 297 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.

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

Polyfills for old browsers add 7 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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 13.9 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 10.5 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 15.0 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.

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

5 images have no width and height attributes, so the layout jumps as each one loads.

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 5.1 MB in 565 requests on a phone: other files 1.5 MB (252), images 1.5 MB (43) and scripts 1.4 MB (220). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

1 image has no alt text, which hurts accessibility and image search.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Alternative text of images should not be repeated as text: 12 elements on the page fail this check, rated minor by axe-core.

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

There are 6 <h1> headlines (“Lillie & Pine”, “Game Day Soy Candle - NEW!” and “Toasted Pumpkin Best Lotion Ever”). One clear main headline is easier for people and search engines.

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

The homepage links to 196 pages on lillieandpine.com and 23 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://www.lillieandpine.com/collections/new-fall-2026, https://www.lillieandpine.com/collections/perfume, https://www.lillieandpine.com/collections/home-family, https://www.lillieandpine.com/collections/mens-scents, https://www.lillieandpine.com/collections/shave-tube and https://www.lillieandpine.com/collections/sadies-stain-stick and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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

1 error was logged to the browser console while the page loaded, for example “Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the…”.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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