Website review, no card needed

naldo.com.ar logo

naldo.com.ar website review

Visit site (opens in a new tab)Reviewed 17 November 202653 issues · 91 checks

This review found 53 issues worth fixing on naldo.com.ar, 20 of them high impact, across 91 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.5 s3.6 sMay 30Nov 144.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.7 s
Jun 6, 20263.8 s
Jun 13, 20263.9 s
Jun 20, 20264.0 s
Jun 27, 20264.1 s
Jul 4, 20264.1 s
Jul 11, 20264.1 s
Jul 18, 20264.1 s
Jul 25, 20264.0 s
Aug 1, 20264.0 s
Aug 8, 20264.1 s
Aug 15, 20264.1 s
Aug 22, 20264.1 s
Aug 29, 20264.1 s
Sep 5, 20264.2 s
Sep 12, 20264.0 s
Sep 19, 20264.0 s
Sep 26, 20264.0 s
Oct 3, 20264.0 s
Oct 10, 20264.4 s
Oct 17, 20264.4 s
Oct 24, 20264.4 s
Oct 31, 20264.4 s
Nov 7, 20264.1 s
Nov 14, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
259 ms240 msMay 30Nov 14252 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026255 ms
Jun 6, 2026256 ms
Jun 13, 2026257 ms
Jun 20, 2026255 ms
Jun 27, 2026253 ms
Jul 4, 2026248 ms
Jul 11, 2026246 ms
Jul 18, 2026244 ms
Jul 25, 2026244 ms
Aug 1, 2026243 ms
Aug 8, 2026242 ms
Aug 15, 2026244 ms
Aug 22, 2026243 ms
Aug 29, 2026244 ms
Sep 5, 2026245 ms
Sep 12, 2026248 ms
Sep 19, 2026250 ms
Sep 26, 2026250 ms
Oct 3, 2026252 ms
Oct 10, 2026246 ms
Oct 17, 2026247 ms
Oct 24, 2026247 ms
Oct 31, 2026247 ms
Nov 7, 2026251 ms
Nov 14, 2026252 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 naldo.com.ar (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. naldo.com.ar at 4.3 s4.3 s
  2. naldo.com.ar at 8.6 s8.6 s
  3. naldo.com.ar at 12.9 s12.9 s
  4. naldo.com.ar at 17.2 s17.2 s
  5. naldo.com.ar at 21.6 s21.6 s
  6. naldo.com.ar at 25.9 s25.9 s
  7. naldo.com.ar at 30.2 s30.2 s
  8. naldo.com.ar at 34.5 s34.5 s

Speed

10 to fix53
  • Reduce unused JavaScript

    3.0 s · 571 KiB

    About 571 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.

  • Use efficient cache lifetimes

    2.7 s · 405 KiB

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

  • Improve image delivery

    3.3 MB

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

  • 8 third-party services on the page

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

  • vtexassets.com adds 589 ms

    589 ms

    vtexassets.com costs a phone 589 ms of main-thread work and 4.4 MB 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.

  • Mobile performance score: 53

    53/100

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

  • Reduce unused CSS

    600 ms · 98 KiB

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

  • Google Tag Manager adds 391 ms

    391 ms

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

  • Main-thread work: 3.5 s

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

  • Render-blocking requests

    300 ms

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

  • Legacy JavaScript

    150 ms · 47 KiB

    Polyfills for old browsers add 47 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 6 long tasks on the main thread

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

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 19 ms

    19 ms

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

Core Web Vitals

9 to fix67
  • 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.

  • Largest Contentful Paint: 24.0 s

    24.0 s

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

  • Speed Index: 39.9 s

    39.9 s

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

  • Time to Interactive: 24.7 s

    24.7 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Real-user INP: 257 ms

    257 ms

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Total Blocking Time: 302 ms

    302 ms

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

  • 22 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

4 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user CLS: 0.07

    0.07

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

  • Real-user TTFB: 714 ms

    714 ms

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

  • Cumulative Layout Shift: 0.005

    0.005

    The layout barely moves while loading (CLS 0.005, good is under 0.1).

Images and page weight

4 to fix36
  • Page weight: 5.6 MB in 152 requests

    5.6 MB

    Your homepage downloads 5.6 MB in 152 requests on a phone: images 3.5 MB (44), scripts 1.7 MB (49) and HTML 149 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 1.8 MB together. On a phone connection a single image that size takes seconds.

  • An image on the first screen is lazy-loaded

    3f37ddf5-7dee-4aa5-ac8d-2ce0a832afcc___deb83e3d789f381793316 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).

  • 3 images far larger than shown

    310 KiB

    3 images are downloaded at several times the size a phone draws them, for example e0d78c29-4fe2-4638-a84c-e87cd0e689e6___d688e894a031a5bc38319 at 1,285 px wide, shown at 390 px. Resized copies would save about 310 KiB.

  • About 1.6 g of CO₂ per visit

    1.58 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

10 to fixGoogle 6584
  • ARIA attributes must conform to valid values (8 elements)

    ARIA attributes must conform to valid values: 8 elements on the page fail this check, rated critical by axe-core.

  • 2 buttons without a name

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

  • 9 tap targets too small

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

  • Positive tabindex

    7 elements have a tabindex above 0, which scrambles the keyboard order.

  • 3 text elements with low contrast

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

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 9 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.

  • 8 links without text

    8 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. (1 element).

2 checks passed
  • Every image has alt text

    All 18 images in the HTML carry an alt attribute.

  • 38 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: 38 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9279
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Structured data has 1 problem

    Structured data found (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.

  • No XML sitemap

    No XML sitemap at https://www.MiTienda.com.br/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

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

  • 16 internal links, 1 external

    The homepage links to 16 pages on naldo.com.ar and 1 external page.

4 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “¿Buscás ofertas en electrodomésticos? ⭐️ Descubrí los mejores precios en Naldo. Las mejores marcas de electrodomésticos…”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Naldo | Electrodomésticos, tecnología y artículos para el hogar”.

  • Canonical URL set

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

  • robots.txt in place

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

AI search readiness

1 to fix83
  • 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.

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

  • llms.txt published

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

Other pages

5 to fix55
  • 1 linked page is broken

    Your homepage links to https://www.naldo.com.ar/climatizacion/aires-acondicionados/ventiladores, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 4 linked pages hidden from search

    https://www.naldo.com.ar/487, https://www.naldo.com.ar/847, https://www.naldo.com.ar/688 and https://www.naldo.com.ar/neo%205 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 3 pages share a title

    /, https://www.naldo.com.ar/credito-personal and https://www.naldo.com.ar/dinerar all use the title “Naldo | Electrodomésticos, tecnología y artículos para el hogar”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages share a meta description

    https://www.naldo.com.ar/487, https://www.naldo.com.ar/credito-personal, https://www.naldo.com.ar/847, https://www.naldo.com.ar/688, https://www.naldo.com.ar/hp and https://www.naldo.com.ar/neo%205 and 1 other use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://www.naldo.com.ar/credito-personal and https://www.naldo.com.ar/dinerar have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.naldo.com.ar/dinerar has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 8 pages slow to respond

    https://www.naldo.com.ar/487, https://www.naldo.com.ar/hogar-jardin-y-tiempo-libre/jardin/piletas, https://www.naldo.com.ar/credito-personal, https://www.naldo.com.ar/847, https://www.naldo.com.ar/hp and https://www.naldo.com.ar/neo%205 and 2 others took over 3 s to send their HTML from our server.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 11 pages that loaded have a meta description.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

4 to fixGoogle 8870
  • 3 broken images

    3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=97127455&tm=gtm002&Ver=2&mid=bb81b377-de31-47cd-975d-4578bee46a4f&bo=1&sid=a9809750e23611f1a6b40bb48c980889&vid=a980e990e23611f1a5eb0f72e07aba15&vids=1&msclkid=N&gtm_t.

  • 16 small tap targets

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

  • 4 JavaScript errors while loading

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

  • 10 distorted images

    10 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 7 low-resolution images

    7 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • 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: 1 customer or partner logo. 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.

  • Only about 73 words

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

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 cookies (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.

  • 24 other companies contacted

    Loading the homepage contacts 24 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 naldo.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
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 53 issues on naldo.com.ar, including 19 speed issues, 4 SEO issues and 5 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