lepuju.com website review

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

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

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

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

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

8 third-party services load with your homepage (pages.dev, Shopify and Google Tag Manager and others), adding 1.0 MB and 387 ms of main-thread time.

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

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

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

pages.dev costs a phone 171 ms of main-thread work and 363 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.

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

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

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

2 KiB JavaScript is shipped twice across bundles.

Your largest element takes 29.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “【2月中旬入荷次第お届けのご予約】anuke（アンヌーク） Washer Knit Cardigan 62710511.”.

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

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

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

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

Your homepage downloads 7.4 MB in 218 requests on a phone: fonts 4.0 MB (2), images 1.3 MB (33) and scripts 1.1 MB (68). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Frame_1.png at 800 px wide, shown at 190 px. Resized copies would save about 53 KiB.

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

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

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

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

<td> elements in a large <table> do not have table headers. (2 elements).

8 links have no real href, so search engines can't follow them.

Your <h1> is empty.

The homepage links to 510 pages on lepuju.com and 11 external pages.

https://lepuju.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://lepuju.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://lepuju.com/customer_authentication/redirect, https://lepuju.com/en/collections/all, https://lepuju.com/en/collections/baby, https://lepuju.com/en/collections/outer_baby, https://lepuju.com/en/collections/tops_baby and https://lepuju.com/en/collections/bottoms_baby and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://lepuju.com/customer_authentication/redirect and https://lepuju.com/en/collections/shoes_baby have no <h1> headline, so visitors and search engines get no clear main topic.

https://lepuju.com/customer_authentication/redirect took over 3 s to send its HTML from our server.

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

5 of 23 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 “Failed to load resource: the server responded with a status of 404 ()”.

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

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.

The homepage shows no opening hours. If customers visit or call, show when.

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,125 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 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.