lepuree.com website review

15 images could be 550 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

About 94 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

6 third-party services load with your homepage (Shopify, Klaviyo and subi.co and others), adding 571 KiB and 192 ms of main-thread time.

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

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

1 long task block the main thread while loading, the longest for 50 ms. During a long task the page ignores taps.

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

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 9.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

1 image 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 2.6 MB in 307 requests on a phone: images 902 KiB (29), other files 846 KiB (122) and scripts 653 KiB (117). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example footer-promo_cb20276c-43d6-4d40-bfc6-e633f57affac.webp at 2,688 px wide, shown at 350 px. Resized copies would save about 200 KiB.

1 image (236 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

1 image further down the page (236 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 0.74 g of CO₂e: 88.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is only 11 characters: “Le Puree US”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 41 characters: “Organic Baby and Toddler Food. Delivered.”. 70 to 160 characters is enough to sell the click.

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

Your <h1> is empty.

The homepage links to 34 pages on lepuree.com and 7 external pages.

The HTML your server sends has 1,213 of the 3,757 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://lepuree.com/products/tiny-hearts-x-le-puree-bundle, https://lepuree.com/products/new-starter-bundle-25-meals and https://lepuree.com/products/meat-bundle declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/, https://lepuree.com/pages/collection-list, https://lepuree.com/pages/shop-now, https://lepuree.com/products/gift-us, https://lepuree.com/pages/why-lp and https://lepuree.com/pages/faqs and 7 others all use the title “Le Puree US”. Search engines can't tell which page to show for a search, so each competes with the others.

https://lepuree.com/pages/collection-list, https://lepuree.com/pages/shop-now, https://lepuree.com/products/gift-us, https://lepuree.com/pages/why-lp, https://lepuree.com/pages/faqs and https://lepuree.com/blogs/news and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://lepuree.com/products/tiny-hearts-x-le-puree-bundle, https://lepuree.com/products/new-starter-bundle-25-meals and https://lepuree.com/products/meat-bundle use the same meta description. A description written for each page earns more clicks.

https://lepuree.com/pages/collection-list, https://lepuree.com/pages/shop-now, https://lepuree.com/pages/why-lp, https://lepuree.com/pages/faqs, https://lepuree.com/blogs/news and https://lepuree.com/collections/purees and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://lepuree.com/products/tiny-hearts-x-le-puree-bundle, https://lepuree.com/products/new-starter-bundle-25-meals and https://lepuree.com/products/meat-bundle took over 3 s to send their HTML from our server.

We fetched 13 pages linked from your homepage and read each the way a search engine does.

4 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://lepuree.com/cdn/shop/t/22/assets/checkout-gift-with-purchase.css?v=1413' because i…”.

1 image is served at too low a resolution for sharp phone screens.

Social proof on the homepage: 34 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage carries about 3,757 words of visible text.

Before a visitor clicks anything, the page loads Klaviyo and Meta 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 8 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 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.