Localisation report
weex.com
Product: 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.
Brand voice: Energetic, promotional, trading-focused
Localisation score
79/100
GoodThe website is generally well localised, with some issues to improve.
Sampled 15 pages across technical, linguistic, contextual, and visual localisation credits. How we score localisation audits
Rank #3 of 24 public audits
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.
Found here
Document head · <html lang>
https://www.weex.com/zh-CNWhat we saw
<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
How to fix it
Set html lang="zh-CN" so it matches this page’s URL locale.
Currency does not match the locale
A zh page still shows dollar amounts without a local currency. Affects 2 sampled pages.
Found here
Page body · sampled copy
https://www.weex.com/zh-CNWhat we saw
$10,000 Seen on 2 pages, e.g. https://www.weex.com/zh-CN, https://www.weex.com/zh-TW
How to fix it
Use a zh-appropriate currency instead of unlocalized dollar amounts.
Untranslated call to action
A vi page still uses source-language CTA copy. Affects 8 sampled pages.
Found here
Pricing hero · <button>
https://www.weex.com/viWhat we saw
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
How to fix it
Translate leftover source-language CTAs to match the surrounding locale copy.
17 passed · 13 to fix · 5 not applicable
Locale detection
Fail64technicalPages should declare a correct html lang that matches the URL and content locale.
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.
Found here
Document head · <html lang>
https://www.weex.com/zh-CNWhat we saw
<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
How to fix it
Set html lang="zh-CN" so it matches this page’s URL locale.
Language switcher
Fail78technicalVisitors should move between locales without losing the current page.
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.
Found here
Header · language switcher
https://www.weex.com/What we saw
"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".
How to fix it
Verify every locale option maps the current pathname to the equivalent localized pathname, including nested pages.
Sitemap
Fail60technicalLike 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.
Sitemap is missing localized URLs
A sitemap was found, but sampled entries do not include locale-prefixed URLs.
Found here
Sitemap · sitemap.xml
https://www.weex.com/seo-sitemaps/sitemap.xmlWhat we saw
Sitemap https://www.weex.com/seo-sitemaps/sitemap.xml has no locale-prefixed URLs in the sample
How to fix it
Include localized URLs in the sitemap for every published locale.
Structured data
Fail0technicalJSON-LD inLanguage should match the page locale when structured data is present.
Structured data omits inLanguage
JSON-LD is present but does not declare inLanguage on sampled pages.
Found here
JSON-LD · <script type="application/ld+json">
https://www.weex.com/What we saw
CollectionPage is present but inLanguage is missing
How to fix it
Set JSON-LD inLanguage to match each page locale.
International formatting
Fail62technicalDates, numbers, currency, Arabic Western digits, and Gregorian calendars should match locale conventions.
Currency does not match the locale
A zh page still shows dollar amounts without a local currency. Affects 2 sampled pages.
Found here
Page body · sampled copy
https://www.weex.com/zh-CNWhat we saw
$10,000 Seen on 2 pages, e.g. https://www.weex.com/zh-CN, https://www.weex.com/zh-TW
How to fix it
Use a zh-appropriate currency instead of unlocalized dollar amounts.
Translation completeness
Fail0linguisticLocalized pages should not leave source-language copy in place, except brand names and URLs.
Untranslated call to action
A vi page still uses source-language CTA copy. Affects 8 sampled pages.
Found here
Pricing hero · <button>
https://www.weex.com/viWhat we saw
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
How to fix it
Translate leftover source-language CTAs to match the surrounding locale copy.
Cultural adaptation
Fail50contextualCurrency, dates, addresses, and local examples should fit the market.
Possible cultural adaptation gap
A zh page still uses US-style currency or contact details. Affects 8 sampled pages.
Found here
Page body · sampled copy
https://www.weex.com/zh-CNWhat we saw
$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
How to fix it
Use locale-appropriate currency and contact formats instead of US-style defaults.
Text expansion
Fail40visualLonger translations should not create obvious length pressure versus the source UI.
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.
Found here
Control · <button>
https://www.weex.com/viWhat we saw
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
How to fix it
Shorten the translation or give the control more room so the longer copy does not overflow.
RTL support
Fail64visualRTL locales should set dir=rtl, avoid direction:ltr overrides, and prefer logical CSS over physical left/right properties.
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.
Found here
CSS · margin/float/text-align
https://www.weex.com/fa-IRWhat we saw
;left:0; ;right:0; right: 16px Seen on 2 pages, e.g. https://www.weex.com/fa-IR, https://www.weex.com/ar
How to fix it
Prefer logical properties such as margin-inline-start, inset-inline, and text-align: start for RTL layouts.
Localized images and assets
Fail85visualLanguage-specific images and alt text should match the page locale.
Text overflow
Fail80visualText should not clip, truncate unexpectedly, or overflow buttons and navigation.
Layout breakage
Fail80visualLocalized pages should not overlap, break grids, or overflow modals.
Responsive localisation
Fail80visualLocalized layouts should hold up across mobile, tablet, and desktop widths.
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.
Found here
Document head · <html lang>
https://www.weex.com/zh-CNWhat we saw
<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
How to fix it
Set html lang="zh-CN" so it matches this page’s URL locale.
Sitemap is missing localized URLs
A sitemap was found, but sampled entries do not include locale-prefixed URLs.
Found here
Sitemap · sitemap.xml
https://www.weex.com/seo-sitemaps/sitemap.xmlWhat we saw
Sitemap https://www.weex.com/seo-sitemaps/sitemap.xml has no locale-prefixed URLs in the sample
How to fix it
Include localized URLs in the sitemap for every published locale.
Structured data omits inLanguage
JSON-LD is present but does not declare inLanguage on sampled pages.
Found here
JSON-LD · <script type="application/ld+json">
https://www.weex.com/What we saw
CollectionPage is present but inLanguage is missing
How to fix it
Set JSON-LD inLanguage to match each page locale.
Currency does not match the locale
A zh page still shows dollar amounts without a local currency. Affects 2 sampled pages.
Found here
Page body · sampled copy
https://www.weex.com/zh-CNWhat we saw
$10,000 Seen on 2 pages, e.g. https://www.weex.com/zh-CN, https://www.weex.com/zh-TW
How to fix it
Use a zh-appropriate currency instead of unlocalized dollar amounts.
Untranslated call to action
A vi page still uses source-language CTA copy. Affects 8 sampled pages.
Found here
Pricing hero · <button>
https://www.weex.com/viWhat we saw
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
How to fix it
Translate leftover source-language CTAs to match the surrounding locale copy.
Possible cultural adaptation gap
A zh page still uses US-style currency or contact details. Affects 8 sampled pages.
Found here
Page body · sampled copy
https://www.weex.com/zh-CNWhat we saw
$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
How to fix it
Use locale-appropriate currency and contact formats instead of US-style defaults.
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.
Found here
Control · <button>
https://www.weex.com/viWhat we saw
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
How to fix it
Shorten the translation or give the control more room so the longer copy does not overflow.
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.
Found here
CSS · margin/float/text-align
https://www.weex.com/fa-IRWhat we saw
;left:0; ;right:0; right: 16px Seen on 2 pages, e.g. https://www.weex.com/fa-IR, https://www.weex.com/ar
How to fix it
Prefer logical properties such as margin-inline-start, inset-inline, and text-align: start for RTL layouts.
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.
Found here
Header · language switcher
https://www.weex.com/What we saw
"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".
How to fix it
Verify every locale option maps the current pathname to the equivalent localized pathname, including nested pages.
Optional. Enter your work email and we will send a concise summary of this public report.
Strong localisation signals. Create a workspace to keep locales healthy as you ship, or book a deeper review.
