Choosing Hosting: The Technical Reality Behind Marketing Claims
Comparing hosting is hard, because what is sold is a technical service while what is marketed is a slogan. Below are the criteria that actually matter when deciding.
What the marketing phrases really mean
| Claim | What it actually means |
|---|---|
| Unlimited traffic | Bandwidth is unlimited but CPU, RAM and I/O are not. As traffic grows you hit those limits. |
| Unlimited storage | There is usually an inode (file count) limit. A 250,000 inode cap can strain a mid-sized site. |
| 99.9% uptime | 8 hours 45 minutes of permitted downtime per year. 99.99% allows 52 minutes. The gap can be critical. |
| SSD speed | SSD is now standard. The real difference is between NVMe and SATA SSD, and in server density. |
| Free SSL | Let's Encrypt can be offered free by anyone. It is not a differentiator. |
The criteria that actually matter
1. TTFB (time to first byte)
The single most honest metric. Test the provider's own site or a customer site. Under 200 ms on an empty PHP page is good; over 600 ms is a problem. Repeat the measurement at different times — server density rises in the evening.
2. Are resource limits transparent?
Quality providers publish CPU core count, memory limit, concurrent entry processes and I/O speed openly. If that information is not on the page, do not buy without asking.
3. PHP and software versions
Can you select PHP 8.3 or above? Is OPcache enabled? Are Redis or Memcached offered? These three matter more for WordPress and WooCommerce performance than the plan's price.
4. Backup policy
The critical questions: how often are backups taken? For how many days are they kept? Are they stored in a different physical location? Is restoration chargeable, and can you do it yourself? "Daily backups" means very little if restoring costs an extra fee.
5. Support quality
Ask a technical question before buying: "Can you enable the MySQL slow query log?" If the answer arrives within 20 minutes and is correct, that is a good sign. A template response now means a template response during an outage.
Shared, VPS, cloud: which and when?
| Shared | VPS | Cloud | |
|---|---|---|---|
| Best for | Corporate sites, blogs, small stores | Mid-sized e-commerce, custom software | Variable traffic, high availability |
| Management burden | None | Medium–high | High |
| Scaling | Limited | Manual | Automatic |
| Cost predictability | Fixed | Fixed | Variable |
Practical advice: do not move to a VPS before you genuinely need one. On an unmanaged VPS, an unpatched package is a bigger risk than every restriction of shared hosting combined.
Migration checklist
- Take a full backup from the old server and download it to your own machine
- Lower the DNS TTL to 300 seconds 24 hours before the move
- Test the site on the new server via your hosts file
- Prepare the SSL certificate before the DNS switch
- Plan e-mail accounts and MX records separately — this is the most commonly forgotten step
- Redefine cron jobs on the new server
- Do not shut down the old server for 7 days after the switch
A closing note
Hosting is a small line in the total digital budget, yet it forms the base of the site's entire performance. The difference between a cheap plan and a good one is typically a couple of hundred units of currency a year — less than the cost of a single lost customer. Cheap hosting is usually the most expensive decision.
Frequently Asked Questions
Does a small corporate site need a VPS?
Usually no. For static or lightweight CMS sites under 30,000 monthly visits, a good shared plan is enough. The need for a VPS comes less from traffic than from processing load: e-commerce, membership systems, frequent background jobs or custom software requirements make a VPS sensible.
Should the server be located in Turkey?
If most of your visitors are in Turkey, a local server gives a 20–60 ms advantage that shows in LCP. With a CDN in place, however, the gap largely closes. Where you have legal data residency obligations, location is a requirement rather than a preference.
