limabrand.es website review

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

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

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

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

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

5 third-party services load with your homepage (pop-convert.com, Shopify and widgetic.com and others), adding 458 KiB and 359 ms of main-thread time.

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

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

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

About 119 KiB of JavaScript is downloaded but never used 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 8.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ENVÍOS GRATUITOS POR COMPRAS SUPERIORES A 55€”.

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

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

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 34.2 MB in 289 requests on a phone: media 29.5 MB (2), images 3.0 MB (39) and other files 879 KiB (126). Under 2 MB keeps phones on slow connections fast.

8F8964F8-CCFB-4197-8068-53DA0E91FE65.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).

9 images further down the page (689 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

3 tap targets are too small or too close together to hit reliably with a finger.

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 24 characters: “Lima Jewels – LIMA BRAND”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 31 characters: “Lifestyle brand of jewellery :)”. 70 to 160 characters is enough to sell the click.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 151 pages on limabrand.es and 2 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), 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://limabrand.es/collections/ropa, https://limabrand.es/collections/collares, https://limabrand.es/collections/collares-dorados-1, https://limabrand.es/collections/collares-especiales, https://limabrand.es/collections/collares-dorados and https://limabrand.es/collections/pendientes-1 and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://limabrand.es/collections/ropa, https://limabrand.es/collections/collares, https://limabrand.es/collections/collares-dorados-1, https://limabrand.es/collections/collares-especiales, https://limabrand.es/collections/collares-dorados and https://limabrand.es/collections/pendientes-1 and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

The homepage has only about 205 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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