No character encoding (charset) declared
A charset declaration tells the browser which character set to use when displaying the page's text, so letters, symbols and punctuation render correctly. This check looks for a meta charset tag early in the page's head section or a charset value in the server's Content-Type response header. Neither was found on this site. Without an explicit charset, the browser has to guess the encoding before it can safely render text, which delays the start of rendering and risks garbled characters appearing on the page. This is one of Google Lighthouse's default Best Practices checks. Your developer should add a meta charset tag set to utf-8 as the very first element inside the page's head, or set the Content-Type response header to include charset=utf-8 at the server level. This is a one-line fix, about ten minutes.
Why this matters
Without an explicit charset, the browser has to guess the encoding before it can safely render text, which delays the start of rendering and risks garbled characters appearing on the page. This is one of Google Lighthouse's default Best Practices checks.
How to fix it
Your developer should add a meta charset tag set to utf-8 as the very first element inside the page's head, or set the Content-Type response header to include charset=utf-8 at the server level. This is a one-line fix, about ten minutes.