sleve.mx website review

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

8 third-party services load with your homepage (loox.io, Klaviyo and Shopify and others), adding 252 KiB and 155 ms of main-thread time.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

1 long task block the main thread while loading, the longest for 138 ms. During a long task the page ignores taps.

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

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

About 22 KiB of CSS is downloaded but never applied on this page.

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

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

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

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

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 7.7 MB in 189 requests on a phone: media 5.7 MB (1), other files 794 KiB (107) and images 759 KiB (28). Under 2 MB keeps phones on slow connections fast.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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.

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

The homepage links to 53 pages on sleve.mx and 5 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://sleve.mx/collections/audifonos-over-ear, https://sleve.mx/collections/cables-cargadores, https://sleve.mx/pages/nosotros, https://sleve.mx/collections/audifonos-true-wireless-system, https://sleve.mx/collections/baterias-externas and https://sleve.mx/collections/mas-vendidos and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://sleve.mx/pages/ofertas-sleve, https://sleve.mx/collections/audifonos-over-ear, https://sleve.mx/collections/cables-cargadores, https://sleve.mx/pages/nosotros, https://sleve.mx/collections/audifonos-true-wireless-system and https://sleve.mx/products/evo have no <h1> headline, so visitors and search engines get no clear main topic.

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

12 of 34 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: net::ERR_FAILED”.

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.

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

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

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