leprunier.com website review

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

8 third-party services load with your homepage (route.com, ZenDesk and Accessibe Accessibility Overlay and others), adding 2.7 MB and 1.4 s of main-thread time.

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

About 1.6 MB of JavaScript is downloaded but never used on this page.

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

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

route.com costs a phone 555 ms of main-thread work and 1.1 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.

496 KiB JavaScript is shipped twice across bundles.

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

ZenDesk costs a phone 192 ms of main-thread work and 430 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.

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

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

1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

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

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

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

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

Your largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 153 ms to 151 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 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.7 MB in 305 requests on a phone: scripts 3.1 MB (129), other files 868 KiB (123) and images 418 KiB (23). Under 2 MB keeps phones on slow connections fast.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 27 characters: “Le Prunier® Plum Beauty Oil”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

The homepage links to 55 pages on leprunier.com and 7 external pages.

https://leprunier.com/blogs/press has no meta description, so Google writes the search snippet from whatever text it finds.

https://leprunier.com/products/the-plum-beauty-oil-duo, https://leprunier.com/products/plum-beauty-oil and https://leprunier.com/products/plum-beauty-oil-reserve use the same meta description. A description written for each page earns more clicks.

https://leprunier.com/pages/heritage has no <h1> headline, so visitors and search engines get no clear main topic.

https://leprunier.com/products/plum-beauty-oil took over 3 s to send its HTML from our server.

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

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

5 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) Error: Unauthorized”.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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