Powered Cache is an easy to use plugin which contains a number of useful features in the free version and includes a number of extensions in the premium version of the plugin. After you have installed and activated the plugin on your child site it will add a new admin menu on your site named; Powered Cache In order to have page caching work using the Powered Cache plugin, you will need to go into the basic options settings and then enable it. You can set if you want Gzip compression to be enabled in the sites .htaccess file as
If you are looking for a very lightweight plugin to help improve your site performance. The PhastPress plugin is worth taking the time to check out. After you have installed and activated the plugin it will add a new sub-menu under settings in wp-admin; Settings > PhastPress The PhastPress plugin settings are broken down into plugin, Images and HTML, CSS and JS. The plugin includes image optimization using a free image optimization service API, being able to inline critical CSS, load all JS script asynchronously. You can also minify HTML, defer iframe loading by being able to lazy load them.
The site health check feature is a new feature in WordPress 5.2. If you have the MainWP child plugin already hidden from the list of plugins on the child site using the branding extension for MainWP, you may also want to hide the MainWP child plugin from showing on the info tab of the Site Health page. There is now an easy way to hide themes and plugins from showing in the site health info tab, using the Site Health Manager plugin. First, you will need to install and activate the Site Health Manager plugin on all the connected child
If you need to log site emails but require more control over what data is being logged and how long that data is being stored, WP Mail Logging is a solid plugin that can be installed. After you have installed and activated the plugin, it will add a new admin menu called; WP Mail Logging To view logged email, you can view those from; WP Mail Logging > WP Mail Logging The plugin setting can be found from; WP Mail Logging > Settings > General Settings By default, on plugin deactivation and uninstall, the data will not be removed from
In version 5.2 of WordPress, the site health check was added. It allows users to gain information about possible issues, and how to create a debug set of information. In a number of cases, you may want to remove the site health check page from being accessible on a child site, to ensure clients do not have to deal with being misled about issues. It is possible to remove the Site Health check page in wp-admin from showing on a child site. Normally, it would show from; Tools > Site Health The first way to remove the site health check
WordPress 5.2 introduced the new Site Health feature for checking the health of a site. There is already a plugin to remove the Site Health feature from WordPress core in version 5.2. It is already possible to set which of the Site Health tests you would like to enable on a site using the Site Health Tool Manager plugin. Site Health Settings You can deselect which tests you do not want to run in the site health checker. The MainWP Bulk Setting extension work with the Site Health Tool Manager plugin, which means you can globally set which tests you
Varnish is a fast server-side web application accelerator. A number of Managed WordPress and other hosts already have Varnish installed and make it easy to enable on your child sites. In this example, we are going to show how easy it is using Cloudways for enabling Varnish on your child site (which is using WooCommerce), then for setting the correct rules for Varnish all through an easy-to-use UI. First, login to Cloudways and then select the server which your child site is running on. Apps > Application Settings > General Settings By default, Varnish will not be enabled and you
WordPress 5.2 includes a new, exciting feature which will show the health of your site. This helpful feature is on track for release on May 7th. You can access the site health feature on your site if you are an admin user in wp-admin from; Tools > Site Health The first page will end up running a series of tests on your site. Those test results will be displayed back on the page. The percentage, which shows at the top of the page, might be removed before WordPress 5.2 is released and replaced with a more meaningful display of results.
The single biggest child site issue that you can end up dealing with is why is the site email not being sent. You could use an SMTP plugin and then use SMTP creds to connect. But using a transactional email provider makes it easier in knowing that your child site email will be delivered correctly. The delivery of site email can be a pain to deal with on child sites. If a site is using WooCommerce or a form plugin like Gravity Forms, you want to ensure that form notifications and customer order notifications are being sent out to customers.
If you use MainWP for managing your child sites, you already have a way to update plugins, themes, and push different code changes to those sites without having to deal with multisite performance issues. Multisite allows many subsites to share common plugins and themes. In addition, all sites will end up sharing the same database and server resources. The downside to sharing database and server resources will be explained later. Multisite only database tables wp_site wp_sitemeta wp_blogs wp_blogmeta – New added in WordPress 5.1 wp_blog_versions wp_signups wp_registration_log Global database tables shared over all subsites wp_users wp_usermeta Whilst each subsite will