“Properly Defines Charset – Error” in Best Practices of Pagespeed Insights

  • Resolved gusepir

    (@gusepir)


    3 months, 3 weeks ago

    There is a “Properly Defines Charset – Error” in Best Practices of Pagespeed Insights diagnoses…

    I am using the free plugin. my mobile performance test results as 20-35 and a red exlamation mark in Best Practices section, in details, browser compatibility has the “Properly defines charset -Error!” explanation…

    And, when I deactivate Gtranslate plugin, all the results become normal, performance rises to 80-100 and best practices turns to normal, too.

    I checked my html output, http headers, wp-config file and database charset and collation settings(which are all, as far as I could understand, as they should be)

    What else should l make to make it all work smoothly?

    Any help will be appreciated, thanks in advance:)

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author edo888

    (@edo888)

    3 months, 3 weeks ago

    Hi,

    I believe you have Auto detect browser language enabled and your website is not in English. In that case you will measure the regular website load time + the time it needs to translate your website to English.

    Measuring performance is a tricky business.

    Thanks! 🙂

    Thread Starter gusepir

    (@gusepir)

    3 months, 3 weeks ago

    thanks for quick reply but rather than a comment about performance measurement, l needed a solution about (!) mark in browser compatibility which is problematic even if i disregard performance rate points etc.

    what you stated means that “auto-detect browser language cannot be used in non-english websites in this plugin” ?

    do you suggest no solution for that?

    Plugin Author edo888

    (@edo888)

    3 months, 3 weeks ago

    You did not post your website address, so I cannot comment about “charset”. I suggest you to read the explanation provided by Pagespeed tool.

    what you stated means that “auto-detect browser language cannot be used in non-english websites in this plugin” ?

    Absolutely not. My statement means that you should not expect to have the same performance.

    Thread Starter gusepir

    (@gusepir)

    3 months, 3 weeks ago

    l already posted the website address in the first (opening) message and l don t know how it didn t show up here… but here it is: https://melizonbasioglu.com

    Besides, l have read anything l could find about the charset problem, from pagespeed, from all over the internet forums, l also discussed the matter with my hosting company’s technical staff. Strangely nothing about my specific question, that is why l am here asking you, as a last chance 🙂

    looking forward a permanent solution from you, thanks for all your time

    Plugin Author edo888

    (@edo888)

    3 months, 3 weeks ago

    I have checked with Pagespeed and do not see the mentioned error. I believe you have turned off Auto detect browser language option.

    Thread Starter gusepir

    (@gusepir)

    3 months, 3 weeks ago

    i m very sorry, i had forgot to clear the cache, kindly retry please

    Plugin Author edo888

    (@edo888)

    3 months, 3 weeks ago

    Yes, I see that for preflight ajax requests to Google Translate servers do not have charset defined in the response, so the tool complains. However it has nothing to do with performance.

    If you really need to get rid of that warning and improve performance of the translated pages you will need our paid version, which doesn’t depend on js and serves the translations directly from our servers: https://gtranslate.io/#pricing

    Thanks! 🙂

    Thread Starter gusepir

    (@gusepir)

    3 months, 3 weeks ago

    l see, thank you sincerely for your time and concern:)

    Plugin Author edo888

    (@edo888)

    3 months, 3 weeks ago

    You are welcome! 🙂

Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.