WordPress network vs Separate installs
No real difference either way, really. Network installs make the most sense when you want all the sites to share a single set of users. But the basic table handling is pretty much the same either way.
No real difference either way, really. Network installs make the most sense when you want all the sites to share a single set of users. But the basic table handling is pretty much the same either way.
Use WordPress’ conditional tags, global variables, defines, class checks and the like. For instance like so: <?php // load helper functions – always require_once get_stylesheet_directory() . ‘/inc/helper-functions.php’; // load admin functions – for back-end only if ( is_admin() ) require_once get_stylesheet_directory() . ‘/inc/admin-functions.php’; // load WooCommerce functions – when WooCommerce is active if ( in_array( … Read more
I have never benchmarked this but… Since every HTTP request is a distinct request, the whole WordPress Core will load on every request either way, and a little bit more code loads for Multisite. So, it seems to me that two installs should run slightly better than a single multisite install, though I doubt you … Read more
lets say we’re registering 3 post types: is it worse for performance to do this in 3 different plugins (one for each post type), than registering all 3 in one plugin? in other words, is using an extra plugin adding to the load time, even if it doesn’t do anything? The technical process of plugin … Read more
In practice in wordpress the number of SQL queries has the biggest impact on the performance of the site and the quality of the PHP code is usually irrelevant. In theory for any additional PHP file that you include you delay your code by the time needed to fetch the file from the disk. This … Read more
I fear the answer here is that redirecting will just never come with good performance. Especially doing it via PHP, because then it’s handled rather late. You could think about doing it via apache in particular the .htaccess file, which intercepts way earlier, before PHP/WordPress even come into play. Which will be better, but of … Read more
The rule of thumb is not to do any caching, except for object caching, for logged in users. Actually IIRC object caching will give you exactly what you want. But if you have to do it your way, you should make your cache keys to be based on the query and have different cache for … Read more
Well I looked at the website using FireFox I hit F12 and went to the Network tab. Hit the refresh button within the tab. This is the result I got a bunch of your CSS and images are taking a really long time to load. https://developer.mozilla.org/en-US/docs/Tools/Network_Monitor#Performance_analysis
First, make sure you actually deleted the plugin and did not just disable it. Assuming that the plugin was deleted, one of the following could cause this: Bad Cron Jobs Some plugins will create cron jobs and not remove them when the plugin is disabled or deleted. These can easily slow sites down if set … Read more
You’ve touched on a few things here, and there’s both the server and the frontend response time that you’re battling with. You might have issues with both. It’s worth noting firstly that PageSpeed (and the style recalcuating alert in the Chrome timeline) both deal with front-end aspects only – in slightly different ways though (another … Read more