GovInsider

À examiner (12)

• Locale routing

  Échec72technique

  Localized 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://govinsider.asia/intl-en

    Ce que nous avons constaté

    Detected locale signals: en

    Comment le corriger

    Publish additional locales through locale URL prefixes, hreflang alternates, and matching html lang tags.

• Sitemap

  Échec72technique

  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.

  • hightechnical · 100 % de confiance

    robots.txt does not reference the sitemap

    A sitemap is reachable, but robots.txt does not include a Sitemap: directive pointing to it.

    Trouvé ici

    robots.txt · Sitemap:

    https://govinsider.asia/sitemap.xml

    Ce que nous avons constaté

    Reachable sitemap https://govinsider.asia/sitemap.xml is not listed in robots.txt

    Comment le corriger

    Add "Sitemap: https://govinsider.asia/sitemap.xml" to robots.txt.

• Translation accuracy

  Échec72linguistique

  Target copy should preserve the source meaning, numbers, and product actions.

  • infolinguistic · 30 % de confiance

    Source-to-target accuracy cannot be verified

    The evidence contains only English pages and no source-language or translated counterpart for comparison.

    Ce que nous avons constaté

    "locales":["en"]

    Comment le corriger

    Provide source and target page pairs to verify meaning, numbers, and product actions.

• Fluency

  Échec78linguistique

  Copy should sound natural, without grammar issues or machine-translation artifacts.

  • mediumlinguistic · 76 % de confiance

    Search label appears concatenated

    The search control text appears to combine the label and action text without spacing, which reads unnaturally.

    Trouvé ici

    Header · <button>

    https://govinsider.asia/intl-en

    Ce que nous avons constaté

    "Search for contentSEARCH"

    Comment le corriger

    Separate the field label from the action label, or add appropriate spacing and accessible text.

  • lowlinguistic · 76 % de confiance

    Navigation copy appears compressed

    The extracted navigation text contains a dense sequence of fragments that may indicate missing separators.

    Trouvé ici

    Header · <nav>

    https://govinsider.asia/intl-en

    Ce que nous avons constaté

    "digital gov public sector day digital services"

    Comment le corriger

    Add visual or textual separators and verify the rendered navigation labels.

• Brand voice

  Échec88linguistique

  Localized copy should preserve the intended tone of the source.

• Grammar and style

  Échec78linguistique

  Locale-specific capitalization, punctuation, formality, and agreement should be correct.

  • mediumlinguistic · 73 % de confiance

    Missing separation in search control text

    The search control combines two words without spacing, creating a capitalization and punctuation problem.

    Trouvé ici

    Header · <button>

    https://govinsider.asia/intl-en

    Ce que nous avons constaté

    "Search for contentSEARCH"

    Comment le corriger

    Render “Search for content” and “Search” as distinct, correctly spaced labels.

  • lowlinguistic · 73 % de confiance

    Navigation phrase is difficult to parse

    The extracted navigation sequence lacks clear punctuation or separators between items.

    Trouvé ici

    Header · <nav>

    https://govinsider.asia/intl-en

    Ce que nous avons constaté

    "digital gov public sector day digital services"

    Comment le corriger

    Ensure each navigation item is separated in the markup and rendered with appropriate spacing.

• Cultural adaptation

  Échec88contextuel

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

• Localized images and assets

  Échec88visuel

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

• Visual hierarchy

  Échec55visuel

  Localization 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 48 sampled pages.

    Trouvé ici

    Page body · heading

    https://govinsider.asia/intl-en

    Ce que nous avons constaté

    The Philippines’ independent tower firms organise to gain direct access to regulators Seen on 10 pages, e.g. https://govinsider.asia/intl-en, https://govinsider.asia/intl-en/articles, https://govinsider.asia/intl-en/videos

    Comment le corriger

    Shorten the heading so it does not crowd the visual hierarchy.

• Text overflow

  Échec78visuel

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

  • mediumvisual · 68 % de confiance

    Search text may be visually or semantically concatenated

    The extracted control text joins the search prompt and action, creating a potential text-rendering issue.

    Trouvé ici

    Header · <button>

    https://govinsider.asia/intl-en

    Ce que nous avons constaté

    "Search for contentSEARCH"

    Comment le corriger

    Inspect the rendered control and separate its prompt, input, and action text so none overlap or run together.

• Layout breakage

  Échec86visuel

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

• Responsive localisation

  Échec84visuel

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