Website review, no card needed

liliana.com.ar logo

liliana.com.ar website review

Visit site (opens in a new tab)Reviewed 26 October 202655 issues · 96 checks

This review found 55 issues worth fixing on liliana.com.ar, 20 of them high impact, across 96 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.1 s3.6 sMay 2Oct 173.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.1 s
May 9, 20264.0 s
May 16, 20263.9 s
May 23, 20263.9 s
May 30, 20263.9 s
Jun 6, 20263.9 s
Jun 13, 20263.9 s
Jun 20, 20263.8 s
Jun 27, 20263.8 s
Jul 4, 20263.7 s
Jul 11, 20263.6 s
Jul 18, 20263.6 s
Jul 25, 20263.6 s
Aug 1, 20263.7 s
Aug 8, 20263.8 s
Aug 15, 20263.8 s
Aug 22, 20263.9 s
Aug 29, 20263.9 s
Sep 5, 20263.9 s
Sep 12, 20264.0 s
Sep 19, 20263.9 s
Sep 26, 20264.0 s
Oct 3, 20264.0 s
Oct 10, 20263.9 s
Oct 17, 20263.8 s
Real-visitor tap response (INP)75th percentile, phones
438 ms326 msMay 2Oct 17421 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026387 ms
May 9, 2026375 ms
May 16, 2026355 ms
May 23, 2026341 ms
May 30, 2026340 ms
Jun 6, 2026339 ms
Jun 13, 2026350 ms
Jun 20, 2026366 ms
Jun 27, 2026370 ms
Jul 4, 2026375 ms
Jul 11, 2026374 ms
Jul 18, 2026370 ms
Jul 25, 2026371 ms
Aug 1, 2026370 ms
Aug 8, 2026373 ms
Aug 15, 2026372 ms
Aug 22, 2026366 ms
Aug 29, 2026373 ms
Sep 5, 2026380 ms
Sep 12, 2026391 ms
Sep 19, 2026411 ms
Sep 26, 2026417 ms
Oct 3, 2026419 ms
Oct 10, 2026425 ms
Oct 17, 2026421 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of liliana.com.ar (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. liliana.com.ar at 1.0 s1.0 s
  2. liliana.com.ar at 2.1 s2.1 s
  3. liliana.com.ar at 3.1 s3.1 s
  4. liliana.com.ar at 4.2 s4.2 s
  5. liliana.com.ar at 5.2 s5.2 s
  6. liliana.com.ar at 6.2 s6.2 s
  7. liliana.com.ar at 7.3 s7.3 s
  8. liliana.com.ar at 8.3 s8.3 s

Speed

15 to fix12
  • Reduce unused JavaScript

    1.4 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • vtexassets.com adds 1.1 s

    1.1 s

    vtexassets.com costs a phone 1.1 s of main-thread work and 4.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 12

    12/100

    Your mobile performance score is 12 (desktop: 29). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.6 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (vtexassets.com, YouTube and Google Tag Manager and others), adding 6.8 MB and 2.8 s of main-thread time.

  • Use efficient cache lifetimes

    800 ms · 600 KiB

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

  • Improve image delivery

    1.2 MB

    9 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • YouTube adds 560 ms

    560 ms

    YouTube costs a phone 560 ms of main-thread work and 978 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.

  • Reduce unused CSS

    450 ms · 195 KiB

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

  • Google Tag Manager adds 554 ms

    554 ms

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

  • Font display

    550 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 550 ms).

  • Facebook adds 325 ms

    325 ms

    Facebook costs a phone 325 ms of main-thread work and 270 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.

  • 20 long tasks on the main thread

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

  • Render-blocking requests

    300 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

  • 1,565 HTML elements

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

  • Minify JavaScript

    26 KiB

    26 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    12 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 226 ms

    226 ms

    Your server sent the HTML in 226 ms, well inside Google's 600 ms guideline.

Core Web Vitals

13 to fix0
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user INP: 516 ms

    516 ms

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

  • Real-user CLS: 0.48

    0.48

    For real visitors the layout shifts by 0.48 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 16.5 s

    16.5 s

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

  • Time to Interactive: 36.9 s

    36.9 s

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

  • Speed Index: 11.6 s

    11.6 s

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

  • First Contentful Paint: 5.6 s

    5.6 s

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

  • Cumulative Layout Shift: 0.497

    0.497

    The layout shifts by 0.497 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Real-user LCP: 3.1 s

    3.1 s

    Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 2.1 s

    2.1 s

    Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 968 ms

    968 ms

    Real visitors wait 968 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • 23 images without width and height

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

  • Tap response (INP) got 11% slower for real visitors

    +11%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

Images and page weight

6 to fix29
  • Page weight: 6.2 MB in 169 requests

    6.2 MB

    Your homepage downloads 6.2 MB in 169 requests on a phone: scripts 2.9 MB (59), images 1.6 MB (26) and fonts 857 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    3ab09d8b-f214-4609-ad8f-e5a6c7f36b74___51c8646e7823542b6fc9e weighs 726 KiB. On a phone connection a single image that size takes seconds.

  • 2 images in older formats

    2 images (1.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.

  • An image on the first screen is lazy-loaded

    61f48f69-4290-48ef-926c-05c9381844ed___b899f35055597f799ff38 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 far larger than shown

    323 KiB

    1 image is downloaded at several times the size a phone draws it, for example b5105bb5-3c58-4d92-8416-0b72b951a55a___89a857e370c5708151042 at 1,920 px wide, shown at 358 px. Resized copies would save about 323 KiB.

  • 2 images below the first screen load straight away

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

  • About 1.8 g of CO₂ per visit

    1.77 g

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

Accessibility

7 to fixGoogle 8490
  • 3 buttons without a name

    3 buttons have no accessible name, so screen readers announce just “button”.

  • 27 tap targets too small

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

  • 26 text elements with low contrast

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

  • All page content should be contained by landmarks (22 elements)

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • 2 links without text

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

  • 1 form field without a label

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (7 elements).

2 checks passed
  • Every image has alt text

    All 40 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 6 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9291
  • Structured data has 1 problem

    Structured data found (ItemList and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 77 internal links, 0 external

    The homepage links to 77 pages on liliana.com.ar and 0 external pages.

6 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Descubrí los mejores electrodomésticos para tu cocina y hogar. Encontrá en Liliana ventiladores, calefactores, aspirado…”.

  • One H1 headline

    Your main headline reads: “¡Viví tus Electros en Modo Hot!”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Tienda Oficial Liliana - Electrodomésticos para tu vida”.

  • Canonical URL set

    The canonical URL is https://www.liliana.com.ar/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.liliana.com.ar/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (526 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.liliana.com.ar/llms.txt (2 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 3 linked pages hidden from search

    https://www.liliana.com.ar/230, https://www.liliana.com.ar/212 and https://www.liliana.com.ar/228 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 3 pages share a meta description

    https://www.liliana.com.ar/230, https://www.liliana.com.ar/212 and https://www.liliana.com.ar/228 use the same meta description. A description written for each page earns more clicks.

  • 3 pages slow to respond

    https://www.liliana.com.ar/ventiladores/ventiladores-de-pared, https://www.liliana.com.ar/calefaccion/exterior and https://www.liliana.com.ar/calefaccion/paneles-calefactores took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 6985
  • 24 small tap targets

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

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Error: <svg> attribute width: Expected length, "auto".”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • No call to action on the first screen

    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 calls to action

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

  • Thin social proof

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

  • No direct contact details

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 315 words of copy

    The homepage carries about 315 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel 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.

  • 23 cookies set on arrival

    23

    Opening the homepage sets 23 cookies, 1 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 40 other companies contacted

    Loading the homepage contacts 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at liliana.com.ar, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
React
Analytics
Google Tag Manager | Microsoft Clarity

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 55 issues on liliana.com.ar, including 28 speed issues, 3 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25