z2alwayschasingcl.com website review

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

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

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

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

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

6 third-party services load with your homepage (Clarity, Shopify and azurefd.net and others), adding 408 KiB and 316 ms of main-thread time.

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

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

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 KiB could be saved by minifying CSS.

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

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

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

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

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 2.0 MB in 149 requests on a phone: other files 634 KiB (64), images 568 KiB (16) and scripts 490 KiB (57). Under 2 MB keeps phones on slow connections fast.

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

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

Your title is 87 characters, so Google will cut it off around 60: “Z2, ciencia de la nutrición deportiva aplicada a tu rendimiento. – Z2 Performance Chile”.

There are 3 <h1> headlines (“Z2 Performance Chile”, “NUEVOS PACKS Z2” and “10% off”). One clear main headline is easier for people and search engines.

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

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

1 link has no real href, so search engines can't follow it.

The homepage links to 55 pages on z2alwayschasingcl.com and 4 external pages.

Your homepage links to https://www.z2alwayschasingcl.com/pages/z2rclub, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.z2alwayschasingcl.com/collections/all, https://www.z2alwayschasingcl.com/collections/accesorios, https://www.z2alwayschasingcl.com/collections/pack-de-geles and https://www.z2alwayschasingcl.com/collections/gels have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.z2alwayschasingcl.com/collections/all, https://www.z2alwayschasingcl.com/collections/todos-os-produtos, https://www.z2alwayschasingcl.com/collections/accesorios, https://www.z2alwayschasingcl.com/collections/packs-de-geles, https://www.z2alwayschasingcl.com/collections/pack-de-geles and https://www.z2alwayschasingcl.com/pages/z2-contenido and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

4 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.z2alwayschasingcl.com/cdn/shop/t/4/assets/custom.scss.css?v=1248' because its …”.

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.

The homepage has only about 217 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 Meta Pixel and Microsoft Clarity (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 8 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 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.