It’s that time again, we’ve got another round of feature updates to share with you regarding exciting changes to Kinsta’s hosting plans and our MyKinsta dashboard!
Our team has listened to your feedback, and we’ve made it happen. While other hosts are raising prices, we are dedicated to finding ways to add even more value to our existing plans.
Previously our starter plan required that you pay annually to be eligible for a free migration by our support team. No more! 🥳 All plans from Starter to Enterprise now include one or more free migrations, no exceptions.
You can see how many free migrations you have available in the MyKinsta dashboard under Migrations. These changes are already in place across the board.
We’ve added more free migrations (handled by our team) to a few of our hosting plans. Changes:
This includes all types of plans, such as our 15% discount for nonprofits and charities.
We’ve added SiteGround, A2 Hosting, and tsoHost to our unlimited free migrations offer! If you have a lot of WordPress sites and are thinking of moving to Kinsta, make sure to check out this offer.
PHP workers determine how many simultaneous requests your site can handle at a given time. To put it simply, each uncached request for your website is handled by a PHP Worker.
We recommend our Business 1 or higher plans to those of you running membership sites, ecommerce (WooCommerce, Easy Digital Downloads), LMS, etc. This is due to the fact that they typically have a lot of uncacheable content and concurrent users.
To improve performance for you, we’ve increased the number of PHP workers on the following plans:
This change has been made for all current Kinsta clients.
404 pages can be very resource intensive. A lot of WordPress sites, especially large membership sites, generate more 404 errors than you might think. Perhaps you changed the location of a page and forgot to add a redirect, or you have a wrong link on something you shared on social media.
In other words, there are many things that cause a visitor to end up on your 404 page. These pages also tend to have queries to pull alternate search results which then hit the database.
To ensure better performance on your WordPress site, Kinsta now caches 404 pages for 15 minutes. The
X-Kinsta-Cache header value will show a
HIT, meaning it’s being served from cache. If you create a page which previously was a 404, the cache is purged immediately.
Our MyKinsta analytics tool can help you determine the exact amount of 404 errors happening on your site.
It’s important to clarify though that we don’t cache all 404 requests. There are two different kinds: those from PHP pages which land on your 404 page, and those from missing files or images which no longer exist or have been moved. We cache 404 pages, 404 requests to missing files and images are handled differently.
We want our analytics and caching statistics to be as accurate as possible. It’s important because when troubleshooting performance issues, you typically will look at your total cache HIT ratio, which you want to be as high as possible. Therefore, we’ve now added POST requests to our reporting.
POST requests cannot be cached, apart from some highly specialized setups. The
X-Kinsta-Cache header value will show a
BYPASS for these requests. These are not to be confused with blog posts or any type of WordPress post (which are cacheable). A POST request is used to send data to the server. So for example, the data sent when you submit a web form.
Kinsta offers 6 different types of backups, one of those being downloadable backups. These are an archive file with your website’s files as well as the SQL file containing the contents of your database.
Previously when you downloaded a backup you would simply get a message via the MyKinsta dashboard. However, many of you let us know that you also wanted an email. So in addition to the MyKinsta message, you will also now get an email with a download link when your downloadable backup is ready.
If you like seeing these smaller updates that the Kinsta team is constantly pushing out, let us know on Twitter @kinsta.
Send this to a friend