monumentalhogar.com website review

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

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

8 third-party services load with your homepage (Google Tag Manager, tiendanube.com and Facebook and others), adding 1.2 MB and 1.2 s of main-thread time.

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

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

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

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

tiendanube.com costs a phone 350 ms of main-thread work and 99 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.

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

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

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

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

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

1 image could be 18 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

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

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

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

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

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

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (38 elements).

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

No XML sitemap at https://acdn-us.mitiendanube.com/stores/006/908/352/themes/common/sitemap.xml.gz, so Google discovers your pages only by following links.

11 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 369 pages on monumentalhogar.com and 8 external pages.

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

2 images failed to load on a phone, for example https://monumentalhogar.com/.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 20 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 710 words of visible text.

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