mueblespergo.com website review

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

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

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

Your mobile performance score is 60 (desktop: 76). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Clarity and others), adding 874 KiB and 665 ms of main-thread time.

10 images could be 311 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

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

About 316 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hasta 30% + 20% Off y hasta 24 meses sin intereses”.

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

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

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

Real visitors wait 217 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-17, real Chrome visitors' largest content (lcp) went from 1.7 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 5.1 MB in 324 requests on a phone: images 3.0 MB (132), scripts 1.1 MB (97) and other files 705 KiB (78). Under 2 MB keeps phones on slow connections fast.

40 images (2.6 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_WEB-04_162fdace-aaad-4d80-8b6f-a1e8e43c4a46.webp 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 interfaz_WA_2.webp at 343 px wide, shown at 65 px. Resized copies would save about 91 KiB.

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

Certain ARIA roles must be contained by particular parents: 5 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 5 elements on the page fail 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.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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.

The homepage links to 334 pages on mueblespergo.com and 15 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.mueblespergo.com/collections/mesas-interior, https://www.mueblespergo.com/collections/sillas-interior and https://www.mueblespergo.com/collections/bancos-interior all use the title “Comedores modernos y premium | Muebles Pergo – Muebles Pergo”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.mueblespergo.com/pages/nuestras-sucursales has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mueblespergo.com/collections/sofas/sofas, https://www.mueblespergo.com/collections/love-seats/loveseats, https://www.mueblespergo.com/collections/escuadras/escuadras, https://www.mueblespergo.com/collections/sillones-individuales/Sillones-Individuales, https://www.mueblespergo.com/collections/sofa-camas and https://www.mueblespergo.com/collections/mesas-de-centro-1/Mesas-De-Centro and 5 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://www.mueblespergo.com/collections/sillones-individuales/Sillones-Individuales, whose canonical is https://www.mueblespergo.com/collections/sillones-individuales/sillones-individuales. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.mueblespergo.com/pages/nuestras-sucursales, https://www.mueblespergo.com/collections/sofas/sofas, https://www.mueblespergo.com/collections/love-seats/loveseats, https://www.mueblespergo.com/collections/escuadras/escuadras, https://www.mueblespergo.com/collections/sillones-individuales/Sillones-Individuales and https://www.mueblespergo.com/collections/sofa-camas 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 154 found) and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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 14 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 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.