madesa.com.co website review

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

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

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

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

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

Google Tag Manager costs a phone 429 ms of main-thread work and 503 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 300 ms faster on a phone.

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

14 images could be 299 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

11 KiB JavaScript is shipped twice across bundles.

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

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 18.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Cocina y comedor Madesa. Sale: muebles con hasta 40% de des…”.

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

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

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

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

Real visitors wait 301 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 80 ms to 294 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 4.7 MB in 479 requests on a phone: other files 1.8 MB (268), scripts 1.7 MB (120) and images 804 KiB (58). Under 2 MB keeps phones on slow connections fast.

banners_Home_Terciaria_688x487_1.png 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).

1 image is downloaded at several times the size a phone draws it, for example 01-MDES0200148N5Z-ambientado.webp at 390 px wide, shown at 97 px. Resized copies would save about 22 KiB.

6 images (248 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.33 g of CO₂e: 159.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

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

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

The homepage links to 277 pages on madesa.com.co and 32 external pages.

https://madesa.com.co/pages/cocinas, https://madesa.com.co/collections/cocinas-esquineras, https://madesa.com.co/collections/modulos-de-cocina-1, https://madesa.com.co/collections/mueble-para-horno-y-microondas, https://madesa.com.co/collections/armario-despensa-vertical and https://madesa.com.co/collections/mueble-para-nevera and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://madesa.com.co/collections/cocinas-integrales, https://madesa.com.co/collections/cocinas-compactas, https://madesa.com.co/collections/cocinas-esquineras, https://madesa.com.co/collections/muebles-de-cocina, https://madesa.com.co/collections/modulos-de-cocina-1 and https://madesa.com.co/collections/muebles-para-meson-y-gabinetes-bajos and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

88 of 213 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.

1 error was logged to the browser console while the page loaded, for example “[Mercado Pago Widget] Error in initWidget: TypeError: Cannot read properties of undefined (reading 'length')”.

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

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and HubSpot and 1 more (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 29 cookies, 9 of them by other companies (measured from a US location before any click).

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