leonisa.pe website review

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

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

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

8 third-party services load with your homepage (Clarity, Shopify and Klaviyo and others), adding 1.3 MB and 785 ms of main-thread time.

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

Clarity costs a phone 430 ms of main-thread work and 30 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 285 ms. During a long task the page ignores taps.

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

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

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

About 56 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 290 ms faster on a phone.

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

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

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

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.

5 KiB could be saved by minifying JavaScript.

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

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

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

4 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 201 ms to 229 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.6 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.8 MB in 433 requests on a phone: other files 1.6 MB (267), images 1.0 MB (72) and scripts 743 KiB (75). Under 2 MB keeps phones on slow connections fast.

bmobile-1-1026n26-oferta-brasier-ref-091054-pe.jpg 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).

1 image further down the page (97 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 1.07 g of CO₂e: 128.7 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”.

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

8 images have no alt text, which hurts accessibility and image search.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 240 pages on leonisa.pe and 30 external pages.

https://leonisa.pe/pages/bestsellers-leonisa is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://leonisa.pe/pages/lenceria-para-novia has no meta description, so Google writes the search snippet from whatever text it finds.

https://leonisa.pe/pages/bestsellers-leonisa and https://leonisa.pe/pages/lenceria-para-novia have no <h1> headline, so visitors and search engines get no clear main topic.

https://leonisa.pe/collections/brasieres-push-ups-realce, https://leonisa.pe/collections/brasieres-corrector-de-postura and https://leonisa.pe/collections/embarazo-maternidad-postparto took over 3 s to send their HTML from our server.

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

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

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.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

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