lapretofficial.com website review

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

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

About 997 KiB of JavaScript is downloaded but never used on this page.

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

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

8 third-party services load with your homepage (Shopify, Hexton and nfcube.com and others), adding 1.6 MB and 247 ms of main-thread time.

Hexton costs a phone 94 ms of main-thread work and 1.2 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.

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

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

Shopify costs a phone 119 ms of main-thread work and 320 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 long task block the main thread while loading, the longest for 86 ms. During a long task the page ignores taps.

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

7 KiB could be saved by minifying JavaScript.

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

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

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

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

Your homepage downloads 5.2 MB in 330 requests on a phone: images 2.3 MB (41), scripts 1.6 MB (55) and other files 1.1 MB (196). Under 2 MB keeps phones on slow connections fast.

31 images (2.2 MB) are 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_e6777a95-b70e-4710-9bff-8dc4012b96a4.webp 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.47 g of CO₂e: 175.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 15 characters: “Lapret Official”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“” and “Join Our Community”). One clear main headline is easier for people and search engines.

The homepage links to 102 pages on lapretofficial.com and 9 external pages.

https://www.lapretofficial.com/collections/all, https://www.lapretofficial.com/collections/new-arrivals, https://www.lapretofficial.com/policies/shipping-policy, https://www.lapretofficial.com/collections/afternoon-in-lapret, https://www.lapretofficial.com/collections/the-six-dragons and https://www.lapretofficial.com/collections/whispers-of-summer and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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