tony.com.mx website review

17 images could be 4.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 13.2 s faster on a phone.

93 files are served with short cache lifetimes, so returning visitors download them again (3.0 MB).

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

31 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.

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

A phone's processor spends 6.7 s on main-thread work while loading, 3.5 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 20.7 MB and 2.7 s of main-thread time.

vtexassets.com costs a phone 945 ms of main-thread work and 15.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 costs a phone 876 ms of main-thread work and 1.0 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 CDN costs a phone 440 ms of main-thread work and 743 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 349 ms. During a long task the page ignores taps.

Other Google APIs/SDKs costs a phone 33 ms of main-thread work and 2.9 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.

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

About 78 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.

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

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.

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

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

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

Your largest element takes 32.5 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 35.6 s. Good is under 3.8 s.

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

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

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

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

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

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

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

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

Your homepage downloads 11.6 MB in 286 requests on a phone: images 7.6 MB (126), scripts 3.0 MB (60) and other files 496 KiB (56). Under 2 MB keeps phones on slow connections fast.

31 images are downloaded at several times the size a phone draws them, for example 346ee62c-8e71-45be-b9d8-0f6abe72e9c5___ac9d96017510a777b01a3 at 6,667 px wide, shown at 350 px. Resized copies would save about 10.1 MB.

7 images weigh 8.5 MB together. On a phone connection a single image that size takes seconds.

31 images (4.4 MB) 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.

30 images further down the page (2.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

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

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

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

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

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

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

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

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

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://www.MiTienda.com.br/sitemap.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 29 pages on tony.com.mx and 8 external pages.

A phone browser shows 917 words, but the HTML your server sends has only 186. 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.tony.com.mx/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.tony.com.mx/ubica-tu-sucursal has no <title>, so Google invents the link text in results.

https://www.tony.com.mx/260 and https://www.tony.com.mx/273 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/ and https://www.tony.com.mx/electr%C3%B3nica/audio all use the title “TONY Superpapelerías | Tienda en Linea”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.tony.com.mx/ubica-tu-sucursal has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.tony.com.mx/260, https://www.tony.com.mx/wishlist, https://www.tony.com.mx/electr%C3%B3nica/audio and https://www.tony.com.mx/273 use the same meta description. A description written for each page earns more clicks.

https://www.tony.com.mx/ubica-tu-sucursal and https://www.tony.com.mx/wishlist have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.tony.com.mx/electr%C3%B3nica/audio, https://www.tony.com.mx/papel and https://www.tony.com.mx/escolar/escritura took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://tonypapelerias.vtexassets.com/arquivos/1200x600paypal-01.svg.

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

4 errors were logged to the browser console while the page loaded, for example “Cannot destructure property 'store' of '(intermediate value)' as it is undefined.”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Large scripts ship without source maps.

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 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 917 words of visible text.

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