mpc.cl website review

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

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

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

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

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

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

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

Google CDN costs a phone 124 ms of main-thread work and 348 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.

Google Fonts costs a phone 0 ms of main-thread work and 334 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 59 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 210 ms faster on a phone.

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

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

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

Desktop scores 50 but mobile only 24. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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

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

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

The first text or image appears after 4.0 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.

Scripts block taps and scrolling for 667 ms in total while the page loads. 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.9 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

Your homepage downloads 2.9 MB in 79 requests on a phone: scripts 1.8 MB (17), images 683 KiB (38) and fonts 368 KiB (5). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 9e8456e7dbae37845ba34ce1351ceb07b06edb63.webp at 1,903 px wide, shown at 230 px. Resized copies would save about 178 KiB.

9 images further down the page (417 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 0.83 g of CO₂e: 99.2 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”.

1 dropdown has no label.

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

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 91 pages on mpc.cl and 8 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.

robots.txt blocks GPTBot and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://www.mpc.cl/buscador and https://www.mpc.cl/proyecto/edificio-san-damian-de-vitacura-ii-parque-san-damian all use the title “Departamentos en Venta - Proyectos | Inmobiliaria MPC”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.mpc.cl/construccion_terceros, https://www.mpc.cl/contacto, https://www.mpc.cl/proyecto/edificio-suiza-2060, https://www.mpc.cl/proyecto/edificio-galvarino-gallardo-1815, https://www.mpc.cl/proyecto/edificios-mirador-los-trapenses and https://www.mpc.cl/proyecto/edificio-zanartu-1179 have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mpc.cl/buscador and https://www.mpc.cl/proyecto/edificio-san-damian-de-vitacura-ii-parque-san-damian use the same meta description. A description written for each page earns more clicks.

https://www.mpc.cl/buscador, https://www.mpc.cl/buscador/todos/providencia, https://www.mpc.cl/buscador/todos/lo-barnechea, https://www.mpc.cl/buscador/todos/las-condes, https://www.mpc.cl/buscador/todos/uoa and https://www.mpc.cl/buscador/todos/vitacura and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.mpc.cl/contacto and https://www.mpc.cl/buscador/todos/uoa have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

10 images failed to load on a phone, for example https://www.mpc.cl/images/home/p1.webp.

4 of 20 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: the server responded with a status of 404 ()”.

13 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

Large scripts ship without source maps.

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.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 1 more (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 9 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.