How to Read a Hosting Plan: Limits, Features and Fine Print
Two hosting plans can advertise the same number of websites and provide very different services. A website allowance tells you how many projects may be added, not how much computing capacity each receives.
Read the plan as a specification. For every feature that matters, identify the allowance, the restriction and what happens if you exceed it. Use this guide alongside the plan comparison worksheet.
Website slots are not resource guarantees
Ask whether storage, databases and processing allowances apply per site or across the account. A subscription with ten site slots may still have one shared resource budget.
Check whether subdomains, staging copies and development sites count toward the limit. The meaning of “website” varies by product, so use the supplier’s definition rather than assuming one familiar control panel’s behaviour.
Storage has more than one limit
A gigabyte allowance does not describe the whole storage policy. File-count limits, database restrictions and rules about backups or large media can affect an otherwise small account.
Record what contributes to usage: mailboxes, logs, staging copies and backups may be counted differently. “Unmetered” should lead you to the acceptable-use policy, rather than to an assumption of unlimited capacity.
Look for processing limits
CPU, memory, concurrent processes and request limits can matter when a website performs dynamic work. A plan card may show only selected allowances; ask where the complete limits are documented.
| Term | Useful question |
|---|---|
| CPU allocation | Is it shared, reserved or subject to a usage policy? |
| Memory | Is the stated limit for one process, one site or the whole account? |
| Concurrent work | What happens when simultaneous requests reach the limit? |
| Overage | Does excess use cause a warning, restriction, charge or suspension? |
Do not translate these figures into a universal monthly-visitor capacity. The application, cache behaviour and amount of work per request affect the result.
Read included features as separate services
For backups, check frequency, retention, included data and restore access. For staging, check whether the copy is isolated and whether pushing changes can overwrite live data. For email, record mailbox count, storage and renewal terms.
A CDN allowance needs its own scope. It may improve delivery of eligible assets without moving your database or accelerating every customer action. The edge and cloud explanation separates those roles.
Check software compatibility
List required runtime versions, extensions, scheduled tasks and access methods. For WordPress, consult the current official requirements, then check requirements for your own plugins and theme.
A one-click installer is convenient, but it does not establish long-term version support or compatibility with every extension. Ask how upgrades and unsupported versions are handled.
Separate management from marketing
“Managed”, “business” and “premium” need a task list. Confirm who maintains the server, updates the application and investigates failures. Read exclusions for custom code, third-party plugins and malware cleanup.
Support availability, first response and resolution are different promises. Our support comparison guide explains what to record without relying on unsupported response-time scores.
Keep a copy of the specification
Save the dated plan details, relevant policy pages and answers to important questions. Confirm the checkout term and renewal before committing. If an essential feature remains unclear, resolve it before buying rather than filling the gap with an assumption.
