lippioutdoor.com website review

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

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

8 third-party services load with your homepage (POWr, Google Tag Manager and Clarity and others), adding 1.7 MB and 1.8 s of main-thread time.

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

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

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

POWr costs a phone 753 ms of main-thread work and 13 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.

Google Tag Manager costs a phone 490 ms of main-thread work and 813 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.

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

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

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

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

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

7 KiB JavaScript is shipped twice across bundles.

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.

4 KiB could be saved by minifying CSS.

2 KiB could be saved by minifying JavaScript.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

Your largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Desbloquea descuentos en el carrito”.

The first text or image appears after 3.1 s on a phone. Good is under 1.8 s.

Real visitors wait 266 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 60.1 MB in 472 requests on a phone: media 53.6 MB (16), images 2.9 MB (48) and scripts 2.0 MB (101). Under 2 MB keeps phones on slow connections fast.

13 images are downloaded at several times the size a phone draws them, for example puelo_0014_puelo-cs-hi-negro-uva_0028_ok-08cdf5fe-a573-4c2e- at 1,500 px wide, shown at 160 px. Resized copies would save about 1.6 MB.

19 images further down the page (2.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

m-glaciar-sherpa-pro-jacket-42_0001_capa-2-58b7e710-f0b5-4e4 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).

5 images (818 KiB) 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.

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

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There are 4 <h1> headlines (“”, “” and “”). One clear main headline is easier for people and search engines.

The homepage links to 433 pages on lippioutdoor.com and 11 external pages.

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

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

https://www.lippioutdoor.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.lippioutdoor.com/pages/terminos-y-condiciones, https://www.lippioutdoor.com/pages/politicas-de-privacidad, https://www.lippioutdoor.com/collections/softshell-hombre and https://www.lippioutdoor.com/collections/top-hombre use the same meta description. A description written for each page earns more clicks.

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

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

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

Chrome logged issues while loading the page (“Cookie”).

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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 23 cookies, 2 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 41 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.