Website review, no card needed

yuxus.com logo

yuxus.com website review

Visit site (opens in a new tab)Reviewed 9 November 202627 issues · 61 checks

This review found 27 issues worth fixing on yuxus.com, 9 of them high impact, across 61 checks. The most urgent: page weight: 21.8 MB. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
5.1 s2.8 sMay 23Nov 73.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.3 s
May 30, 20263.3 s
Jun 6, 20263.4 s
Jun 13, 20263.5 s
Jun 20, 20263.6 s
Jun 27, 20264.0 s
Jul 4, 20264.7 s
Jul 11, 20264.8 s
Jul 18, 20264.3 s
Jul 25, 20263.8 s
Aug 1, 20263.3 s
Aug 8, 20263.1 s
Aug 15, 20263.4 s
Aug 22, 20263.5 s
Aug 29, 20263.5 s
Sep 5, 20263.4 s
Sep 12, 20263.4 s
Sep 19, 20263.4 s
Sep 26, 20263.4 s
Oct 3, 20263.4 s
Oct 10, 20263.3 s
Oct 17, 20263.3 s
Oct 24, 20263.2 s
Oct 31, 20263.1 s
Nov 7, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
515 ms183 msMay 23Nov 7317 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026222 ms
May 30, 2026221 ms
Jun 6, 2026232 ms
Jun 13, 2026262 ms
Jun 20, 2026312 ms
Jun 27, 2026377 ms
Jul 4, 2026477 ms
Jul 11, 2026464 ms
Jul 18, 2026390 ms
Jul 25, 2026354 ms
Aug 1, 2026303 ms
Aug 8, 2026274 ms
Aug 15, 2026271 ms
Aug 22, 2026272 ms
Aug 29, 2026279 ms
Sep 5, 2026286 ms
Sep 12, 2026294 ms
Sep 19, 2026305 ms
Sep 26, 2026311 ms
Oct 3, 2026316 ms
Oct 10, 2026320 ms
Oct 17, 2026324 ms
Oct 24, 2026327 ms
Oct 31, 2026324 ms
Nov 7, 2026317 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

5 to fix33
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Real-user INP: 317 ms

    317 ms

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

  • Tap response (INP) got 45% slower for real visitors

    +45%

    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-user FCP: 2.4 s

    2.4 s

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

  • Largest content (LCP) held steady for real visitors

    -5%

    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).

2 checks passed
  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Real-user TTFB: 686 ms

    686 ms

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

Images and page weight

4 to fix38
  • Page weight: 21.8 MB

    21.8 MB

    Your homepage downloads 21.8 MB on a phone, 20.3 MB of it images (93%). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

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

  • 3 images in older formats

    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.

  • 6 images below the first screen load straight away

    6 images further down the page (377 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.2 g of CO₂ per visit

    6.17 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fix94
  • 20 buttons without a name

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

  • 16 images without alt text

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

  • All page content should be contained by landmarks (38 elements)

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

  • 5 form fields without a label

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

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fix93
  • Title is short (5 characters)

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

  • 215 internal links, 23 external

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

7 checks passed
  • Meta description: 137 characters

    Your meta description is 137 characters: “Yuxus Company. Madrid clothing brand. Clean silhouettes, premium fabrics and heavyweight hoodies made to last. Crafted …”.

  • One H1 headline

    Your main headline reads: “YUXUS · Premium oversized streetwear designed in Madrid”.

  • Canonical URL set

    The canonical URL is https://www.yuxus.com/.

  • Structured data in place

    Structured data found: ClothingStore, Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.yuxus.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (899 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.yuxus.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix43
  • 1 linked page is broken

    Your homepage links to https://www.yuxus.com/pages/wishlist, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 page without a title

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

  • 1 linked page hidden from search

    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.

  • 1 page without a meta description

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

  • 8 pages without an H1

    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.

  • 3 pages with very little text

    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.

  • 2 pages slow to respond

    https://www.yuxus.com/collections/all-products and https://www.yuxus.com/customer_authentication/redirect took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

2 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

Best practices

3 to fix71
  • 3 broken images

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

  • 27 small tap targets

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

  • 5 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • No call to action on the first screen

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

  • Local business without LocalBusiness data

    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.

  • No phone number on the homepage

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

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No opening hours

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 338 words of copy

    The homepage carries about 338 words of visible text.

3 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “SHOP”, “Shop” and “Subscribe.”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

  • 5 trackers load before any consent

    5

    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.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 cookies (measured from a US location before any click).

  • 38 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at yuxus.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 12 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Intelligems A B Testing · Cookieyes Gdpr · Pagefly Ai Page Builder · Geosort · Klaviyo Email Marketing Sms · Microsoft Clarity · Kleep X Yuxus Prod · Prysm Social Yuxus · trustpilot.com · nfcube.com · sequra.com · amazonaws.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Bootstrap
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on yuxus.com, including 5 speed issues, 1 SEO issue and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25