tata.com.uy website review

Google Tag Manager costs a phone 2.0 s of main-thread work and 1.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.

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Insider and others), adding 1.8 MB and 4.0 s of main-thread time.

62 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

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

About 820 KiB of JavaScript is downloaded but never used on this page.

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.

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

Insider costs a phone 446 ms of main-thread work and 125 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.

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

Privy costs a phone 397 ms of main-thread work and 147 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.

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

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

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

About 11 KiB of CSS is downloaded but never applied on this page.

Desktop scores 61 but mobile only 36. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 6.3 MB in 209 requests on a phone: images 4.0 MB (94), scripts 2.1 MB (37) and other files 155 KiB (71). Under 2 MB keeps phones on slow connections fast.

2 images (280 KiB) 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.

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

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

1 dropdown has no label.

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

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

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

4 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. (64 elements).

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

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

Your title is only 4 characters: “TaTa”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 18 characters: “TaTauy SuperMarket”. 70 to 160 characters is enough to sell the click.

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

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

No XML sitemap at https://tata.com.uy/sitemap/sitemap-index.xml, so Google discovers your pages only by following links.

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

The homepage links to 37 pages on tata.com.uy and 27 external pages.

A phone browser shows 937 words, but the HTML your server sends has only 160. 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.

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.

There is no https://www.tata.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.

https://www.tata.com.uy/lp/politica-de-privacidad has no <title>, so Google invents the link text in results.

/, https://www.tata.com.uy/multiahorro, https://www.tata.com.uy/nuestrasmarcas, https://www.tata.com.uy/programa-puntos-plus, https://www.tata.com.uy/beneficios-y-promociones and https://www.tata.com.uy/cambios-devoluciones and 3 others all use the title “TaTa”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.tata.com.uy/lp/politica-de-privacidad has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.tata.com.uy/multiahorro, https://www.tata.com.uy/coleccion/8728, https://www.tata.com.uy/pequenos-electrodomesticos, https://www.tata.com.uy/coleccion/7758, https://www.tata.com.uy/nuestrasmarcas and https://www.tata.com.uy/coleccion/6463 and 7 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.tata.com.uy/coleccion/8728, whose canonical is https://www.tata.com.uy/undefined. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.tata.com.uy/multiahorro, https://www.tata.com.uy/nuestrasmarcas, https://www.tata.com.uy/lp/politica-de-privacidad, https://www.tata.com.uy/programa-puntos-plus, https://www.tata.com.uy/beneficios-y-promociones and https://www.tata.com.uy/cambios-devoluciones and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.tata.com.uy/multiahorro, https://www.tata.com.uy/coleccion/8728, https://www.tata.com.uy/pequenos-electrodomesticos, https://www.tata.com.uy/coleccion/7758, https://www.tata.com.uy/nuestrasmarcas and https://www.tata.com.uy/coleccion/8739 and 6 others 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.

https://www.tata.com.uy/lp/politica-de-privacidad and https://www.tata.com.uy/terminos-y-condiciones took over 3 s to send their HTML from our server.

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

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage carries about 937 words of visible text.

Opening the homepage sets 3 cookies (measured from a US location before any click).

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.

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