tiendaride.cl website review

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

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

Your mobile performance score is 19. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

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

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

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

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

Hotjar costs a phone 375 ms of main-thread work and 233 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.

Shopify costs a phone 235 ms of main-thread work and 539 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.

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

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

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

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.

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.53 (75th percentile). Good is under 0.1.

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

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

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

The layout shifts by 0.535 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

Your homepage downloads 3.0 MB in 180 requests on a phone: scripts 1.4 MB (100), images 593 KiB (19) and other files 543 KiB (40). Under 2 MB keeps phones on slow connections fast.

1 image (38 KiB) is 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.

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

1 button has no accessible name, so screen readers announce just “button”.

1 dropdown has no label.

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

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

18 tap targets are too small or too close together to hit reliably with a finger.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

6 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

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

Structured data found (BreadcrumbList, Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

The homepage links to 301 pages on tiendaride.cl and 12 external pages.

https://tiendaride.cl/customer_authentication/redirect has no <title>, so Google invents the link text in results.

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

https://tiendaride.cl/customer_authentication/redirect, https://tiendaride.cl/pages/marcas and https://tiendaride.cl/collections/todo-equipamiento have no meta description, so Google writes the search snippet from whatever text it finds.

https://tiendaride.cl/collections/bicicletas-1, https://tiendaride.cl/collections/enduro, https://tiendaride.cl/collections/e-bikes, https://tiendaride.cl/collections/bicicletas-downhill, https://tiendaride.cl/collections/cross-country and https://tiendaride.cl/collections/ninos and 5 others use the same meta description. A description written for each page earns more clicks.

https://tiendaride.cl/customer_authentication/redirect, https://tiendaride.cl/pages/marcas and https://tiendaride.cl/collections/todo-equipamiento have no <h1> headline, so visitors and search engines get no clear main topic.

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

21 of 90 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 “Cart token is not found”.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 1,209 words of visible text.

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