Website review, no card needed

jumbo.com.ar logo

jumbo.com.ar website review

Visit site (opens in a new tab)Reviewed 28 October 202653 issues · 91 checks

This review found 53 issues worth fixing on jumbo.com.ar, 23 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
6.5 s2.9 sMay 9Oct 246.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.3 s
May 16, 20263.7 s
May 23, 20263.9 s
May 30, 20264.0 s
Jun 6, 20264.3 s
Jun 13, 20264.1 s
Jun 20, 20263.9 s
Jun 27, 20263.9 s
Jul 4, 20263.9 s
Jul 11, 20263.7 s
Jul 18, 20263.6 s
Jul 25, 20263.7 s
Aug 1, 20263.8 s
Aug 8, 20264.1 s
Aug 15, 20264.6 s
Aug 22, 20265.0 s
Aug 29, 20265.3 s
Sep 5, 20265.5 s
Sep 12, 20265.5 s
Sep 19, 20265.6 s
Sep 26, 20265.7 s
Oct 3, 20265.9 s
Oct 10, 20266.1 s
Oct 17, 20266.0 s
Oct 24, 20266.0 s
Real-visitor tap response (INP)75th percentile, phones
618 ms215 msMay 9Oct 24261 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026548 ms
May 16, 2026518 ms
May 23, 2026529 ms
May 30, 2026551 ms
Jun 6, 2026551 ms
Jun 13, 2026571 ms
Jun 20, 2026539 ms
Jun 27, 2026506 ms
Jul 4, 2026469 ms
Jul 11, 2026453 ms
Jul 18, 2026432 ms
Jul 25, 2026394 ms
Aug 1, 2026389 ms
Aug 8, 2026373 ms
Aug 15, 2026353 ms
Aug 22, 2026345 ms
Aug 29, 2026326 ms
Sep 5, 2026300 ms
Sep 12, 2026293 ms
Sep 19, 2026288 ms
Sep 26, 2026284 ms
Oct 3, 2026283 ms
Oct 10, 2026278 ms
Oct 17, 2026263 ms
Oct 24, 2026261 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 jumbo.com.ar (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. jumbo.com.ar at 1.1 s1.1 s
  2. jumbo.com.ar at 2.3 s2.3 s
  3. jumbo.com.ar at 3.4 s3.4 s
  4. jumbo.com.ar at 4.6 s4.6 s
  5. jumbo.com.ar at 5.7 s5.7 s
  6. jumbo.com.ar at 6.9 s6.9 s
  7. jumbo.com.ar at 8.0 s8.0 s
  8. jumbo.com.ar at 9.2 s9.2 s

Speed

14 to fix22
  • Reduce unused JavaScript

    12.4 s · 2.1 MB

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

  • vtexassets.com adds 2.1 s

    2.1 s

    vtexassets.com costs a phone 2.1 s of main-thread work and 3.0 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.

  • Reduce unused CSS

    1.5 s · 201 KiB

    About 201 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Mobile performance score: 22

    22/100

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

  • Main-thread work: 9.8 s

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

  • 3,549 HTML elements

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

  • 8 third-party services on the page

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

  • Use efficient cache lifetimes

    850 ms · 181 KiB

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

  • Google CDN adds 814 ms

    814 ms

    Google CDN costs a phone 814 ms of main-thread work and 1.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.

  • Google Tag Manager adds 791 ms

    791 ms

    Google Tag Manager costs a phone 791 ms of main-thread work and 682 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 356 ms. During a long task the page ignores taps.

  • TikTok adds 307 ms

    307 ms

    TikTok costs a phone 307 ms of main-thread work and 274 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.

  • Improve image delivery

    255 KiB

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

  • storyly.io adds 60 ms

    60 ms

    storyly.io costs a phone 60 ms of main-thread work and 947 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.

  • Legacy JavaScript

    150 ms · 46 KiB

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

  • Minify JavaScript

    145 KiB

    145 KiB could be saved by minifying JavaScript.

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 107 ms

    107 ms

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

Core Web Vitals

14 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 LCP: 7.5 s

    7.5 s

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

  • Real-user FCP: 4.4 s

    4.4 s

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

  • Largest Contentful Paint: 33.7 s

    33.7 s

    Your largest element takes 33.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hasta 40% en Almacén, Bebidas y más”.

  • Speed Index: 20.8 s

    20.8 s

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

  • Time to Interactive: 37.8 s

    37.8 s

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

  • First Contentful Paint: 5.3 s

    5.3 s

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

  • Total Blocking Time: 1.9 s

    1.9 s

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

  • Real-user INP: 304 ms

    304 ms

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

  • Real-user CLS: 0.15

    0.15

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

  • Largest content (LCP) got 71% slower for real visitors

    +71%

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Cumulative Layout Shift: 0.154

    0.154

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

  • 17 images without width and height

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

1 checks passed
  • Tap response (INP) got 51% faster for real visitors

    -51%

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

Images and page weight

1 to fix70
  • Page weight: 7.2 MB in 297 requests

    7.2 MB

    Your homepage downloads 7.2 MB in 297 requests on a phone: scripts 3.6 MB (78), images 1.9 MB (80) and other files 803 KiB (120). Under 2 MB keeps phones on slow connections fast.

  • 7 images below the first screen load straight away

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

  • About 2.0 g of CO₂ per visit

    2.04 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

9 to fixGoogle 8086
  • Images must have alternative text (2 elements)

    Images must have alternative text: 2 elements on the page fail this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 58 tap targets too small

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

  • 41 text elements with low contrast

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

  • Interactive controls must not be nested (2 elements)

    Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

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

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

  • 21 links without text

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

  • 2 form fields without a label

    2 form fields have 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. (13 elements).

1 checks passed
  • 41 automated accessibility rules passed

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

SEO

2 to fixGoogle 9292
  • Structured data has 1 problem

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

  • No XML sitemap

    No XML sitemap at http://janus-edge.vtex.com.br/sitemap.xml?an=jumboargentinaio, 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 set, so this is minor.

  • 591 internal links, 2 external

    The homepage links to 591 pages on jumbo.com.ar and 2 external pages.

6 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “¡Encontrá en Jumbo Online todo lo que necesitás al mejor precio! Aprovechá las Ofertas, Descuentos y Promociones en Pro…”.

  • One H1 headline

    Your main headline reads: “Jumbo | Supermercado Online”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Jumbo Argentina | Aprovechá las Ofertas I Supermercado Online”.

  • Canonical URL set

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

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

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

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.

  • No llms.txt

    There is no https://www.jumbo.com.ar/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Text is in the HTML

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

Other pages

5 to fix67
  • 2 pages without a title

    https://www.jumbo.com.ar/55707 and https://www.jumbo.com.ar/65337 have no <title>, so Google invents the link text in results.

  • 12 linked pages hidden from search

    https://www.jumbo.com.ar/55566, https://www.jumbo.com.ar/actualiza-chrome, https://www.jumbo.com.ar/65548, https://www.jumbo.com.ar/65549, https://www.jumbo.com.ar/65550 and https://www.jumbo.com.ar/65551 and 6 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://www.jumbo.com.ar/55707 and https://www.jumbo.com.ar/65337 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages share a meta description

    https://www.jumbo.com.ar/55566, https://www.jumbo.com.ar/actualiza-chrome, https://www.jumbo.com.ar/65548, https://www.jumbo.com.ar/65549, https://www.jumbo.com.ar/65550 and https://www.jumbo.com.ar/65551 and 6 others use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://www.jumbo.com.ar/55566, https://www.jumbo.com.ar/actualiza-chrome, https://www.jumbo.com.ar/cybermonday, https://www.jumbo.com.ar/55707, https://www.jumbo.com.ar/65548 and https://www.jumbo.com.ar/65549 and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 pages slow to respond

    https://www.jumbo.com.ar/55566, https://www.jumbo.com.ar/actualiza-chrome, https://www.jumbo.com.ar/55707, https://www.jumbo.com.ar/65548, https://www.jumbo.com.ar/65549 and https://www.jumbo.com.ar/65550 and 5 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

Best practices

2 to fixGoogle 9287
  • 43 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Unexpected end of JSON input JSON.parse (<anonymous>)”.

  • 1 low-resolution image

    1 image is 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

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: 1 trust badge. 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 496 words of copy

    The homepage carries about 496 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Hotjar and TikTok Pixel.

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, Hotjar and TikTok Pixel (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.

  • 34 cookies set on arrival

    34

    Opening the homepage sets 34 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.

  • 30 other companies contacted

    Loading the homepage contacts 30 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 jumbo.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

Analytics
Google Tag Manager | Hotjar
Hosting
AWS

Company

Founded
1976
Headquarters
Santiago

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 jumbo.com.ar, including 28 speed issues, 2 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