Tracking script causes forced reflow of the page

[canyonwebworks]

This is nearly identical to the patched issue in plausible/analytics: plausible/analytics#5727 (comment)
I'm hoping it will be fixed in the same manner for WordPress users.

Past Issues Searched

• I have searched open and closed issues to make sure that the bug has not yet been reported

A similar bug was reported here: plausible/analytics#5727 (comment)
It was fixed thus: plausible/analytics#6174

Issue is a Bug Report

• This is a bug report and not a feature request, nor asking for self-hosted support

Using official Plausible Cloud hosting or self-hosting?

Self-hosting

Describe the bug

I noticed the following performance issue in Google PageSpeed insights for my site

This is caused by the a dynamic, assumed closed-source Plausible-hosted tracking script: pa-<CLIENT ID>.js

Expected behavior

I'd also like to avoid this performance penalty just like non-WordPress service users.

[Dan0sz]

@metmarkosaric If it's fixed in the JS library, I would assume that it would be fixed in our plugin as well, right? Has the fix been released yet?

[metmarkosaric]

@Dan0sz yes, this is already live and available to cloud subscribers using the WordPress plugin.

this question is about our self-hosted Community Edition, which follows a separate release schedule and isn’t updated continuously like our cloud

the fix will be included in the next self-hosted release, which we’re hoping to ship later this year. self-hosted users will get it once they upgrade their instance to that release

[canyonwebworks]

FWIW, my takeaway having been totally ignored in this conversation and told to wait on something that will likely not come because the issue was marked "completed," is: I probably won't be paying for Plausible anymore.