tavi.cl website review

10 images could be 402 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

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

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

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

6 third-party services load with your homepage (loox.io, Google CDN and kiwisizing.com and others), adding 295 KiB and 223 ms of main-thread time.

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

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

Your largest element takes 9.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Polera Crop Racerback Tank”.

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

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

The first text or image appears after 2.6 s on a phone. Good is under 1.8 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 2.0 MB in 145 requests on a phone: other files 738 KiB (76), images 639 KiB (15) and scripts 474 KiB (35). Under 2 MB keeps phones on slow connections fast.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

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

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

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

ARIA input fields do not have accessible names (1 element).

ARIA toggle fields do not have accessible names (1 element).

1 tap target is too small or too close together to hit reliably with a finger.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

Elements with role="none" or role="presentation" have conflicts (1 element).

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

Your title is 67 characters, so Google will cut it off around 60: “Tavi I Vestuario y Accesorios de Yoga | Pilates y Estudio – tavi cl”.

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

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

The homepage links to 165 pages on tavi.cl and 3 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.

https://tavi.cl/policies/shipping-policy, https://tavi.cl/collections/tops, https://tavi.cl/collections/petos-y-bras, https://tavi.cl/collections/poleras, https://tavi.cl/collections/polerones-y-chaquetas and https://tavi.cl/collections/bottoms and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://tavi.cl/collections/tops, https://tavi.cl/collections/petos-y-bras, https://tavi.cl/collections/poleras, https://tavi.cl/collections/polerones-y-chaquetas, https://tavi.cl/collections/bottoms and https://tavi.cl/collections/leggings and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://tavi.cl/collections/petos-y-bras, https://tavi.cl/collections/leggings, https://tavi.cl/collections/lounge-wear, https://tavi.cl/collections/shorts-y-bikers and https://tavi.cl/collections/calcetines took over 3 s to send their HTML from our server.

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

3 errors were logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 429 (Too Many Requests)”).

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.

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

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