Hi! That’s normal indeed – it’s the plugin loading itself. We couldn’t prevent that from happening because if it doesn’t load, it can’t determine whether or not to prevent itself from loading ??
It’s not doing much at that point though, so 433.91ms is an aweful long time for just loading the plugin classes (then again it seems this entire request took 7579.99ms, which is quite long to begin with).
If you want to disable loading plugins in specific contexts you can do that programmatically: https://kinsta.com/blog/disable-wordpress-plugins-loading/
However, note that our plugin may be required in the frontend too, for example in My Account, on the thank you page, or even on any other page when WordPress is handling cron events, so doing this may result in unexpected behavior.
