toto.com.uy website review

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

13 images could be 833 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.

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

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

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

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

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

Google CDN costs a phone 921 ms of main-thread work and 736 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 block the main thread while loading, the longest for 761 ms. During a long task the page ignores taps.

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

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

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

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

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

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

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.

4 KiB could be saved by minifying JavaScript.

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.56 (75th percentile). Good is under 0.1.

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

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

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

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

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

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

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

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

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

Your homepage downloads 4.8 MB in 142 requests on a phone: scripts 2.2 MB (49), images 1.2 MB (35) and fonts 753 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

6 images (545 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.

2 images are downloaded at several times the size a phone draws them, for example 3e743ff3-89b2-4fed-9648-d2ee86d40f87___f2976065afc1b71e5b476 at 1,738 px wide, shown at 390 px. Resized copies would save about 275 KiB.

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

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

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

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

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

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

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

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 on the page fails this check, rated moderate by axe-core.

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

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

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

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

Your meta description is 167 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (ItemList, VideoObject and 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 twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 24 pages on toto.com.uy and 3 external pages.

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.toto.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.toto.com.uy/505, https://www.toto.com.uy/288, https://www.toto.com.uy/1094 and https://www.toto.com.uy/1898 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.toto.com.uy/505, https://www.toto.com.uy/288, https://www.toto.com.uy/1094 and https://www.toto.com.uy/1898 use the same meta description. A description written for each page earns more clicks.

https://www.toto.com.uy/1898 has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.toto.com.uy/sandaliacasualtacoaltoviamarteclara19t/p, https://www.toto.com.uy/sandaliacasualtacoaltoviamartemei14o/p, https://www.toto.com.uy/sandaliacasualtacoaltoviamartealessia4e/p, https://www.toto.com.uy/sandaliacasualdecueromarcodonattihaimi22w/p, https://www.toto.com.uy/sandaliacasualdecueromarcodonattigea15p/p and https://www.toto.com.uy/zapatoparaninosgugablasconvelcro22w/p 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.toto.com.uy/hombre and https://www.toto.com.uy/zapatoparaninosgugablasconvelcro22w/p took over 3 s to send their HTML from our server.

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

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

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

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

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.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

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

Opening the homepage sets 16 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 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.