yuxus.es website review

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

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

8 third-party services load with your homepage (Google Tag Manager, PayPal and Shopify and others), adding 5.9 MB and 650 ms of main-thread time.

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

Shopify costs a phone 87 ms of main-thread work and 5.1 MB 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 440 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

49 KiB could be saved by minifying JavaScript.

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

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

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

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

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

11 KiB JavaScript is shipped twice across bundles.

11 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 43.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Back in stock +”.

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

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

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

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

Real visitors wait 285 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-11-07, real Chrome visitors' tap response (inp) went from 222 ms to 317 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors wait 959 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Your homepage downloads 51.8 MB in 525 requests on a phone: media 38.8 MB (2), images 9.7 MB (114) and other files 1.7 MB (281). Under 2 MB keeps phones on slow connections fast.

zaragoza_652fe0ef-924c-4107-98f3-317e25877e1d.webp weighs 706 KiB. On a phone connection a single image that size takes seconds.

3 images (935 KiB) are 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.

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

20 buttons have no accessible name, so screen readers announce just “button”.

Inline text spacing must be adjustable with custom stylesheets: 10 elements on the page fail this check, rated serious by axe-core.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

5 links have no real href, so search engines can't follow them.

The homepage links to 215 pages on yuxus.es and 23 external pages.

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

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

https://www.yuxus.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.yuxus.com/collections/all-products, https://www.yuxus.com/collections, https://www.yuxus.com/pages/lookbook, https://www.yuxus.com/pages/stores, https://www.yuxus.com/pages/about-us and https://www.yuxus.com/customer_authentication/redirect and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.yuxus.com/collections/all-products, https://www.yuxus.com/collections/bestsellers and https://www.yuxus.com/collections/backinstock have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://www.yuxus.com/pages/wishlist and https://www.yuxus.com/customer_authentication/redirect took over 3 s to send their HTML from our server.

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

3 images failed to load on a phone, for example https://www.yuxus.com/.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“The `disableRemotePlayback` attribute should be used in order to disable the default Cast integrati…”).

5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getRegistrations')”.

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 1 trust badge. 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.

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

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

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo, Microsoft Clarity, Pinterest Tag and TikTok Pixel (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 17 cookies, 2 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.