Website review, no card needed

disco.com.ar logo

disco.com.ar website review

Visit site (opens in a new tab)Reviewed 3 November 202647 issues · 89 checks

This review found 47 issues worth fixing on disco.com.ar, 21 of them high impact, across 89 checks. The most urgent: vtexassets.com adds 1.5 s. 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.0 s3.8 sMay 16Oct 314.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.1 s
May 23, 20264.3 s
May 30, 20264.5 s
Jun 6, 20264.8 s
Jun 13, 20264.7 s
Jun 20, 20264.7 s
Jun 27, 20264.7 s
Jul 4, 20264.9 s
Jul 11, 20265.0 s
Jul 18, 20265.0 s
Jul 25, 20265.1 s
Aug 1, 20264.9 s
Aug 8, 20264.7 s
Aug 15, 20264.5 s
Aug 22, 20264.2 s
Aug 29, 20264.0 s
Sep 5, 20264.0 s
Sep 12, 20264.2 s
Sep 19, 20264.7 s
Sep 26, 20265.2 s
Oct 3, 20265.8 s
Oct 10, 20265.7 s
Oct 17, 20265.4 s
Oct 24, 20265.2 s
Oct 31, 20264.7 s
Real-visitor tap response (INP)75th percentile, phones
468 ms197 msMay 16Oct 31297 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026395 ms
May 23, 2026400 ms
May 30, 2026415 ms
Jun 6, 2026420 ms
Jun 13, 2026437 ms
Jun 20, 2026407 ms
Jun 27, 2026371 ms
Jul 4, 2026325 ms
Jul 11, 2026311 ms
Jul 18, 2026299 ms
Jul 25, 2026287 ms
Aug 1, 2026290 ms
Aug 8, 2026288 ms
Aug 15, 2026288 ms
Aug 22, 2026298 ms
Aug 29, 2026304 ms
Sep 5, 2026305 ms
Sep 12, 2026295 ms
Sep 19, 2026273 ms
Sep 26, 2026253 ms
Oct 3, 2026228 ms
Oct 10, 2026228 ms
Oct 17, 2026243 ms
Oct 24, 2026257 ms
Oct 31, 2026297 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 disco.com.ar (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. disco.com.ar at 1.2 s1.2 s
  2. disco.com.ar at 2.4 s2.4 s
  3. disco.com.ar at 3.5 s3.5 s
  4. disco.com.ar at 4.7 s4.7 s
  5. disco.com.ar at 5.9 s5.9 s
  6. disco.com.ar at 7.1 s7.1 s
  7. disco.com.ar at 8.3 s8.3 s
  8. disco.com.ar at 9.5 s9.5 s

Speed

12 to fix24
  • vtexassets.com adds 1.5 s

    1.5 s

    vtexassets.com costs a phone 1.5 s of main-thread work and 2.9 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: 24

    24/100

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

  • Main-thread work: 6.8 s

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

  • 3,367 HTML elements

    The page has 3,367 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/Doubleclick Ads and others), adding 5.8 MB and 2.8 s of main-thread time.

  • Reduce unused JavaScript

    1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    750 ms · 187 KiB

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

  • Google Tag Manager adds 710 ms

    710 ms

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

    150 ms · 562 KiB

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

  • Use efficient cache lifetimes

    472 KiB

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

  • Google/Doubleclick Ads adds 221 ms

    221 ms

    Google/Doubleclick Ads costs a phone 221 ms of main-thread work and 680 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.

  • storyly.io adds 60 ms

    60 ms

    storyly.io costs a phone 60 ms of main-thread work and 935 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 213 ms. During a long task the page ignores taps.

  • Minify JavaScript

    145 KiB

    145 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    57 KiB

    Polyfills for old browsers add 57 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.

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 147 ms

    147 ms

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

Core Web Vitals

12 to fix33
  • 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: 507 ms

    507 ms

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

  • Speed Index: 15.9 s

    15.9 s

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

  • Time to Interactive: 37.0 s

    37.0 s

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

  • Largest Contentful Paint: 6.0 s

    6.0 s

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

  • Total Blocking Time: 923 ms

    923 ms

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Cumulative Layout Shift: 0.336

    0.336

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

  • Real-user LCP: 3.9 s

    3.9 s

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

  • Real-user FCP: 2.7 s

    2.7 s

    Real visitors see the first content after 2.7 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.

  • 28 images without width and height

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

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

    +17%

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

2 checks passed
  • Real-user CLS: 0.08

    0.08

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

  • Tap response (INP) got 30% faster for real visitors

    -30%

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

Images and page weight

3 to fix53
  • Page weight: 6.5 MB in 312 requests

    6.5 MB

    Your homepage downloads 6.5 MB in 312 requests on a phone: scripts 2.9 MB (77), images 2.4 MB (94) and HTML 577 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 21 images below the first screen load straight away

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

  • 1 image far larger than shown

    12 KiB

    1 image is downloaded at several times the size a phone draws it, for example 5a4de78d-8cb2-416a-8aef-e13e318091b9___4246c6eba4cbd30aeda83 at 1,108 px wide, shown at 324 px. Resized copies would save about 12 KiB.

  • 1 image in older formats

    1 image (31 KiB) is 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.

  • About 1.8 g of CO₂ per visit

    1.83 g

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

Accessibility

7 to fixGoogle 8589
  • 68 tap targets too small

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

  • 32 text elements with low contrast

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

  • 11 images without alt text

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

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

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

  • 30 links without text

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

  • 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
  • 43 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: 43 passed and 7 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 9287
  • 7 H1 headlines

    There are 7 <h1> headlines (“Comestibles y Bebidas”, “Frescos y Congelados” and “Perfumería y Limpieza”). One clear main headline is easier for people and search engines.

  • 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=discoargentina, 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.

  • 616 internal links, 2 external

    The homepage links to 616 pages on disco.com.ar and 2 external pages.

5 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “¡En Disco tenemos todo lo que necesitás! Comprá online sin moverte de casa: aprovechá los descuentos y ofertas que Supe…”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Supermercado Disco Online | Todo lo Que Necesitás | CyberMonday”.

  • Canonical URL set

    The canonical URL is https://www.disco.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.disco.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,572 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 13 linked pages hidden from search

    https://www.disco.com.ar/65569, https://www.disco.com.ar/39293, https://www.disco.com.ar/65777, https://www.disco.com.ar/65778, https://www.disco.com.ar/65779 and https://www.disco.com.ar/65776 and 7 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 14 pages share a meta description

    https://www.disco.com.ar/65569, https://www.disco.com.ar/actualiza-chrome, https://www.disco.com.ar/39293, https://www.disco.com.ar/65777, https://www.disco.com.ar/65778 and https://www.disco.com.ar/65779 and 8 others use the same meta description. A description written for each page earns more clicks.

  • 10 pages slow to respond

    https://www.disco.com.ar/39293, https://www.disco.com.ar/65777, https://www.disco.com.ar/65778, https://www.disco.com.ar/65779, https://www.disco.com.ar/65776 and https://www.disco.com.ar/65596 and 4 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 198 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 9271
  • 2 broken images

    2 images failed to load on a phone, for example https://www.disco.com.ar/.

  • 35 small tap targets

    35 of 94 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 “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

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

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

    The homepage carries about 476 words of visible text.

2 checks passed
  • Analytics in place

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

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

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

  • 39 cookies set on arrival

    39

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

  • 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 disco.com.ar, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2020.

Stack

Analytics
Google Tag Manager | Hotjar
Hosting
AWS

Hiring

Hiring
36 open roles
Teams
Sales (7), Product Strategy & Corporate Development (6), Engineering (5), Finance (3)
Job board
greenhouse

Company

Founded
1961
Headquarters
Córdoba

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on disco.com.ar, including 24 speed issues, 3 SEO issues and 3 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