gloriahoon.cl website review

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

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

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

2 third-party services load with your homepage (Shopify and shop.app), adding 142 KiB and 36 ms of main-thread time.

About 50 KiB of CSS is downloaded but never applied on this page.

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.

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

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

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

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

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 13.1 MB in 208 requests on a phone: media 9.9 MB (2), images 2.0 MB (25) and other files 685 KiB (70). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (25 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

10 elements hidden from screen readers can still receive keyboard focus.

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

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

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

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

Your meta description is 268 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 80 pages on gloriahoon.cl and 5 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), 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://gloriahoon.cl/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://gloriahoon.cl/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://gloriahoon.cl/collections/modeladores-shape-control, https://gloriahoon.cl/collections/enteros, https://gloriahoon.cl/collections/joyas, https://gloriahoon.cl/collections/ropa-deportiva, https://gloriahoon.cl/collections/bottom and https://gloriahoon.cl/collections/docor and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://gloriahoon.cl/collections/recien-llegados/Verano-2026, whose canonical is https://gloriahoon.cl/collections/recien-llegados. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://gloriahoon.cl/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 224 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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