ldz.cl website review

25 images could be 16.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

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

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

6 third-party services load with your homepage (bablic.com, website-files.com and ucarecdn.com and others), adding 42.0 MB and 394 ms of main-thread time.

website-files.com costs a phone 78 ms of main-thread work and 41.5 MB 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.

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

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

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

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

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

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

Your largest element takes 9.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “1 of 6”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 42.0 MB in 96 requests on a phone: images 41.5 MB (68), scripts 261 KiB (7) and fonts 234 KiB (13). Under 2 MB keeps phones on slow connections fast.

18 images (3.4 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.

4 images further down the page (110 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 11.91 g of CO₂e: 1428.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails 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.

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

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

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

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

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

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

Your meta description is only 47 characters: “Aqui hay que escribir un párrafo descriptivo...”. 70 to 160 characters is enough to sell the click.

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.

The homepage links to 93 pages on ldz.cl and 4 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.

There is no https://www.ldz.cl/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.ldz.cl/infoproyecto/hotel-sheraton-remodelacion-habitaciones and https://www.ldz.cl/infoproyecto/hotel-sheraton all use the title “Hotel Sheraton”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.ldz.cl/ldz, https://www.ldz.cl/proyectos, https://www.ldz.cl/clientes, https://www.ldz.cl/noticias, https://www.ldz.cl/contact and https://www.ldz.cl/infoproyecto/hotel-termas-de-chillaann and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.ldz.cl/ldz, https://www.ldz.cl/proyectos, https://www.ldz.cl/clientes, https://www.ldz.cl/noticias and https://www.ldz.cl/contact have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.ldz.cl/clientes, https://www.ldz.cl/noticias, https://www.ldz.cl/contact, https://www.ldz.cl/infoproyecto/hotel-termas-de-chillaann, https://www.ldz.cl/infoproyecto/hotel-atton-san-martin and https://www.ldz.cl/infoproyecto/remodelacion-habitaciones-hyatt and 5 others 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 29 found) and read each the way a search engine does.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no form on the homepage, so every lead has to click through to another page first.

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

Opening the homepage sets 5 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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.