It's already set in UNA with the following metatag:

<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />

moreover UNA sending encoding in HTTP headers, as suggested by Google documentation.

so I think this tool is broken since charset is provided using 2 ways, where one is exactly as recommended by their docs.