zucarmex.com website review

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

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

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

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

7 third-party services load with your homepage (Google Tag Manager, ContentSquare and Google/Doubleclick Ads and others), adding 7.6 MB and 399 ms of main-thread time.

Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.

ctfassets.net costs a phone 0 ms of main-thread work and 5.6 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.

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

About 12 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

vtexassets.com costs a phone 0 ms of main-thread work and 1.6 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.

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

For real visitors the layout shifts by 0.44 (75th percentile). Good is under 0.1.

Your largest element takes 21.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “banner movil glass”.

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

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

Real visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

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

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

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

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

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

Your homepage downloads 8.3 MB in 199 requests on a phone: images 7.2 MB (34), scripts 594 KiB (16) and fonts 279 KiB (12). Under 2 MB keeps phones on slow connections fast.

20 images are downloaded at several times the size a phone draws them, for example 6488d40a-b8fc-4d49-b1f9-bb5b5cbaa9a3.png at 4,688 px wide, shown at 390 px. Resized copies would save about 4.6 MB.

5 images weigh 3.7 MB together. On a phone connection a single image that size takes seconds.

6 images (1.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.

6488d40a-b8fc-4d49-b1f9-bb5b5cbaa9a3.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image further down the page (47 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 2.37 g of CO₂e: 284.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 buttons have no accessible name, so screen readers announce just “button”.

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

<object> elements must have alternative text: 18 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Your title is only 21 characters: “Vive Zulka | Zucarmex”. 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.

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

No XML sitemap at https://vivezulka.com/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 32 pages on zucarmex.com and 7 external pages.

A phone browser shows 2,004 words, but the HTML your server sends has only 155. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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://vivezulka.com/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://vivezulka.com/productos/oferta-relampago-zulka, https://vivezulka.com/productos/fardos-y-cajas, https://vivezulka.com/productos/linea-bakers, https://vivezulka.com/productos/sucre-by-zulka, https://vivezulka.com/productos/sticks-zulka and https://vivezulka.com/productos/toneladas-azucar and 1 other have no <title>, so Google invents the link text in results.

https://vivezulka.com/productos/oferta-relampago-zulka, https://vivezulka.com/productos/fardos-y-cajas, https://vivezulka.com/productos/linea-bakers, https://vivezulka.com/productos/sucre-by-zulka, https://vivezulka.com/productos/sticks-zulka and https://vivezulka.com/productos/toneladas-azucar and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://vivezulka.com/productos/oferta-relampago-zulka, https://vivezulka.com/productos/variedad-azucar-glass, https://vivezulka.com/productos/fardos-y-cajas, https://vivezulka.com/productos/linea-bakers, https://vivezulka.com/productos/variedad-azucar-mascabado and https://vivezulka.com/productos/sucre-by-zulka and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://vivezulka.com/productos/oferta-relampago-zulka, https://vivezulka.com/productos/variedad-azucar-glass, https://vivezulka.com/productos/fardos-y-cajas, https://vivezulka.com/productos/linea-bakers, https://vivezulka.com/productos/variedad-azucar-mascabado and https://vivezulka.com/productos/sucre-by-zulka 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 18 found) and read each the way a search engine does.

The page uses 1 deprecated browser API that will stop working in future browsers (“Attribution Reporting is deprecated and will be removed. See https://goo.gle/ps-status for details.”).

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.

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 2,004 words of visible text.

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