Rapport de localisation
Eucalyptus
Digital healthcareeucalyptus.health
Produit: Eucalyptus is a global telehealth provider operating digital healthcare clinics. Its clinics connect patients with certified practitioners, treatments, and ongoing care, with a focus on preventative and chronic healthcare.
Voix de marque: Patient-first, trustworthy, accessible, care-focused
Score de localisation
41/100
MédiocreDes lacunes importantes en matière de localisation affectent l’expérience.
- 73Audit technique
- 77Audit linguistique
- N/AAudit contextuel
- 76Audit visuel
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 #23 sur 23 audits publics
À corriger en priorité
- 1high
Missing language declaration
15 sampled pages do not set html lang, so browsers and assistive tech cannot identify the locale.
See details - 2medium
Only one locale signal detected
The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).
See details - 3medium
No localized terminology set is present
The evidence contains no locale pages, so consistency of translated terminology across locales cannot be verified.
See details
Critères d’audit
3 passed · 7 to watch · 6 to fix · 19 not applicable
À examiner (6)
Locale detection
Échec40techniquePages should declare a correct html lang that matches the URL and content locale.
- hightechnical · 95 % de confiance
Missing language declaration
15 sampled pages do not set html lang, so browsers and assistive tech cannot identify the locale.
Trouvé ici
Document head · <html lang>
https://www.eucalyptus.health/Ce que nous avons constaté
html lang is missing on 15 pages, e.g. https://www.eucalyptus.health/, https://www.eucalyptus.health/?41ebd6b8_page=1, https://www.eucalyptus.health/?41ebd6b8_page=2
Comment le corriger
Set html lang to a BCP 47 language tag for each page locale, such as en, fr-FR, or es-419.
Locale routing
Échec72techniqueLocalized pages should use a consistent URL structure and resolve successfully.
- mediumtechnical · 90 % de confiance
Only one locale signal detected
The sample found little evidence of multi-locale routing (hreflang, locale prefixes, or html lang variety).
Trouvé ici
Sampled pages · document
https://www.eucalyptus.health/Ce que nous avons constaté
Detected locale signals: none
Comment le corriger
Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.
Structured data
Échec52techniqueJSON-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.eucalyptus.health/Ce que nous avons constaté
MedicalOrganization is present but inLanguage is missing
Comment le corriger
Set JSON-LD inLanguage to match each page locale.
Terminology consistency
Échec55linguistiqueImportant concepts should not be translated differently across pages.
- mediumlinguistic · 85 % de confiance
No localized terminology set is present
The evidence contains no locale pages, so consistency of translated terminology across locales cannot be verified.
Trouvé ici
Ce que nous avons constaté
"locales":[]
Comment le corriger
Provide the localized page set and compare recurring concepts such as “Mission,” “Patient Safety,” and “Open Roles” across every locale.
Translation accuracy
Échec50linguistiqueTarget copy should preserve the source meaning, numbers, and product actions.
- mediumlinguistic · 88 % de confiance
Source-to-target accuracy cannot be assessed
Only English copy is provided and no translated target pages or source/target pairs are available for comparison.
Trouvé ici
Ce que nous avons constaté
"locales":[]; "title":"Eucalyptus | Digital Healthcare That Puts Patients First"
Comment le corriger
Supply the localized versions and compare headings, body copy, calls to action, and any numeric content against the source.
Visual hierarchy
Échec55visuelLocalization should not make headings or CTAs lose scanability.
- lowvisual · 80 % de confiance
Heading is excessively long
A localized heading may crowd the visual hierarchy. Affects 22 sampled pages.
Trouvé ici
Page body · heading
https://www.eucalyptus.health/Ce que nous avons constaté
As a global telehealth provider, we're building a safe, effective and accessible future for medicine. Seen on 6 pages, e.g. https://www.eucalyptus.health/, https://www.eucalyptus.health/?41ebd6b8_page=1, https://www.eucalyptus.health/?41ebd6b8_page=2
Comment le corriger
Shorten the heading so it does not crowd the visual hierarchy.
Worth a look (7)
Fluency
Watch88linguistiqueCopy should sound natural, without grammar issues or machine-translation artifacts.
Brand voice
Watch86linguistiqueLocalized copy should preserve the intended tone of the source.
Grammar and style
Watch84linguistiqueLocale-specific capitalization, punctuation, formality, and agreement should be correct.
Localized images and assets
Watch88visuelLanguage-specific images and alt text should match the page locale.
Text overflow
Watch78visuelText should not clip, truncate unexpectedly, or overflow buttons and navigation.
- infovisual · 45 % de confiance
Overflow cannot be confirmed from text-only evidence
The extracted page text does not include visual bounds or screenshots, so clipping and overflow cannot be directly verified.
Trouvé ici
Ce que nous avons constaté
The evidence provides page text and headings but no screenshots or layout measurements.
Comment le corriger
Check navigation, headings, buttons, and long localized strings at the supported viewport widths for clipping or unwanted truncation.
Layout breakage
Watch80visuelLocalized pages should not overlap, break grids, or overflow modals.
- infovisual · 42 % de confiance
Layout integrity cannot be confirmed
The evidence contains no visual screenshots or computed layout data, so overlap, grid breakage, and modal overflow cannot be assessed directly.
Trouvé ici
Ce que nous avons constaté
The supplied page records include status, headings, buttons, and text, but no visual layout evidence.
Comment le corriger
Run visual checks for overlapping elements, broken grids, and overflowing dialogs on each localized page.
Responsive localisation
Watch78visuelLocalized layouts should hold up across mobile, tablet, and desktop widths.
- infovisual · 40 % de confiance
Responsive behavior is unverified
No viewport-specific screenshots or measurements are provided, and no localized pages are listed, so responsive localization cannot be confirmed.
Trouvé ici
Ce que nous avons constaté
"locales":[]; the page evidence contains no viewport or responsive-layout data.
Comment le corriger
Test every locale at mobile, tablet, and desktop widths, including navigation, headings, cards, and calls to action.
Audits réussis (3)
Non applicable (19)
Paramètres régionaux détectés
We did not find any language versions on the sampled pages.
Pages échantillonnées
Étape suivante
Critical gaps showed up. Claim this domain to track fixes in a workspace, or book a review with our team.
Send this to your team
We'll email a short summary — score, top fixes, and a link back to this report — so it's easy to forward.
