maxiconsumo.com website review

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

About 1.0 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 5.1 s faster on a phone.

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

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 926 KiB and 1.1 s of main-thread time.

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

Facebook costs a phone 403 ms of main-thread work and 245 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 330 ms. During a long task the page ignores taps.

17 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 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.

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 6.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

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

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

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

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

17 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-31, real Chrome visitors' tap response (inp) went from 296 ms to 312 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 34.7 MB in 451 requests on a phone: images 30.4 MB (97), scripts 2.4 MB (272) and stylesheets 1.1 MB (12). Under 2 MB keeps phones on slow connections fast.

21 images weigh 21.1 MB together. On a phone connection a single image that size takes seconds.

40 images (27.0 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.

1 image is downloaded at several times the size a phone draws it, for example Black_Week_2025-02.png at 5,707 px wide, shown at 140 px. Resized copies would save about 231 KiB.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 image has no alt text, which hurts accessibility and image search.

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 32 characters: “Maxiconsumo. Tu sucursal online.”. 70 to 160 characters is enough to sell the click.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.maxiconsumo.com/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 687 pages on maxiconsumo.com and 13 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.maxiconsumo.com/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.

/ and https://www.maxiconsumo.com/sucursal_moreno all use the title “Home”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.maxiconsumo.com/sucursal_moreno, https://www.maxiconsumo.com/sucursal_moreno/ofertas, https://www.maxiconsumo.com/sucursal_moreno/sucursales, https://www.maxiconsumo.com/sucursal_moreno/empresa, https://www.maxiconsumo.com/sucursal_moreno/giftcards and https://www.maxiconsumo.com/sucursal_moreno/red-minicosto and 9 others use the same meta description. A description written for each page earns more clicks.

https://www.maxiconsumo.com/sucursal_moreno, https://www.maxiconsumo.com/sucursal_moreno/ofertas and https://www.maxiconsumo.com/sucursal_moreno/sucursales have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Chrome logged issues while loading the page (“Content security policy”).

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: 6 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 1,009 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 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.