Demander une démo

Rapport de localisation

WEEX

Cryptocurrency exchange

weex.com

Produit: WEEX is a cryptocurrency exchange offering spot and futures trading for Bitcoin, Ethereum, altcoins, and other markets. The platform also provides crypto buying, earning, and related trading services.

Voix de marque: Energetic, promotional, trading-focused

Score de localisation

79/100

Bon

Le site web est généralement bien localisé, avec quelques points à améliorer.

  • 76Audit technique
  • 77Audit linguistique
  • 87Audit contextuel
  • 76Audit visuel
Audité: 8/16/2026Portée: Échantillon intelligent public · crédits techniques, linguistiques, contextuels et visuelsConfiance: Contrôle indicatif de l’état de santé à partir de pages échantillonnées — il ne s’agit pas d’une exploration complète du site.

15 pages échantillonnées parmi les crédits de localisation techniques, linguistiques, contextuels et visuels. Comment nous évaluons les audits de localisation

Comment vous vous comparez

Rang #3 sur 22 audits publics

Top 91 % des domaines auditésMoyenne publique : 68/100

À corriger en priorité

  • hightechnical · 95 % de confiance

    URL locale and html lang disagree

    Path locale zh-cn expects html lang zh-CN, but the page declares zh-Hans. Affects 2 sampled pages.

    Trouvé ici

    Document head · <html lang>

    https://www.weex.com/zh-CN

    Ce que nous avons constaté

    <html lang="zh-Hans"> while the path locale is zh-cn Seen on 2 pages, e.g. https://www.weex.com/zh-CN, https://www.weex.com/zh-TW

    Comment le corriger

    Set html lang="zh-CN" so it matches this page’s URL locale.

  • hightechnical · 95 % de confiance

    Currency does not match the locale

    A zh page still shows dollar amounts without a local currency. Affects 2 sampled pages.

    Trouvé ici

    Page body · sampled copy

    https://www.weex.com/zh-CN

    Ce que nous avons constaté

    $10,000 Seen on 2 pages, e.g. https://www.weex.com/zh-CN, https://www.weex.com/zh-TW

    Comment le corriger

    Use a zh-appropriate currency instead of unlocalized dollar amounts.

  • highlinguistic · 92 % de confiance

    Untranslated call to action

    A vi page still uses source-language CTA copy. Affects 8 sampled pages.

    Trouvé ici

    Pricing hero · <button>

    https://www.weex.com/vi

    Ce que nous avons constaté

    Primary CTA: "@keyframes shimmer { 0% { background-position: 250% 0; } 100% { background-position: -250% 0; } }" Seen on 8 pages, e.g. https://www.weex.com/vi, https://www.weex.com/de, https://www.weex.com/es-ES

    Comment le corriger

    Translate leftover source-language CTAs to match the surrounding locale copy.

Critères d’audit

17 réussis · 13 à corriger · 5 non applicable

À examiner (13)

  • Locale detection

    Échec64technique

    Pages should declare a correct html lang that matches the URL and content locale.

    • hightechnical · 95 % de confiance

      URL locale and html lang disagree

      Path locale zh-cn expects html lang zh-CN, but the page declares zh-Hans. Affects 2 sampled pages.

      Trouvé ici

      Document head · <html lang>

      https://www.weex.com/zh-CN

      Ce que nous avons constaté

      <html lang="zh-Hans"> while the path locale is zh-cn Seen on 2 pages, e.g. https://www.weex.com/zh-CN, https://www.weex.com/zh-TW

      Comment le corriger

      Set html lang="zh-CN" so it matches this page’s URL locale.

  • Language switcher

    Échec78technique

    Visitors should move between locales without losing the current page.

    • mediumtechnical · 72 % de confiance

      Current-page preservation is not demonstrated

      The evidence lists many locales and confirms localized homepage URLs, but does not show whether switching language preserves a non-homepage path.

      Trouvé ici

      Header · language switcher

      https://www.weex.com/

      Ce que nous avons constaté

      "locales":["ar","az","de","en", ... ,"zh-tw"] and sampled page URLs include "https://www.weex.com/" and locale homepages such as "https://www.weex.com/zh-CN".

      Comment le corriger

      Verify every locale option maps the current pathname to the equivalent localized pathname, including nested pages.

  • Sitemap

    Échec60technique

    Like Lighthouse: a valid XML sitemap must be discoverable, robots.txt should reference it with an absolute Sitemap: URL, and localized URLs should appear for published locales.

    • mediumtechnical · 90 % de confiance

      Sitemap is missing localized URLs

      A sitemap was found, but sampled entries do not include locale-prefixed URLs.

      Trouvé ici

      Ce que nous avons constaté

      Sitemap https://www.weex.com/seo-sitemaps/sitemap.xml has no locale-prefixed URLs in the sample

      Comment le corriger

      Include localized URLs in the sitemap for every published locale.

  • Structured data

    Échec0technique

    JSON-LD inLanguage should match the page locale when structured data is present.

    • lowtechnical · 95 % de confiance

      Structured data omits inLanguage

      JSON-LD is present but does not declare inLanguage on sampled pages.

      Trouvé ici

      JSON-LD · <script type="application/ld+json">

      https://www.weex.com/

      Ce que nous avons constaté

      CollectionPage is present but inLanguage is missing

      Comment le corriger

      Set JSON-LD inLanguage to match each page locale.

  • International formatting

    Échec62technique

    Dates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.

    • hightechnical · 95 % de confiance

      Currency does not match the locale

      A zh page still shows dollar amounts without a local currency. Affects 2 sampled pages.

      Trouvé ici

      Page body · sampled copy

      https://www.weex.com/zh-CN

      Ce que nous avons constaté

      $10,000 Seen on 2 pages, e.g. https://www.weex.com/zh-CN, https://www.weex.com/zh-TW

      Comment le corriger

      Use a zh-appropriate currency instead of unlocalized dollar amounts.

  • Translation completeness

    Échec0linguistique

    Localized pages should not leave source-language copy in place, except brand names and URLs.

    • highlinguistic · 92 % de confiance

      Untranslated call to action

      A vi page still uses source-language CTA copy. Affects 8 sampled pages.

      Trouvé ici

      Pricing hero · <button>

      https://www.weex.com/vi

      Ce que nous avons constaté

      Primary CTA: "@keyframes shimmer { 0% { background-position: 250% 0; } 100% { background-position: -250% 0; } }" Seen on 8 pages, e.g. https://www.weex.com/vi, https://www.weex.com/de, https://www.weex.com/es-ES

      Comment le corriger

      Translate leftover source-language CTAs to match the surrounding locale copy.

  • Cultural adaptation

    Échec50contextuel

    Currency, dates, addresses, and local examples should fit the market.

    • mediumcontextual · 78 % de confiance

      Possible cultural adaptation gap

      A zh page still uses US-style currency or contact details. Affects 8 sampled pages.

      Trouvé ici

      Page body · sampled copy

      https://www.weex.com/zh-CN

      Ce que nous avons constaté

      $10,000 Seen on 8 pages, e.g. https://www.weex.com/zh-CN, https://www.weex.com/zh-TW, https://www.weex.com/vi

      Comment le corriger

      Use locale-appropriate currency and contact formats instead of US-style defaults.

  • Text expansion

    Échec40visuel

    Longer translations should not create obvious length pressure versus the source UI.

    • mediumvisual · 88 % de confiance

      Localized text is much longer than the source

      A vi string is 160% the length of the source, which often causes overflow. Affects 11 sampled pages.

      Trouvé ici

      Control · <button>

      https://www.weex.com/vi

      Ce que nous avons constaté

      EN "Accept all" → VI "Chấp nhận tất cả" (160%) Seen on 9 pages, e.g. https://www.weex.com/vi, https://www.weex.com/ar, https://www.weex.com/uk

      Comment le corriger

      Shorten the translation or give the control more room so the longer copy does not overflow.

  • RTL support

    Échec64visuel

    RTL locales should set dir=rtl, avoid direction:ltr overrides, and prefer logical CSS over physical left/right properties.

    • mediumvisual · 84 % de confiance

      RTL page uses physical left/right CSS

      Sampled CSS uses float/margin/padding/left/right without logical inline properties, so layout may not mirror in RTL. Affects 2 sampled pages.

      Trouvé ici

      CSS · margin/float/text-align

      https://www.weex.com/fa-IR

      Ce que nous avons constaté

      ;left:0; ;right:0; right: 16px Seen on 2 pages, e.g. https://www.weex.com/fa-IR, https://www.weex.com/ar

      Comment le corriger

      Prefer logical properties such as margin-inline-start, inset-inline, and text-align: start for RTL layouts.

  • Localized images and assets

    Échec85visuel

    Language-specific images and alt text should match the page locale.

  • Text overflow

    Échec80visuel

    Text should not clip, truncate unexpectedly, or overflow buttons and navigation.

  • Layout breakage

    Échec80visuel

    Localized pages should not overlap, break grids, or overflow modals.

  • Responsive localisation

    Échec80visuel

    Localized layouts should hold up across mobile, tablet, and desktop widths.

Audits réussis (17)

Non applicable (5)

Paramètres régionaux détectés

ar (hreflang)az (hreflang)de (hreflang)en (html_lang)es (url_prefix)es-419 (html_lang)es-ar (hreflang)es-bo (hreflang)es-cl (hreflang)es-co (hreflang)es-cr (hreflang)es-do (hreflang)es-ec (hreflang)es-es (hreflang)es-gt (hreflang)es-hn (hreflang)es-mx (hreflang)es-ni (hreflang)es-pa (hreflang)es-pe (hreflang)es-py (hreflang)es-sv (hreflang)es-uy (hreflang)es-ve (hreflang)fa-ir (hreflang)fr (hreflang)id (hreflang)it (hreflang)ja (hreflang)pl (hreflang)pt-ao (hreflang)pt-br (hreflang)pt-mz (hreflang)pt-pt (hreflang)ru (hreflang)uk (hreflang)vi (hreflang)zh-cn (hreflang)zh-hans (html_lang)zh-hant (html_lang)zh-tw (hreflang)

Résultats complets

  • hightechnical · 95 % de confiance

    URL locale and html lang disagree

    Path locale zh-cn expects html lang zh-CN, but the page declares zh-Hans. Affects 2 sampled pages.

    Trouvé ici

    Document head · <html lang>

    https://www.weex.com/zh-CN

    Ce que nous avons constaté

    <html lang="zh-Hans"> while the path locale is zh-cn Seen on 2 pages, e.g. https://www.weex.com/zh-CN, https://www.weex.com/zh-TW

    Comment le corriger

    Set html lang="zh-CN" so it matches this page’s URL locale.

  • mediumtechnical · 90 % de confiance

    Sitemap is missing localized URLs

    A sitemap was found, but sampled entries do not include locale-prefixed URLs.

    Trouvé ici

    Ce que nous avons constaté

    Sitemap https://www.weex.com/seo-sitemaps/sitemap.xml has no locale-prefixed URLs in the sample

    Comment le corriger

    Include localized URLs in the sitemap for every published locale.

  • lowtechnical · 95 % de confiance

    Structured data omits inLanguage

    JSON-LD is present but does not declare inLanguage on sampled pages.

    Trouvé ici

    JSON-LD · <script type="application/ld+json">

    https://www.weex.com/

    Ce que nous avons constaté

    CollectionPage is present but inLanguage is missing

    Comment le corriger

    Set JSON-LD inLanguage to match each page locale.

  • hightechnical · 95 % de confiance

    Currency does not match the locale

    A zh page still shows dollar amounts without a local currency. Affects 2 sampled pages.

    Trouvé ici

    Page body · sampled copy

    https://www.weex.com/zh-CN

    Ce que nous avons constaté

    $10,000 Seen on 2 pages, e.g. https://www.weex.com/zh-CN, https://www.weex.com/zh-TW

    Comment le corriger

    Use a zh-appropriate currency instead of unlocalized dollar amounts.

  • highlinguistic · 92 % de confiance

    Untranslated call to action

    A vi page still uses source-language CTA copy. Affects 8 sampled pages.

    Trouvé ici

    Pricing hero · <button>

    https://www.weex.com/vi

    Ce que nous avons constaté

    Primary CTA: "@keyframes shimmer { 0% { background-position: 250% 0; } 100% { background-position: -250% 0; } }" Seen on 8 pages, e.g. https://www.weex.com/vi, https://www.weex.com/de, https://www.weex.com/es-ES

    Comment le corriger

    Translate leftover source-language CTAs to match the surrounding locale copy.

  • mediumcontextual · 78 % de confiance

    Possible cultural adaptation gap

    A zh page still uses US-style currency or contact details. Affects 8 sampled pages.

    Trouvé ici

    Page body · sampled copy

    https://www.weex.com/zh-CN

    Ce que nous avons constaté

    $10,000 Seen on 8 pages, e.g. https://www.weex.com/zh-CN, https://www.weex.com/zh-TW, https://www.weex.com/vi

    Comment le corriger

    Use locale-appropriate currency and contact formats instead of US-style defaults.

  • mediumvisual · 88 % de confiance

    Localized text is much longer than the source

    A vi string is 160% the length of the source, which often causes overflow. Affects 11 sampled pages.

    Trouvé ici

    Control · <button>

    https://www.weex.com/vi

    Ce que nous avons constaté

    EN "Accept all" → VI "Chấp nhận tất cả" (160%) Seen on 9 pages, e.g. https://www.weex.com/vi, https://www.weex.com/ar, https://www.weex.com/uk

    Comment le corriger

    Shorten the translation or give the control more room so the longer copy does not overflow.

  • mediumvisual · 84 % de confiance

    RTL page uses physical left/right CSS

    Sampled CSS uses float/margin/padding/left/right without logical inline properties, so layout may not mirror in RTL. Affects 2 sampled pages.

    Trouvé ici

    CSS · margin/float/text-align

    https://www.weex.com/fa-IR

    Ce que nous avons constaté

    ;left:0; ;right:0; right: 16px Seen on 2 pages, e.g. https://www.weex.com/fa-IR, https://www.weex.com/ar

    Comment le corriger

    Prefer logical properties such as margin-inline-start, inset-inline, and text-align: start for RTL layouts.

  • mediumtechnical · 72 % de confiance

    Current-page preservation is not demonstrated

    The evidence lists many locales and confirms localized homepage URLs, but does not show whether switching language preserves a non-homepage path.

    Trouvé ici

    Header · language switcher

    https://www.weex.com/

    Ce que nous avons constaté

    "locales":["ar","az","de","en", ... ,"zh-tw"] and sampled page URLs include "https://www.weex.com/" and locale homepages such as "https://www.weex.com/zh-CN".

    Comment le corriger

    Verify every locale option maps the current pathname to the equivalent localized pathname, including nested pages.

Pages échantillonnées

  • 200 · https://www.weex.com/ · lang=en
  • 200 · https://www.weex.com/zh-CN · lang=zh-Hans
  • 200 · https://www.weex.com/zh-TW · lang=zh-Hant
  • 200 · https://www.weex.com/vi · lang=vi
  • 200 · https://www.weex.com/fa-IR · lang=fa
  • 200 · https://www.weex.com/ar · lang=ar
  • 200 · https://www.weex.com/ru · lang=ru
  • 200 · https://www.weex.com/uk · lang=uk
  • 200 · https://www.weex.com/de · lang=de
  • 200 · https://www.weex.com/es-ES · lang=es-ES
  • 200 · https://www.weex.com/es · lang=es-419
  • 200 · https://www.weex.com/fr · lang=fr
  • 200 · https://www.weex.com/pl · lang=pl
  • 200 · https://www.weex.com/pt · lang=pt-BR
  • 200 · https://www.weex.com/it · lang=it

Envoyez-moi un récapitulatif par e-mail

Facultatif. Saisissez votre adresse e-mail professionnelle et nous vous enverrons un résumé concis de ce rapport public.

Étape suivante

Signaux de localisation solides. Créez un espace de travail pour maintenir vos paramètres régionaux en bon état au fil de vos déploiements, ou réservez une analyse plus approfondie.