Issue with Pagespeed: "Properly defines charset Error"

93 Views Asked by At

Hello Stack Overflow community,

I'm currently working on a project hosted on HubSpot, and I've encountered an issue with Pagespeed Insights. The tool is flagging a "Properly defines charset Error," even though I have correctly specified the tag in my HTML.

As a result, the "best practice" indicator is marked in red, and no value is displayed. I've double-checked the charset declaration, and it seems accurate. Has anyone else experienced a similar problem with Pagespeed Insights on HubSpot? Are there any known solutions or workarounds to address this issue and get the "best practice" indicator to display the correct values?

Your insights and suggestions would be greatly appreciated. Thank you in advance!

I've double-checked the charset declaration, and it seems accurate.

1

There are 1 best solutions below

0
On

PageSpeed Insights (PSI) was not complaining the charset wasn't there.

It was complaining an error occurred and it was unable to check:

Screenshot of PSI showing the error

As you can see the actual error is "Required MainDocumentContent gatherer encountered an error: Protocol error (Network.getResponseBody): Request content was evicted from inspector cache".

It looks like the issue was apparently fixed recently in Lighthouse and should be in version v11.1.0. PSI is currently on v11.0.0 so that explains why it's still showign there. However when I test locally in DevTools (on 11.3.0) I still see the same error. So I commented on that bug.

In the meantime you can ignore this error as the charset is indeed correct.