Actually, there is a way to tell which plugins may be the problem. The P3 plugin (ironically, written by GoDaddy) can be used to generate a report of what each plugin is doing in terms of runtime. Longer run times will usually correlate with more resources consumed and give you some initial guidance on which plugins to examine first.

Actually, there is a way to tell which plugins may be the problem. The P3 plugin (ironically, written by GoDaddy) can be used to generate a report of what each plugin is doing in terms of runtime. Longer run times will usually correlate with more resources consumed and give you some initial guidance on which plugins to examine first.

Edit 2020:

So the P3 Profiler plugin might be dead. There is a new Health Check plugin from Automattic that should do an adequate job of replacing P3 and if you have shell access to your server/site, you can also use the WordPress Command Line Interface (wp cli) and run wp doctor check --all for more complete checks.

Actually, there is a way to tell which plugins may be the problem. The P3 plugin (Plugin Performance Profiler), ironically written by GoDaddy, is the way to get a report of what each plugin is doing in terms of runtime. Longer run times usually correlate with more resources consumed and give you some initial guidance on which plugins to examine first.

Actually, there is a way to tell which plugins may be the problem. The P3 plugin   (ironically, written by GoDaddy) can be used to generate a report of what each plugin is doing in terms of runtime. Longer run times will usually correlate with more resources consumed and give you some initial guidance on which plugins to examine first.