revesderecho.com website review

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

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

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

8 third-party services load with your homepage (Shopify, vitals.app and Clarity and others), adding 1,015 KiB and 778 ms of main-thread time.

Shopify costs a phone 360 ms of main-thread work and 540 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 65 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 340 ms faster on a phone.

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

About 354 KiB of JavaScript is downloaded but never used on this page.

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

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

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

Polyfills for old browsers add 50 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.

2 KiB could be saved by minifying CSS.

2 KiB could be saved by minifying JavaScript.

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.

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

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

Your largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “cotton-dulces-banner-mob.gif”.

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

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

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

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

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

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

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

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' tap response (inp) went from 285 ms to 289 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.3 MB in 397 requests on a phone: images 2.0 MB (188), scripts 1.1 MB (92) and other files 727 KiB (99). Under 2 MB keeps phones on slow connections fast.

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

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

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

All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 12 elements on the page fail this check, rated minor by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your title is only 28 characters: “Revesderecho | Tienda Online”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“” and “Nombre del producto”). One clear main headline is easier for people and search engines.

The homepage links to 423 pages on revesderecho.com and 8 external pages.

The HTML your server sends has 1,369 of the 2,893 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

Your homepage links to https://www.revesderecho.com/collections/new-in-ovillos, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.revesderecho.com/collections/ovillos and https://www.revesderecho.com/collections/ovillos-lana-suave-tejer all use the title “Ovillos de Lana Suave para Tejer – Envíos a Todo Chile – Revesderecho”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.revesderecho.com/collections/ovillos-last-chance, https://www.revesderecho.com/collections/last-chance-ovillos, https://www.revesderecho.com/collections/last-chance-accesorios, https://www.revesderecho.com/collections/i-love-it, https://www.revesderecho.com/collections/new-in-accesorios and https://www.revesderecho.com/collections/new-in and 1 other use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.revesderecho.com/collections/ovillos-lana-suave-tejer, whose canonical is https://www.revesderecho.com/collections/ovillos. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.revesderecho.com/collections/ovillos-last-chance, https://www.revesderecho.com/collections/last-chance-ovillos, https://www.revesderecho.com/collections/last-chance-accesorios, https://www.revesderecho.com/collections/i-love-it, https://www.revesderecho.com/collections/new-in-accesorios and https://www.revesderecho.com/collections/new-in 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 121 found) and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

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: 2 trust badges. 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.

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

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