-
Notifications
You must be signed in to change notification settings - Fork 434
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[🐞] High Total Blocking Time (TBT) using Google Analytics and partytown #513
Comments
Can you try with the new release pls? Thanks |
Here is my result. This is your website, right? |
Yes, that's my site that I've been testing with. The overall score is somewhat variable with some runs doing better than others. Obviously the site scores well overall, but I can't help but want to get to 100 😁 Probably the most useful piece to look at rather than the overall score is the "Avoid long main-thread tasks" section and see whether Partytown is listed there as contributing to Total Blocking Time. My expectation was that Partytown shouldn't block, but I have limited insight into the internals, so perhaps there's some reason it's not possible for Partytown to operate in a non-blocking way. |
have the same issue, in my case overall TBT by partytown-sandbox-sw.htm same as I had with Google Analytics and google-tag-manager scripts together) |
Describe the bug
I don't know if this is purely unavoidable. However, it surprised me as I thought Partytown was supposed to move all computations off the main thread.
My page speed score is a couple of points better without Partytown + GA. However, Partytown + GA is still several points better than GA alone.
Reproduction
https://partytown.builder.io/google-tag-manager
Steps to reproduce
Setup Google Analytics with Partytown. E.g. I followed https://partytown.builder.io/sveltekit
Then use https://pagespeed.web.dev/ (look under "Avoid long main-thread tasks") or https://webpagetest.org/ to see that Partytown is significantly blocking the main thread.
Browser Info
Chrome
Additional Information
No response
The text was updated successfully, but these errors were encountered: