Localisation report
quietcircles.com
Product: An AI-powered platform that helps teams learn, engage, and reflect through interactive trivia, puzzles, challenges, team events, and lightweight feedback activities. It is designed to build workplace culture and connection without requiring downloads.
Brand voice: Practical, playful, human, encouraging
Localisation score
81/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 #2 of 24 public audits
Untranslated call to action
A de-de page still uses source-language CTA copy. Affects 9 sampled pages.
Found here
Link · <a>
https://www.quietcircles.com/de-DEWhat we saw
Primary CTA: "Daily Challenges" Seen on 9 pages, e.g. https://www.quietcircles.com/de-DE, https://www.quietcircles.com/es-AR, https://www.quietcircles.com/es-ES
How to fix it
Translate leftover source-language CTAs to match the surrounding locale copy.
No CJK-capable font detected
A ja-jp page shows CJK text but the embedded/inline font stack has no known CJK typeface. Affects 2 sampled pages.
Found here
Page body · font-family
https://www.quietcircles.com/ja-JPWhat we saw
font-family: ui-sans-serif Seen on 2 pages, e.g. https://www.quietcircles.com/ja-JP, https://www.quietcircles.com/ko-KR
How to fix it
Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
Sitemap omits some published locales
Locale-prefixed pages for de, es, fr, hi, id, it, ja, ko do not appear in sampled sitemap URLs.
Found here
Sitemap · sitemap.xml
https://www.quietcircles.com/sitemap.xmlWhat we saw
Sitemap locales in sample: en; missing: de, es, fr, hi, id, it, ja, ko
How to fix it
Include URLs for every published locale prefix in the sitemap.
15 passed · 13 to fix · 7 not applicable
Sitemap
Fail70technicalLike 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 omits some published locales
Locale-prefixed pages for de, es, fr, hi, id, it, ja, ko do not appear in sampled sitemap URLs.
Found here
Sitemap · sitemap.xml
https://www.quietcircles.com/sitemap.xmlWhat we saw
Sitemap locales in sample: en; missing: de, es, fr, hi, id, it, ja, ko
How to fix it
Include URLs for every published locale prefix in the sitemap.
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.quietcircles.com/en-USWhat we saw
Organization is present but inLanguage is missing
How to fix it
Set JSON-LD inLanguage to match each page locale.
Translation completeness
Fail0linguisticLocalized pages should not leave source-language copy in place, except brand names and URLs.
Untranslated call to action
A de-de page still uses source-language CTA copy. Affects 9 sampled pages.
Found here
Link · <a>
https://www.quietcircles.com/de-DEWhat we saw
Primary CTA: "Daily Challenges" Seen on 9 pages, e.g. https://www.quietcircles.com/de-DE, https://www.quietcircles.com/es-AR, https://www.quietcircles.com/es-ES
How to fix it
Translate leftover source-language CTAs to match the surrounding locale copy.
Terminology consistency
Fail88linguisticImportant concepts should not be translated differently across pages.
Navigation terminology is not consistently localized
The German page retains several English navigation labels while surrounding content is translated.
Found here
Header · <nav>
https://www.quietcircles.com/de-DEWhat we saw
German page text: "Home Library Daily Challenges Explore Contact Us 🇩🇪 Anmelden"
How to fix it
Translate the navigation labels consistently for the German locale, or deliberately document product terms that should remain in English.
Brand voice
Fail89linguisticLocalized copy should preserve the intended tone of the source.
German voice is more colloquial than the English source
Words such as “rocken” and “richtig durchstarten” create a stronger, more casual promotional tone than the relatively restrained English source.
Found here
How teams use Quiet Circles · <h2>
https://www.quietcircles.com/de-DEWhat we saw
Source: "How teams use Quiet Circles"; German: "So rocken Teams Quiet Circles"
How to fix it
Align the German register with the approved brand voice, keeping the energetic tone without introducing a materially more casual style unless intentional.
UI context
Fail84contextualTranslations should fit the UI component: button, nav, form, modal, or error.
Localized page contains English navigation labels
English navigation strings remain in the German header, creating a mixed-language UI context.
Found here
Header · <nav>
https://www.quietcircles.com/de-DEWhat we saw
"Home Library Daily Challenges Explore Contact Us 🇩🇪 Anmelden"
How to fix it
Localize the header navigation labels for the German page and verify the same component across all locale variants.
Text expansion
Fail40visualLonger translations should not create obvious length pressure versus the source UI.
Localized text is much longer than the source
A de string is 161% the length of the source, which often causes overflow. Affects 26 sampled pages.
Found here
Heading · heading
https://www.quietcircles.com/de-DEWhat we saw
EN "Where teams learn, reflect, and engage" → DE "Wo Teams zusammen lernen, nachdenken und richtig durchstarten" (161%) Seen on 7 pages, e.g. https://www.quietcircles.com/de-DE, https://www.quietcircles.com/es-AR, https://www.quietcircles.com/es-ES
How to fix it
Shorten the translation or give the control more room so the longer copy does not overflow.
Font and script support
Fail62visualTypography should support the target script without generic fallback-only stacks, tofu glyphs, or missing CJK fonts.
No CJK-capable font detected
A ja-jp page shows CJK text but the embedded/inline font stack has no known CJK typeface. Affects 2 sampled pages.
Found here
Page body · font-family
https://www.quietcircles.com/ja-JPWhat we saw
font-family: ui-sans-serif Seen on 2 pages, e.g. https://www.quietcircles.com/ja-JP, https://www.quietcircles.com/ko-KR
How to fix it
Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
Localized images and assets
Fail58visualLanguage-specific images and alt text should match the page locale.
Image still looks like the source locale
Alt text or filename on a ja-jp page appears to be English. Affects 14 sampled pages.
Found here
Page body · <img alt>
https://www.quietcircles.com/ja-JPWhat we saw
alt="Daily Interactive Puzzles - Team members solving puzzles together" src="/bento/4.png" Seen on 2 pages, e.g. https://www.quietcircles.com/ja-JP, https://www.quietcircles.com/ko-KR
How to fix it
Localize the image asset and alt text for this page locale.
Visual hierarchy
Fail55visualLocalization should not make headings or CTAs lose scanability.
Heading is excessively long
A localized heading may crowd the visual hierarchy. Affects 5 sampled pages.
Found here
Page body · heading
https://www.quietcircles.com/fr-CAWhat we saw
Là où les équipes jettent un coup d’œil, prennent une pause, et s’amusent ensemble Seen on 2 pages, e.g. https://www.quietcircles.com/fr-CA, https://www.quietcircles.com/fr-FR
How to fix it
Shorten the heading so it does not crowd the visual hierarchy.
Text overflow
Fail86visualText should not clip, truncate unexpectedly, or overflow buttons and navigation.
Long localized labels present a possible overflow risk
The evidence includes substantially longer German headings and FAQ button labels, but no screenshot or rendered measurements confirm clipping.
Found here
Hero and FAQ · <h1>, <button>
https://www.quietcircles.com/de-DEWhat we saw
"Wo Teams zusammen lernen, nachdenken und richtig durchstarten"; "Müssen wir alle gleichzeitig online sein, um zu spielen?"
How to fix it
Test these strings at narrow mobile widths and allow wrapping or flexible button sizing where needed.
Layout breakage
Fail88visualLocalized pages should not overlap, break grids, or overflow modals.
Localized layout risk cannot be fully verified from text-only evidence
Long German headings and FAQ labels could affect component sizing, but the provided evidence contains no screenshots or layout measurements confirming breakage.
Found here
Hero and FAQ · <h1>, <button>
https://www.quietcircles.com/de-DEWhat we saw
"Wo Teams zusammen lernen, nachdenken und richtig durchstarten"; "Welche Arten von Herausforderungen gibt's?"
How to fix it
Run visual checks across the supplied locales and widths, especially for hero headings, FAQ buttons, and navigation.
Responsive localisation
Fail87visualLocalized layouts should hold up across mobile, tablet, and desktop widths.
Responsive behavior is not directly evidenced
The localized content includes long German strings that may require responsive handling, but no screenshots or viewport results are provided.
Found here
Hero and header · <h1>, <nav>
https://www.quietcircles.com/de-DEWhat we saw
"Wo Teams zusammen lernen, nachdenken und richtig durchstarten"; "Home Library Daily Challenges Explore Contact Us 🇩🇪 Anmelden"
How to fix it
Verify mobile, tablet, and desktop rendering for long headings and the mixed-length header labels; enable wrapping or responsive navigation as needed.
Sitemap omits some published locales
Locale-prefixed pages for de, es, fr, hi, id, it, ja, ko do not appear in sampled sitemap URLs.
Found here
Sitemap · sitemap.xml
https://www.quietcircles.com/sitemap.xmlWhat we saw
Sitemap locales in sample: en; missing: de, es, fr, hi, id, it, ja, ko
How to fix it
Include URLs for every published locale prefix in the sitemap.
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.quietcircles.com/en-USWhat we saw
Organization is present but inLanguage is missing
How to fix it
Set JSON-LD inLanguage to match each page locale.
Untranslated call to action
A de-de page still uses source-language CTA copy. Affects 9 sampled pages.
Found here
Link · <a>
https://www.quietcircles.com/de-DEWhat we saw
Primary CTA: "Daily Challenges" Seen on 9 pages, e.g. https://www.quietcircles.com/de-DE, https://www.quietcircles.com/es-AR, https://www.quietcircles.com/es-ES
How to fix it
Translate leftover source-language CTAs to match the surrounding locale copy.
Localized text is much longer than the source
A de string is 161% the length of the source, which often causes overflow. Affects 26 sampled pages.
Found here
Heading · heading
https://www.quietcircles.com/de-DEWhat we saw
EN "Where teams learn, reflect, and engage" → DE "Wo Teams zusammen lernen, nachdenken und richtig durchstarten" (161%) Seen on 7 pages, e.g. https://www.quietcircles.com/de-DE, https://www.quietcircles.com/es-AR, https://www.quietcircles.com/es-ES
How to fix it
Shorten the translation or give the control more room so the longer copy does not overflow.
No CJK-capable font detected
A ja-jp page shows CJK text but the embedded/inline font stack has no known CJK typeface. Affects 2 sampled pages.
Found here
Page body · font-family
https://www.quietcircles.com/ja-JPWhat we saw
font-family: ui-sans-serif Seen on 2 pages, e.g. https://www.quietcircles.com/ja-JP, https://www.quietcircles.com/ko-KR
How to fix it
Include a CJK font such as Noto Sans CJK, Malgun Gothic, Hiragino, or PingFang in the stack.
No Korean word-break rule found in sampled CSS
Embedded CSS was found, but it does not declare word-break: keep-all for Hangul.
Found here
CSS · word-break
https://www.quietcircles.com/ko-KRWhat we saw
Sampled <style>/inline CSS declares fonts but no word-break: keep-all
How to fix it
Add word-break: keep-all for Korean text containers.
Image still looks like the source locale
Alt text or filename on a ja-jp page appears to be English. Affects 14 sampled pages.
Found here
Page body · <img alt>
https://www.quietcircles.com/ja-JPWhat we saw
alt="Daily Interactive Puzzles - Team members solving puzzles together" src="/bento/4.png" Seen on 2 pages, e.g. https://www.quietcircles.com/ja-JP, https://www.quietcircles.com/ko-KR
How to fix it
Localize the image asset and alt text for this page locale.
Heading is excessively long
A localized heading may crowd the visual hierarchy. Affects 5 sampled pages.
Found here
Page body · heading
https://www.quietcircles.com/fr-CAWhat we saw
Là où les équipes jettent un coup d’œil, prennent une pause, et s’amusent ensemble Seen on 2 pages, e.g. https://www.quietcircles.com/fr-CA, https://www.quietcircles.com/fr-FR
How to fix it
Shorten the heading so it does not crowd the visual hierarchy.
Page language is locale-matched in sampled pages
The sampled English and German pages declare matching HTML language values.
Found here
Document root · <html>
https://www.quietcircles.com/de-DEWhat we saw
"url":"https://www.quietcircles.com/en-US","htmlLang":"en-US"; "url":"https://www.quietcircles.com/de-DE","htmlLang":"de-DE"
Navigation terminology is not consistently localized
The German page retains several English navigation labels while surrounding content is translated.
Found here
Header · <nav>
https://www.quietcircles.com/de-DEWhat we saw
German page text: "Home Library Daily Challenges Explore Contact Us 🇩🇪 Anmelden"
How to fix it
Translate the navigation labels consistently for the German locale, or deliberately document product terms that should remain in English.
Some source nuances are adapted rather than closely preserved
The German headline uses more idiomatic promotional wording than the English source, which may slightly shift the meaning of “engage” and “high-achieving.”
Found here
Hero · <h1>
https://www.quietcircles.com/de-DEWhat we saw
Source: "Where teams learn, reflect and engage" and "An AI-powered system for high-achieving teams in fast-moving environments"; German: "Wo Teams zusammen lernen, nachdenken und richtig durchstarten" and "Ein KI-gesteuertes System für Top-Teams in schnelllebigen Umgebungen"
How to fix it
Review the German hero copy against the approved source meaning and retain the intended concepts if literal product positioning is required.
Sampled German copy reads naturally
The visible German headings and FAQ questions are idiomatic and do not show clear machine-translation artifacts.
Found here
Hero and FAQ · <h1>, <button>
https://www.quietcircles.com/de-DEWhat we saw
"Wo Teams zusammen lernen, nachdenken und richtig durchstarten"; "Müssen wir alle gleichzeitig online sein, um zu spielen?"
German voice is more colloquial than the English source
Words such as “rocken” and “richtig durchstarten” create a stronger, more casual promotional tone than the relatively restrained English source.
Found here
How teams use Quiet Circles · <h2>
https://www.quietcircles.com/de-DEWhat we saw
Source: "How teams use Quiet Circles"; German: "So rocken Teams Quiet Circles"
How to fix it
Align the German register with the approved brand voice, keeping the energetic tone without introducing a materially more casual style unless intentional.
Primary German CTAs preserve the intended actions
The localized CTAs clearly communicate starting for free and joining the waitlist.
Found here
Hero · <a>
https://www.quietcircles.com/de-DEWhat we saw
"Kostenlos starten"; "Zur Warteliste anmelden"
Localized page contains English navigation labels
English navigation strings remain in the German header, creating a mixed-language UI context.
Found here
Header · <nav>
https://www.quietcircles.com/de-DEWhat we saw
"Home Library Daily Challenges Explore Contact Us 🇩🇪 Anmelden"
How to fix it
Localize the header navigation labels for the German page and verify the same component across all locale variants.
Product navigation is mixed-language in German
The product-oriented navigation includes English labels despite the German locale, which can make the localized workflow feel incomplete.
Found here
Header · <nav>
https://www.quietcircles.com/de-DEWhat we saw
"Home Library Daily Challenges Explore Contact Us 🇩🇪 Anmelden"
How to fix it
Use a locale-specific navigation resource for all product areas, including Home, Library, Daily Challenges, Explore, and Contact Us.
Long localized labels present a possible overflow risk
The evidence includes substantially longer German headings and FAQ button labels, but no screenshot or rendered measurements confirm clipping.
Found here
Hero and FAQ · <h1>, <button>
https://www.quietcircles.com/de-DEWhat we saw
"Wo Teams zusammen lernen, nachdenken und richtig durchstarten"; "Müssen wir alle gleichzeitig online sein, um zu spielen?"
How to fix it
Test these strings at narrow mobile widths and allow wrapping or flexible button sizing where needed.
Localized layout risk cannot be fully verified from text-only evidence
Long German headings and FAQ labels could affect component sizing, but the provided evidence contains no screenshots or layout measurements confirming breakage.
Found here
Hero and FAQ · <h1>, <button>
https://www.quietcircles.com/de-DEWhat we saw
"Wo Teams zusammen lernen, nachdenken und richtig durchstarten"; "Welche Arten von Herausforderungen gibt's?"
How to fix it
Run visual checks across the supplied locales and widths, especially for hero headings, FAQ buttons, and navigation.
Responsive behavior is not directly evidenced
The localized content includes long German strings that may require responsive handling, but no screenshots or viewport results are provided.
Found here
Hero and header · <h1>, <nav>
https://www.quietcircles.com/de-DEWhat we saw
"Wo Teams zusammen lernen, nachdenken und richtig durchstarten"; "Home Library Daily Challenges Explore Contact Us 🇩🇪 Anmelden"
How to fix it
Verify mobile, tablet, and desktop rendering for long headings and the mixed-length header labels; enable wrapping or responsive navigation as needed.
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.
