Website review, no card needed

eldorado.com.uy logo

eldorado.com.uy website review

Visit site (opens in a new tab)Reviewed 27 October 202654 issues · 92 checks

This review found 54 issues worth fixing on eldorado.com.uy, 27 of them high impact, across 92 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.9 s4.4 sMay 9Oct 244.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.8 s
May 16, 20264.7 s
May 23, 20264.7 s
May 30, 20264.7 s
Jun 6, 20264.7 s
Jun 13, 20264.8 s
Jun 20, 20264.8 s
Jun 27, 20264.8 s
Jul 4, 20264.8 s
Jul 11, 20264.8 s
Jul 18, 20264.8 s
Jul 25, 20264.8 s
Aug 1, 20264.7 s
Aug 8, 20264.7 s
Aug 15, 20264.6 s
Aug 22, 20264.5 s
Aug 29, 20264.5 s
Sep 5, 20264.5 s
Sep 12, 20264.6 s
Sep 19, 20264.6 s
Sep 26, 20264.6 s
Oct 3, 20264.6 s
Oct 10, 20264.7 s
Oct 17, 20264.7 s
Oct 24, 20264.8 s
Real-visitor tap response (INP)75th percentile, phones
947 ms244 msMay 9Oct 24670 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026866 ms
May 16, 2026790 ms
May 23, 2026730 ms
May 30, 2026720 ms
Jun 6, 2026610 ms
Jun 13, 2026488 ms
Jun 20, 2026371 ms
Jun 27, 2026325 ms
Jul 4, 2026326 ms
Jul 11, 2026355 ms
Jul 18, 2026385 ms
Jul 25, 2026408 ms
Aug 1, 2026404 ms
Aug 8, 2026408 ms
Aug 15, 2026442 ms
Aug 22, 2026465 ms
Aug 29, 2026510 ms
Sep 5, 2026540 ms
Sep 12, 2026553 ms
Sep 19, 2026569 ms
Sep 26, 2026587 ms
Oct 3, 2026669 ms
Oct 10, 2026732 ms
Oct 17, 2026719 ms
Oct 24, 2026670 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 eldorado.com.uy (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. eldorado.com.uy at 1.0 s1.0 s
  2. eldorado.com.uy at 1.9 s1.9 s
  3. eldorado.com.uy at 2.9 s2.9 s
  4. eldorado.com.uy at 3.9 s3.9 s
  5. eldorado.com.uy at 4.8 s4.8 s
  6. eldorado.com.uy at 5.8 s5.8 s
  7. eldorado.com.uy at 6.7 s6.7 s
  8. eldorado.com.uy at 7.7 s7.7 s

Speed

14 to fix13
  • Reduce unused JavaScript

    5.5 s · 987 KiB

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

  • vtexassets.com adds 2.2 s

    2.2 s

    vtexassets.com costs a phone 2.2 s of main-thread work and 3.1 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.1 s · 204 KiB

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

  • Mobile performance score: 13

    13/100

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

  • Main-thread work: 8.5 s

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

  • 6,255 HTML elements

    The page has 6,255 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 Tag Manager and Google CDN and others), adding 4.7 MB and 3.4 s of main-thread time.

  • Use efficient cache lifetimes

    750 ms · 327 KiB

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

  • Improve image delivery

    450 ms · 399 KiB

    8 images could be 399 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Render-blocking requests

    600 ms

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

  • Google Tag Manager adds 448 ms

    448 ms

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

    450 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 450 ms faster on a phone.

  • Google CDN adds 331 ms

    331 ms

    Google CDN costs a phone 331 ms of main-thread work and 737 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 321 ms. During a long task the page ignores taps.

  • Minify JavaScript

    150 ms · 6 KiB

    6 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

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

  • 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: 28 ms

    28 ms

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

Core Web Vitals

12 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: 5.2 s

    5.2 s

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

  • Real-user INP: 1.7 s

    1.7 s

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

  • Real-user CLS: 0.89

    0.89

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

  • First Contentful Paint: 11.3 s

    11.3 s

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

  • Largest Contentful Paint: 20.0 s

    20.0 s

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

  • Time to Interactive: 25.6 s

    25.6 s

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

  • Cumulative Layout Shift: 0.785

    0.785

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

  • Speed Index: 11.3 s

    11.3 s

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

  • Total Blocking Time: 762 ms

    762 ms

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

  • Real-user FCP: 2.6 s

    2.6 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Largest content (LCP) held steady for real visitors

    0%

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

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

    -16%

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

Images and page weight

3 to fix53
  • Page weight: 4.7 MB in 329 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 329 requests on a phone: scripts 2.5 MB (54), other files 739 KiB (219) and fonts 540 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    177 KiB

    1 image is downloaded at several times the size a phone draws it, for example 8a7c99a8-1255-4611-8ff8-9e5d2a44547c___31b3ec71d7e84d0b05540 at 2,250 px wide, shown at 32 px. Resized copies would save about 177 KiB.

  • 7 images below the first screen load straight away

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

  • About 1.3 g of CO₂ per visit

    1.32 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.32 g of CO₂e: 158.7 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

12 to fixGoogle 7583
  • Images must have alternative text (8 elements)

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

  • 7 buttons without a name

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

  • Hidden but focusable

    55 elements hidden from screen readers can still receive keyboard focus.

  • 20 tap targets too small

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

  • 5 text elements with low contrast

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

  • 118 form fields without a label

    118 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 10 links without text

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

  • Alternative text of images should not be repeated as text (8 elements)

    Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.

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

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

1 checks passed
  • 39 automated accessibility rules passed

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

SEO

3 to fixGoogle 9283
  • 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 X (Twitter) card tag

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

  • 5 internal links, 1 external

    The homepage links to 5 pages on eldorado.com.uy and 1 external page.

5 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “Prepara tus comidas con productos de primera calidad. Los precios más convenientes con la más grande variedad de artícu…”.

  • Title: 40 characters

    Your title is a healthy 40 characters: “El Dorado Supermercado Online en Uruguay”.

  • Canonical URL set

    The canonical URL is https://www.eldorado.com.uy/.

  • 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.eldorado.com.uy/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    3%

    A phone browser shows 684 words, but the HTML your server sends has only 22. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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.eldorado.com.uy/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.

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

Other pages

2 to fix93
  • 2 pages share a meta description

    https://www.eldorado.com.uy/stores and https://www.eldorado.com.uy/como-comprar use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://www.eldorado.com.uy/stores, https://www.eldorado.com.uy/nuestros-catalogos, https://www.eldorado.com.uy/como-comprar and https://www.eldorado.com.uy/ofertas have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://www.eldorado.com.uy/stores, https://www.eldorado.com.uy/nuestros-catalogos, https://www.eldorado.com.uy/como-comprar and https://www.eldorado.com.uy/ofertas have 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.

  • 2 pages slow to respond

    https://www.eldorado.com.uy/nuestros-catalogos and https://www.eldorado.com.uy/como-comprar took over 3 s to send their HTML from our server.

  • 4 internal pages checked

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

6 checks passed
  • Linked pages load

    All 4 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 4 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 4 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “[Minicart App] Can't make request to 'https://www.eldorado.com.uy/api/seller-register/pvt/sellers' outside 'myvtex.com' domain”.

2 checks passed
  • Tap targets are thumb-sized

    211 of 239 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix30
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 684 words of copy

    The homepage carries about 684 words of visible text.

1 checks passed
  • Analytics in place

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

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 2 mores (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.

  • 25 cookies set on arrival

    25

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

  • 34 other companies contacted

    Loading the homepage contacts 34 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 eldorado.com.uy, 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 | Hotjar
Hosting
CloudFront

Company

Founded
1929

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 54 issues on eldorado.com.uy, including 26 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