Slows down a dashboard

  • This plugin slows down a WordPress dashboard a bit. A few times I’ve measured above 0.5, which is a lot. Imagine a few plugins adding a second to the load, it can add up. Luckily, it’s typically below 0.5 seconds. It’s not as bad as for example, Ezoic or Spectra plugins are (these are horrible), but WP Forms still adds some delay to both backend as well as frontend.

    • This topic was modified 1 month, 3 weeks ago by alekmitch.
    • This topic was modified 1 month, 3 weeks ago by alekmitch.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Kenneth Macharia

    (@kmacharia)

    Hey @alekmitch

    Thanks for sharing your feedback! We completely understand how important a fast and smooth WordPress dashboard is, and we appreciate you taking the time to measure the impact and share it with our team.

    We’ve been actively working on optimizing the queries the plugin makes in the admin area to improve performance. If you’ve noticed any specific queries or requests that seem to be causing a slowdown, we’d love to hear more—your insights could really help us fine-tune things even further! Would you mind opening a new topic on our support forum here and sharing a copy of the report you got and the tool that you used so that we can try to replicate this on our end?

    Thanks again for letting us know about this! We appreciate your support. ??

    Thread Starter alekmitch

    (@alekmitch)

    Hi there,

    Unfortunately I’ve removed the plugin from relevant websites so I couldn’t do that. I can tell you I used the Code Profiler plugin. Not the most technical, but easy to use. I’m happy to hear you’re willing to look into this. I understand it could have been due to my particular setups, but I can’t recall anything specific I did that might have influenced your plugin. If you have a specific question about something, I can reply. Other than that, I think not much I can provide.

    Plugin Support Kenneth Macharia

    (@kmacharia)

    Hey @alekmitch,

    Thank you for the additional details.

    I’ve done some testing with this tool and while I can replicate execution times of above 0.5 on the Pro version, the Lite version is significantly lower on my end as shown in this screenshot. It also looks like the higher load times for the Pro and Lite version is attributed to the inclusion of Composer in the plugin which seems to affect the execution time. This disclaimer is also mentioned in the FAQ for the Code Profiler plugin:

    Why does Code Profiler warn me that I have multiple plugins using Composer?

    Composer, a tool for dependency management in PHP, is included in many popular plugins and themes. It is used to autoload PHP classes.
    Code Profiler will inform you if two or more activated plugins use it because you will need to take it into consideration when reading and interpreting the results. Let’s take an example:
    Assuming you have four plugins, #1, #2, #3 and #4. Both plugins #1 and #4 include and require Composer. WordPress will start and load plugin #1, which will run an instance of Composer to load its classes. Immediately after, WordPress will load plugins #2 and #3. Then, it will load plugin #4, which too will need to load its classes. However, plugin #4 will not start a new instance of Composer but, instead, will rely on the one from plugin #1 to load its own classes.
    As a result, the execution time of plugin #1 will increase (its instance of Composer is used to load classes for plugin #4 too), while the execution time of plugin #4 will decrease (it doesn’t need to start a new instance of Composer). Therefore, if you have a dozen or more plugins using Composer, it is important to take into consideration that the execution time of plugin #1 may be much higher than other plugins.

    I hope this helps to clarify.

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