madesa.mx website review

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

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

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

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

15 images could be 5.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, Facebook and goadopt.io and others), adding 1.5 MB and 1.7 s of main-thread time.

About 702 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

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

Google Tag Manager costs a phone 608 ms of main-thread work and 523 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 104 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

5 KiB JavaScript is shipped twice across bundles.

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

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

Your largest element takes 11.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Pareja preparando alimentos en una cocina Madesa. Descuenta…”.

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

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

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

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

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

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

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

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

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

Your homepage downloads 10.0 MB in 342 requests on a phone: images 6.1 MB (73), scripts 2.3 MB (129) and other files 1.2 MB (104). Under 2 MB keeps phones on slow connections fast.

banners_Home_Secundaria-688x487_3.gif weighs 7.3 MB. On a phone connection a single image that size takes seconds.

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

banners_Home_Secundaria-688x487_3.gif is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

3 images are downloaded at several times the size a phone draws them, for example 01-693909-ambientado-escrivaninha-mesa-escritorio-canto-3-ga at 390 px wide, shown at 97 px. Resized copies would save about 71 KiB.

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

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

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

Your title is only 26 characters: “Madesa Muebles – Madesa MX”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 310 pages on madesa.mx and 24 external pages.

https://madesa.mx/pages/cocinas, https://madesa.mx/collections/cocina-esquinera, https://madesa.mx/collections/modulos-mx, https://madesa.mx/collections/gabinetes, https://madesa.mx/collections/toallero and https://madesa.mx/collections/gabinete-especiero and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://madesa.mx/pages/cocinas, https://madesa.mx/collections/cocinas-integrales, https://madesa.mx/collections/cocinas-compactas, https://madesa.mx/collections/cocina-esquinera, https://madesa.mx/collections/modulos-mx and https://madesa.mx/collections/muebles-fregadero-gabinetes-bajos and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://tags.srv.stackadapt.com/rt?sid=btpntfUtB1Gyy1k4BnF4Au.

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

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

Large scripts ship without source maps.

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

Chrome logged issues while loading the page (“Cookie”).

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

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and HubSpot and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 31 cookies, 3 of them by other companies (measured from a US location before any click).

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