Wordpress how many queries is too many

Everything went fine except for a problem I have with the new installation. Please note that I have moved from a regular VPS to a kinda powerful and fast dedicated machine. The thing is that now, the website is slower than when in the previous server.

It takes seconds to load a page and according to Chrome's Dev Tools network panel, it has a period of seconds to the get the first response byte TTFB , which is insane.

With these last two actions, I lowered the loading time to seconds, which is a lot for small site a few hundreds of posts and pages , with no comments enabled. I still have the TTFB period. After that, I installed the Query Monitor plugin and found out that, at every page load, WP performs hundreds ranging from to database queries and, in some cases, even database queries. Honestly, I am quite lost here. I mean, on one hand I have this strange database behavior I cannot really understand. I am lost.

Any help is greatly appreciated. Apologies for my english not my language and please let me know if the is some important information missing.

These are just par for the course. No reason to be scared of using them, of course. When you add more plugins that do something on the front-end of your site, that plugin is going to use extra files to make it work. It is going to pull in javascript files and CSS stylesheets.

In some cases, it might even be pulling in font files, duplicate versions of Jquery, and more. All of these files need to be loaded up for your site visitors so the plugin works. Every JS file, every CSS file, every image… every single file represents another call to your web host. Another HTTP request. The more HTTP requests, the more your server works. The longer it takes to download all the files.

These requests can really stack up, too. You can run your page through a speed tester like Pagespeed Insights or GTMetrix and see that hundreds of files are being downloaded per page view.

Just like HTTP requests, your plugins are likely making more database queries. In practice, this is really only an issue for poorly designed Wordpress plugins. For instance, some will sit there and blindly log everything in a database table without any means of controlling it.

If you want to have a look at just how many queries are being executed on your site, you can install the Query Monitor plugin. For instance, there are instances where plugins may share the same internal identifiers for functions, filters, tables and the like. That will cause them to throw all kinds of errors.

In some cases, you simply have duplicate functionality. Two or more plugins sitting there trying to do the same thing and they keep bumping heads. One of the biggest attack points on Wordpress is the add-ons. To some, Wordpress has developed a reputation for being full of security holes.

In almost all cases, it is the add-ons that open it up to problems. You get the point. Plugins bring the possibility of problems. Basically, there are things you can do to help with the payload and risks of running a lot of plugins. People love to give and get hard numbers here. As if there is some kind of numerical cut-off. That would be great, but in the real world see how easy it is to only run 5 plugins.

It is pretty much impossible unless your site has almost nothing on it. If you run stronger hosting like a VPS from Cloudways , which is what I use , then you can run more plugins. Well, there are several things to look at…. Again, less the better. You absolutely need to be using a caching plugin. It is one of the most obvious things you can do to minimize the impact of plugins.

Now, there are a lot of performance plugins out there. Assigned support staff: Shekhar Bhandari. The most extent is product category page hidden link Where your plugin is calling queries from Plugin: sitepress-multilingual-cms 0, Plugin: wpml-string-translation 44 1 0, Do you think, we can do something about it? Languages: English English. So, the fact is that if you have more plugins and themes with a large number of strings WPML will try to translate them which adds significant load and you will feel the performance issue, which is normal somehow.

In order to reduce this, you can reduce the frequency a plugin queries the database. If you can find an alternate plugin that makes fewer database calls, you may consider using that one instead. Plugins that query large amounts of data and then perform an action with the data will impact performance. In general, plugins that perform overly complex operations should do them off server, and not in your WordPress hosting environment.

At run time, the index will consume huge amounts of resources. Over time, the site slows to a crawl, and in extreme cases can crash the server if it runs out of threads. This is a big issue for new users. Which plugins to use? Which ones are best? I recommend that you pick plugins that have good track records. How to determine that? Well, look at the number of downloads. Look at the plugin ratings. Look at how many support threads have been answered.

Look at how many people are saying that it works. Read some reviews about it. Look at the credibility of the author. Hopefully after all this, you should have your answer. You can see all these metrics on the WordPress plugins repository. Some would say that too many plugins can slow your site down. Some may say the answer to how many WordPress plugins is too much, is as many as you need as the number of plugins does not slow down your site. Number of poorly coded plugins do.