Choosing Hosting for a New Website: What Your Designer Should Set Up

Here's an odd truth about web projects: clients will debate a homepage colour for two weeks, then approve the hosting in a single WhatsApp message. Yet choosing hosting for a new website decides how fast every page loads, whether your email arrives, what happens when something breaks, and how painful it is to ever leave. The design is the car. Hosting is the road. This guide covers what actually matters when choosing hosting, and what a responsible designer should be setting up on your behalf.

What genuinely matters when choosing hosting

• Disk speed: NVMe storage loads database-driven sites like WordPress several times faster than the old spinning disks still sold by budget hosts. For visitors on 4G in Nepal, that difference is the gap between staying and leaving.
• Resources, honestly stated: "Unlimited" hosting at NPR 1,500 a year is unlimited the way a momo buffet is unlimited: until you actually try. Look for stated CPU, RAM and inode limits instead of adjectives.
• Backups included: daily, automatic, kept for weeks, restorable by you. If backups cost extra, the price on the box isn't the price.
• Free SSL: non-negotiable in 2026. Any host charging separately for a basic certificate is telling you about their whole business model.
• Support that answers: test it before buying. Send a pre-sales question at 9 pm and time the reply. That's your future outage experience.
• Current PHP versions: hosts still defaulting to ancient PHP are hosts that will hold your software back and your security open.

What matters much less than advertised

Bandwidth numbers are mostly theatre for small business sites. So is "99.99% vs 99.9% uptime" in marketing copy, since the guarantee is only as good as the compensation behind it. And the first-year discount price matters far less than the renewal price, which is where budget hosts quietly triple the bill.

The ownership question, again, because it matters most

Whoever holds the hosting account controls your website. If your designer buys hosting under their own account and resells it to you informally, you have a landlord, not a website. The professional arrangement is simple: the account is created in your name, on your email, and the credentials are handed over at launch. At WebsNP this is written into every project: on final payment, you own the code, the domain and the hosting. A designer who resists this arrangement is answering a question you should be glad you asked early.

What your designer should set up before handover

A properly delivered site arrives with the hosting already earning its keep. The checklist we work through on every WebsNP launch:

• SSL installed, https forced everywhere, no mixed content warnings
• Daily backups configured and one restore tested
• Business email accounts created, with SPF and DKIM records so your mail doesn't land in spam
• Caching enabled and the site tested on mobile data speeds, not just office WiFi
• PHP on a current version, unused plugins and test files removed
• Credentials for hosting, domain and CMS handed over in writing, plus a recorded training video

How the first year should work

For most new sites, decent shared hosting in Nepal runs NPR 3,000 to 10,000 a year; heavier e-commerce sites more. With WebsNP design packages the first year is simpler than that: hosting on our own NVMe servers is free, along with the domain and SSL. You launch with everything configured by the people who built the site, then at renewal you decide freely, because you own the account and can stay or take everything elsewhere. Choose hosting the way you'd choose the road before buying the car. Five distracted minutes now is years of loading spinners later.