i18n: ensure metric names are untranslated

[Mbb640]

FAQ

• Yes, my issue is not about variability or throttling.
• Yes, my issue is not about a specific accessibility audit (file with axe-core instead).
• Yes, my issue is not answered by other FAQs.

URL

Site-agnostic (screenshots taken from local build, doublechecked on google.ca)

What happened?

When generating reports in French, titles of all performance metrics remain in English.

When generating reports in Spanish, there is a similar issue - though some of the missing French translations are available in Spanish.

What did you expect?

Translations that are supported should be complete.

What have you tried?

No response

How were you running Lighthouse?

CLI

Lighthouse Version

12.3

Chrome Version

No response

Node Version

No response

OS

No response

Relevant log output

[adamraine]

The French translations are actually correct here. We don't want to translate these because they are names.

Maybe we shouldn't even send these through the translation pipeline.

[Mbb640]

I don't know the Lighthouse standard, but lines such as "First Contentful Paint" and "Total Blocking Time" feel closer to descriptions of the following metrics than names to me. If I were to speak only French, I believe it would be useful to be able to read this and immediately understand what is actually being measured.

[adamraine]

They have separate descriptions which will be translated:

Considering these metrics are also associated with acronyms, I don't think it makes sense to translate them into a locale where the acronym no longer fits.

FCP seems to be universally untranslated in our docs:
https://web.dev/articles/fcp?hl=de

TBT doc is more inconsistent, it shows both translated and untranslated in german...
https://web.dev/articles/tbt?hl=de

...and is translated in french: https://web.dev/articles/tbt?hl=fr