zhoue.com.ar website review

About 771 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

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

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

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

Google CDN costs a phone 434 ms of main-thread work and 739 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 Tag Manager costs a phone 362 ms of main-thread work and 503 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.

Facebook costs a phone 260 ms of main-thread work and 221 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.2 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

9 images could be 133 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 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

6 KiB could be saved by minifying JavaScript.

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 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner de ZHOUE”.

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

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

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

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

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

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

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

Your homepage downloads 2.3 MB in 51 requests on a phone: scripts 1.5 MB (13), other files 353 KiB (8) and images 233 KiB (21). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

Your meta description is only 29 characters: “ZHOUE | Tienda Online Oficial”. 70 to 160 characters is enough to sell the click.

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

The homepage links to 82 pages on zhoue.com.ar and 6 external pages.

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

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

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

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

The homepage has only about 48 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.

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