• Resolved OptArt

    (@optart)


    great plugin, one issue though: after getting great success in web vitals “performance”, noticed slight decrease in “best practices” and found out it’s due to “Charset declaration is missing or occurs too late in the HTML”

    it is due to var _wpmeteor popping up above
    <meta http-equiv=”Content-Type” content=”text/html;” charset=”UTF-8″ />

    would there be any issue if you’d load this after charset declaration?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter OptArt

    (@optart)

    i can imagine it’s safest to find <head> and preg_replace after
    what would work for us too (and probably would be helpful in many other scenarios) is to have some filter on plugin output – then we could remove charset definition from our theme and add it by filtering your plugin output

    Plugin Author Aleksandr Guidrevitch

    (@aguidrevitch)

    Hi @optart,

    Thanks for reporting! I’ve added a tab Extras where you can enable rewrite which moves meta charset before the script. Once I’m sure it is working for everyone, I will remove this setting and make it enabled for everyone. I will release 1.5.6, which contains this fix tomorrow, 31 May 2021 once I test it

    WBR,
    Alex

    Thread Starter OptArt

    (@optart)

    thank you, highly appreciated

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘position of var _wpmeteor in the code’ is closed to new replies.