Hosting is the one thing you never see until it fails
Most of us pick a host once, pay the invoice for years, and never open the account again. That works fine until the busiest month of the year arrives and something quietly buckles. This is a fifteen-minute checkup you can do tonight, from the dashboard you already have. A bit geeky, but this is one worth sitting through.
Minute 1 to 3: Find out what you are actually paying for
Open your hosting billing portal and answer three questions. When does the plan renew, and is auto-renew switched on. What the plan actually includes in storage and bandwidth. And what the next invoice will be, because introductory pricing has a habit of quietly tripling.
Write the renewal date down. If it lands in December, you want to know that before the season, not during it, because a renewal surprise plus a traffic spike is a bad combination.
Minute 4 to 6: Test the speed you actually deliver
Run your homepage and one product page through a free speed test such as Google PageSpeed Insights. Use your phone, not just your laptop. Note the load time and, if the report shows it, the time to first byte, which is the part your host controls.
A fast theme cannot rescue a slow server. If your pages consistently take several seconds before anything appears, the server should be on your shortlist of suspects.
Minute 7 to 9: Ask support two questions
Send your host a short ticket and see what happens. Ask them which PHP version your account runs, and how long a restore from backup takes if you request one.
Two birds, one ticket. The answers matter, and so does the reply time, because a host that takes two days to answer a pre-sales question will not sprint when your checkout is melting down. As a guide, modern WordPress runs comfortably on PHP 8.x, and if your account is still on PHP 7.4, which reached end of life back in 2022, that is a genuine sign the host is coasting behind the curve.
Minute 10 to 12: Verify a backup you could actually restore
Look at the backup section of your dashboard and check three things. When the most recent backup ran. Whether it covers files and the database, not just one of them. And whether you can download a copy yourself.
Then do the uncomfortable part: download one backup and glance at it. A backup that lives only in the same account as the website, with no copy anywhere else, is a photo of your business stored in the same drawer as the house keys.
Minute 13 to 15: Score it honestly
Tally the results. A slow time to first byte, a support reply that took days, an ancient PHP version, a backup you cannot download. Any two of those and your plan deserves more than a shrug.
If the audit went well, you have earned a quiet coffee and a diary reminder to repeat this in six months. If it went badly, here is the calm version of switching, because the worst time to migrate is the week everything goes wrong.
If the audit says move, move slowly
Shortlist three hosts that publish their setup honestly: current PHP versions, staging environments, and offsite backups, stated plainly on the plans page. Most reputable hosts will migrate a WordPress site for you, often free, so let them. Keep the old plan running for a week or two after the move, test the site thoroughly, then cancel. Do all of it on a quiet weekend morning, never the week before your biggest sale.
What good looks like
You are not hunting for a perfect score. You are hunting for the absence of silent problems: a host that replies in hours rather than days, runs a PHP version from this decade, keeps restorable backups you can download, and serves pages fast enough that your speed tests blame something other than the server.
Fifteen minutes twice a year is the entire price of that peace of mind. Put it in the calendar now, before the season makes everything urgent at once.
Want more like this? Join MOKU Club for free. Weekly resources, early access to new guides, and occasional templates you can actually use. Join below.
