I recently moved my WordPress site to Kinsta WordPress Hosting, and since the migration I’ve been dealing with slow load times, plugin conflicts, and a few dashboard errors. I’m not sure if it’s a server setting, caching issue, or something in my WordPress setup, and I need help figuring out what caused it and how to fix it without breaking the site further.
I Settled on Kinsta After a Long Stretch in WordPress
I should give some background first. I’ve been around WordPress for about 15 years. I ran an agency for 10 of them. I also did a WordPress podcast for 11 years, and I spent 3 years working inside a WordPress hosting company. So I’ve seen hosting from the customer side, the agency side, and the company side. After bouncing through a pile of providers, I ended up on Kinsta. For me, it’s been the one I stuck with. If your budget has room for it, I’d point you there without much hesitation.
Speed
What hit me first wasn’t some homepage score screenshot. It was the backend. The admin area felt quicker right away. Opening the post editor, hopping between settings pages, moving through routine tasks, all of it felt tighter. If you spend hours a week inside wp-admin, you notice this stuff fast.
I expected decent performance because I was spending around three times more than I used to spend running sites on my own servers. So yeah, speed needed to be there. The part I didn’t expect was the relief. Years ago I did server admin work, around 20 years back, but I’m rusty now and I don’t miss babysitting boxes. Handing that off took work off my plate in a way I felt on day one.
Control Panel
Small confession. At the hosting company where I worked before, we lost deals to Kinsta a lot. I knew why. We had some of the same functions on paper, but users had to jump through weird technical steps to reach them. Most people don’t want a scavenger hunt. They want buttons, clear labels, and a panel where common jobs take a minute instead of a doc search.
The parts I keep using are these:
- Staging and backups, this is the cleanest setup I’ve used. It saves time and cuts down on dumb mistakes.
- DNS management, easy to find, easy to edit, no drama.
- Traffic graphs and reporting, useful for checking activity and keeping an eye on monthly limits before you get surprised.
- Activity log, this one matters more than people think. I can see what changed, who changed it, and even when support touched something.
It doesn’t try to copy cPanel and stuff every possible switch into one screen. I like thta. Fewer dead-end options, less clutter, less time wasted.
FTP Access
This comes up a lot, so I’ll keep it plain. Kinsta’s managed WordPress hosting includes FTP access. If you need to push files straight to the server, you’re covered.
A few FTP clients I’d look at:
FileZilla is the default pick for a lot of people because it’s free and familiar. I’ve used it plenty. It does the job. Once you start moving bigger files or a huge batch, it feels slow.
Commander One is the one I’d tell Mac users to try if they want something with more range. It’s paid. Still, it handles FTP and SFTP well, and archive support is handy if you want to compress files before upload. I found it nicer for dev work than the usual free picks.
Cyberduck gets recommended often because it’s free and open source. I’ve seen enough people hit snags with ordinary file moves and renames thoguh, so I wouldn’t call it my first pick.
WinSCP is still a dependable option on Windows. It has been around forever. The interface looks old, no point pretending otherwise, but it tends to work when you need it to work.
Pricing
Kinsta is not the cheap option. No point dressing it up. A few months ago my monthly bill went up by $10. I noticed, shrugged, and kept going. For what I’m getting, I still think the math works.
The rough pricing last I checked was $35 per month for one site, and $70 for two sites, which is the plan I’m on. If your hosting budget is tight, this will feel steep. If your site matters and you’re tired of wasting hours on hosting nonsense, the higher price starts making sense prety fast.
2 Likes
Migration issues on Kinsta are often self-inflicted by old settings from the previous host. I’d check these in order.
-
Turn off every cache plugin. WP Rocket, W3 Total Cache, LiteSpeed Cache, Autoptimize combos, all of it. Kinsta already handles page caching at the server level. Two cache layers often wreck admin screens and stale pages.
-
Purge Kinsta cache from MyKinsta and from the WP admin bar. Then test while logged out. Logged-in speed is a bad benchmark.
-
Check PHP version. Some older plugins throw dashboard errors on newer PHP. Switch versions in MyKinsta, test, then read the error log. Don’t guess.
-
Use Kinsta APM. This matters more than homepage speed tests. It shows which plugin, query, or external call is slow. If one plugin is adding 800ms to admin-ajax or REST calls, there’s your problem.
-
Disable plugins in batches. Five at a time. Faster than one by one. Conflicts usually show up fast. I’ve seen security plugins and backup plugins fight Kinsta’s stack more than anything else.
-
Check cron. Missed or stacked wp-cron jobs make wp-admin feel laggy. Kinsta support will tell you if a real cron setup makes sense.
-
Look at Cloudflare settings if you added your own layer on top. Extra minify, Rocket Loader, bot tools, and cache rules often cause weird brekage.
I’ll disagree a bit with @mikeappsreviewer on one point. Faster hosting does not always fix a messy WordPress setup. Kinsta is solid, but bad plugins stay bad on expensive hosting too.
If you need to inspect files, use SFTP and look at wp-config.php, debug logs, and mu-plugins. Commander One is a clean option on Mac for this. Easier than fighting clunky FTP apps, imo.
One thing I’d add to what @mikeappsreviewer and @caminantenocturno said: verify the migration didn’t drag over junk from the old host at the database/config level.
I’ve seen Kinsta get blamed when the real problem was:
- old hardcoded CDN URLs
- leftover object cache drop-ins
- bloated
autoloadoptions inwp_options - broken transients
- bad
.htaccessrules copied from Apache-style setups
Kinsta’s stack is pretty opinionated, so old host tweaks can turn into weird dashboard behavior fast. I’d inspect wp-content for stray files like advanced-cache.php, object-cache.php, or odd mu-plugins that came along for the ride. Slight disagreement with @mikeappsreviewer: a “fast backend” isn’t universal after migration if the DB is a mess.
Also check mixed HTTPS settings and force-SSL rules. That can create admin loops, missing assets, and random slow loads that feel like server lag but aren’t.
If you want to inspect files cleanly over SFTP on Mac, Commander One is actually pretty nice for this. Easier than wrestling with some older FTP apps, imo.
If the site is still acting up, clone it to staging and test theme + must-use plugins first. That usually exposes the real issue prety quick.