Hosting is where the public site runs, but the buying decision is larger than server space. A local business needs its domain to resolve, pages to load, forms to deliver, booking or payment systems to hand off, and an owner to recover the account when a provider relationship changes.
Use this comparison to choose a hosting model for a lead-generating or service-business website. It is not a platform popularity contest. It is a fit test for the people, workflows, and risks that have to remain reliable after launch.
Understand the three common models
| Model | What the provider usually manages | What the business must still decide |
|---|---|---|
| Hosted site builder | Infrastructure, platform updates, and a visual publishing environment | Plan limits, account ownership, forms, integrations, export, and content accuracy |
| Managed CMS hosting | Server layer plus some security, backups, or updates depending on the plan | CMS, plugins, theme, content, permissions, restore evidence, and support boundaries |
| Self-managed hosting | Compute, storage, or network resources | Operating system, runtime, updates, security, backups, monitoring, deployment, and recovery |
Labels are not contracts. Read the service description and agreement. “Managed” may exclude application updates, third-party plugins, forms, email, or restoring an application after a bad change. “Self-managed” may be reasonable for a technical team, but it is a weak fit when nobody is assigned to maintain it.
Score the hosting fit
Score each factor from 0 to 4 and multiply by the weight. This 100-point tool emphasizes operating risk rather than marketing features.
| Factor | Weight | Strong fit looks like |
|---|---|---|
| Owner capacity | 20 | The actual owner can publish, update, monitor, and recover the chosen environment |
| Customer-path support | 25 | Forms, booking, payments, redirects, integrations, and error states are supported and tested |
| Recovery and portability | 20 | Business-controlled access, backups, restore evidence, exports, and a documented exit path |
| Security responsibility | 15 | Updates, certificates, permissions, alerts, and incident ownership are explicit |
| Performance evidence | 10 | Representative templates and devices can be measured, improved, and monitored |
| Complete cost | 10 | Build, hosting, domains, tools, support, changes, and renewal costs are visible |
Use the resulting percentage as a fit conversation. A low score on recovery or customer-path support is a reason to resolve that gap before purchase even if the total looks acceptable.
Keep identity and recovery under business control
The business should normally control the registrar, DNS, hosting or platform account, billing method, recovery email, and multifactor method. A provider can have the role required to deploy or support the site without becoming the only person who can renew the domain or move the website.
ICANN’s registrant information explains the relationship between a registrant and registrar, including management, renewal, and transfer responsibilities. Use that as a prompt to verify the intended business registrant, current contact details, renewal notices, and transfer process.
Keep an account register with the service, purpose, owner, administrator, billing owner, renewal date, recovery method, export route, and provider access. The account ownership guide gives a broader handoff checklist for domains, analytics, Search Console, forms, payments, and other systems.
Ask what reliability means
A host may advertise uptime without explaining what the number excludes or how an outage is handled. Ask how the provider reports incidents, what support channel is available, who escalates a failure, and which parts of the stack are outside its control. A booking vendor outage, DNS error, or expired payment integration may not be fixed by the web host.
For a site with revenue paths, create synthetic tests for the homepage, primary service page, phone link, form, booking, checkout, and confirmation. Mark test submissions so they do not enter business reporting. Confirm that a visible success message corresponds to a real internal handoff.
Backups need the same specificity. WordPress’s official backup guidance explains why both files and database matter. Ask what is backed up, where it is stored, how long it is retained, how a restore is requested, and when restoration was last tested. A backup that cannot be restored is an assumption, not a recovery plan.
Assign security duties
Write down who handles platform updates, runtime versions, plugins, themes, access reviews, vulnerable dependencies, certificates, form abuse, logs, and incident communication. WordPress’s update documentation recommends keeping WordPress current and backing up before updates; a managed plan should state whether it actually performs and tests those actions.
Do not confuse a host’s infrastructure security with complete website security. Application code, credentials, user roles, third-party scripts, payment settings, and content changes still require owners. Remove unused accounts and use individual access rather than shared passwords.
Treat performance as a measured outcome
Ask which page templates, device conditions, and third-party scripts will be measured. Google’s Core Web Vitals documentation describes field metrics for loading, responsiveness, and visual stability. Those measures help investigate experience, but they do not turn a hosting plan into a ranking guarantee.
Record a baseline for the actual pages customers use, then compare after a theme, image, font, widget, or integration change. If the largest delay comes from a third-party booking or analytics script, moving hosts may not solve it.
Compare complete cost and exit friction
Calculate:
First-year hosting cost = plan + domain + required tools + support + owner hours + expected changes + migration or exit work.
Include premium plugins, transactional email, backups, staging, security tools, payment fees, and the cost of a provider ticket for a change. The website cost guide lists ownership costs that are often omitted from the first quote.
Ask what happens if the provider stops offering the plan, the business changes providers, or the site must move domains. Identify source or export rights, DNS access, media files, redirects, analytics, and form data. Exit terms are part of the hosting purchase because lock-in changes the true price.
Choose the model your team can operate
Choose a hosted builder when lower infrastructure responsibility and simple publishing fit the business. Choose managed CMS hosting when the site needs CMS flexibility but the owner wants help with the server and routine care. Choose self-managed hosting only when a named technical owner can maintain the complete stack and prove recovery.
When a website has outgrown its environment, document the constraint first. The platform comparison can help frame editing, integrations, ownership, and maintenance together. A new host should solve a real operating problem, not simply introduce another dashboard.