What is web hosting and how do you choose it? Hosting types, selection criteria and effects on website speed

What is web hosting? The difference between a domain and a server

Web hosting is a rented infrastructure service that keeps a website’s files, database and often email accounts on a continuously running server and delivers that content to visitors’ browsers. A domain name is the website’s address; when the address is entered, DNS records direct the request to the hosting server. Although often purchased from the same company, these are separate services renewed individually. A hosting package generally consists of the following components:

• Storage space: Storage where website files, images and local backups are kept.
• Database: MySQL or MariaDB storing pages, posts and settings in content management systems such as WordPress.
• Processing resources: The CPU and memory allocation running PHP code.
• SSL certificate: The certificate encrypting traffic between browser and server and allowing the address to open with HTTPS.
• Control panel: File, email and DNS settings through cPanel, Plesk or the provider’s own dashboard.
• Email: Business mailboxes connected to the domain; not included in every package.

The practical answer to “What is hosting?” is the place where a website owner entrusts code and data. If that place is slow, frequently unavailable or not backed up regularly, both visitors and search engines feel it, however carefully the website is designed.

Hosting types: shared, VPS, cloud, managed WordPress and dedicated

Web hosting types differ according to how many accounts share server resources and who manages the server. In a shared package, a single physical machine is divided among many accounts; on a dedicated server, the entire machine belongs to a single customer. The options in between balance isolation and management workload in different proportions.

Which type suits which website?

When choosing hosting for a corporate website, the deciding factor is how dynamically it operates. For a promotional website consisting of service pages, a contact form and a blog, a well-configured shared or managed WordPress package is usually sufficient because most pages can be served from cache. As features requiring the server to recalculate on every visit increase, such as member login, carts, live stock or intensive search filters, a VPS or cloud server offering isolated resources becomes meaningful.

A dedicated server is for projects operating under consistently high loads with their own system administrator. For a business without a technical team, an unmanaged VPS or dedicated server can turn resource gains into security and maintenance risks; a managed package is a safer route.

Technical criteria for choosing web hosting: PHP, web server and storage

The first technical information to examine when choosing web hosting is the software versions the website will run on and the server hardware type. This information is not always clearly stated on package pages; the provider can be asked in writing before purchase.

PHP and database versions

WordPress.org’s official server requirements pagerecommends a hosting environment offering PHP 8.3 or later, MariaDB 10.11 or later or MySQL 8.0 or later, and HTTPS support. On the PHP side, the version’s support period also matters: according to php.net’s supported versions table , as of September 26, 2026, branches 8.2, 8.3, 8.4 and 8.5 are supported, and security support for 8.2 ends on December 31, 2026. The same page states that users of unsupported versions may be exposed to unpatched security vulnerabilities.

Web server: LiteSpeed, NGINX and Apache

WordPress.org recommends Apache or Nginx as the most robust and comprehensive options; other servers supporting PHP and MySQL also work. LiteSpeed, used by some providers, is associated with the LiteSpeed Cache plugin for WordPress. According to the plugin’s WordPress.org page, server-level caching works only on LiteSpeed-based servers or with the QUIC.cloud CDN; general optimization features can be used on any server, including Apache and NGINX.

Storage type: NVMe and SSD

Storage affects the speed of database queries and file reads. NVMe is a type of SSD operating over the PCIe bus, designed for higher read/write capacity than older SATA-connected drives. If the package page says only “SSD,” ask separately about the drive type and the account’s disk operation limit.

Resource limits: CPU, memory, entry processes and inodes

In a shared web hosting package, the main constraint is the processing resources allocated to the account rather than storage space. One example of a system regulating resource sharing is CloudLinux’s LVE technology; according to CloudLinux documentation , its purpose is to prevent a single website from bringing down the entire web server. To do this, it sets separate CPU, memory, disk operation and process limits for every account. The main limits that may appear in package information are:

• CPU (SPEED): The processing power allocated to the account; a website reaching the limit begins responding slowly.
• Physical memory (PMEM): The RAM PHP processes may use; visitors may see a 500 or 503 error if exceeded.
• Entry processes (EP): The number of dynamic requests running simultaneously; the server returns a 508 error when the limit is reached.
• IO and IOPS: The amount of data that can be read and written and the number of operations per second.
• Inodes: The number of files and folders the account can hold; cache files and mailboxes can fill this count faster than expected.

“Unlimited traffic” or “unlimited storage” does not mean these limits do not exist. When comparing packages, the most reliable approach is to request CPU, memory, entry process, IO and inode values from the provider in writing.

Backups, SSL and technical support

Backups are one of the least prominent features on package pages but the most sought after when a failure occurs. The real question is not whether backups exist, but how often they are made, how many days of history are retained, whether they are stored separately from the server and whether restoration is possible through the dashboard. Keeping the backup only on the same server also puts the copy at risk if that server fails.

An SSL certificate is a basic requirement for every website, and HTTPS support is explicitly included in WordPress.org’s requirements. The certificate may be included in the package or purchased separately; in either case, check whether it renews automatically and covers subdomains.

For technical support, examine the channels and hours of availability and who intervenes in a server-related problem. On unmanaged VPS and dedicated servers, support is often limited to hardware and networking. If a service-level agreement (SLA) exists, rights during an outage are read from that document.

Data center location and a KVKK note

Data center location matters for two reasons: network distance to visitors and the country where personal data is processed. If most visitors are in Turkey, a server close to them in network terms helps shorten connection setup; web.dev also lists connection and TLS setup among TTFB components. A content delivery network (CDN) can partially compensate for this distance by serving static files from different locations.

On the legal side, hosting a website that collects personal data through contact forms, membership or orders on an overseas server requires assessment under Law No. 6698’s provisions on international transfers. According to the KVKK (Turkey’s Personal Data Protection Law) international transfers page , the amendment to Article 9 of the Law introduced a tiered regime:

1. The Board has issued an adequacy decision concerning the destination country, a sector in that country or an international organization.
2. If no adequacy decision exists, one of the appropriate safeguards listed in the Law is provided; standard contract texts were adopted by Board Decision No. 2024/959 of June 4, 2024.
3. If neither exists, one of the limited exceptional circumstances specified in the Law applies.

The same page states that, as of September 26, 2026, the Board had not yet made a determination regarding countries providing adequate protection. This section is not a legal opinion; when selecting a server location for a website processing personal data, the best approach is to assess the situation with a lawyer.

How does hosting affect website speed and Core Web Vitals?

Web hosting affects page speed most directly through TTFB (Time to First Byte). web.dev’s TTFB guide defines this as the total time spent on redirects, DNS lookup, connection and TLS setup, and the stages until the server sends its first byte. According to the guide, most websites should target 0.8 seconds or less; above 1.8 seconds is considered poor. TTFB is not a Core Web Vitals metric, but it can delay the metrics that follow it.

web.dev’s LCP optimization guide states that a high TTFB can make reaching the 2.5-second LCP target difficult or even impossible. Google Search Central also explicitly recommends that website owners aim for good Core Web Vitals for search success and a good user experience. According to web.dev, thresholds are evaluated at the 75th percentile of page loads, with mobile and desktop assessed separately. The server’s contribution to each metric is as follows:

The server’s impact is not limited to speed. According to Google’s crawl budget guide for large websites, Googlebot’s crawl capacity increases when a website responds consistently and quickly; when response times increase or the server returns 5xx errors, Google crawls less. Fixes involving images, caching and code are covered in the Core Web Vitals guide ; improvements covering server and WordPress settings fall within the WordPress speed optimization service.

Common mistakes when choosing web hosting

Most mistakes in web hosting selection arise from comparing packages only by price and storage space. The situations causing the most problems after setup are:

• Deciding by the first-year price: The renewal fee may differ from the promotional price; comparisons should use the renewal amount.
• Trusting the word “unlimited”: Even if storage and traffic appear unlimited, shared servers have CPU, memory, entry process and inode limits.
• Staying on an old PHP version: If the website is left on an old version even though a current branch can be selected in the dashboard, the risk of software whose security support has ended remains with the website owner.
• Opening accounts in someone else’s name: If the domain and hosting are in the designer’s or a former employee’s name, renewal, migration and access remain dependent on that person.
• Assuming hosting is the sole cause of slowness: Heavy themes, uncompressed images and unnecessary plugins slow a website even on a good server; measurements should be made before upgrading the package.

Why does Onur Freelance open hosting accounts in the business’s name?

For projects undertaken by Onur Freelance, both domain registration and the hosting account are placed directly in the business’s name. This choice keeps ownership of the technical infrastructure with the business from the outset: renewal invoices go to the business, the business decides if it wants to change providers, and accounts do not need to be transferred even if it works with another team later.

This article does not recommend a particular web hosting brand. The suitable package is assessed against the criteria above according to the website type, features such as forms or membership, and expected visitor volume. Corporate website prices start from 15,000 TL, and websites are delivered with SSL and mobile compatibility; the scope is on the corporate web design page.

Monthly maintenance for updates, backups and server monitoring is optional and costs 500–2,000 TL; details are on the website management page. Because the account remains with the business, taking or declining maintenance is entirely its decision.

How do you choose a hosting package? A step-by-step checklist

The question of how to choose a hosting package becomes a few clear comparisons when the sequence below is followed. Obtaining every answer from the provider in writing also makes clear what was promised if a problem occurs later:

1. Determine the website type: Promotional website, blog, membership structure or e-commerce; the need for isolated resources grows as dynamic functionality increases.
2. Verify software versions: Are PHP 8.3 or later and the MariaDB or MySQL version recommended by WordPress.org available?
3. Request resource limits: Are CPU, memory, entry process, IO and inode values in writing?
4. Ask about storage and the web server: Is storage NVMe, which web server is used, and is server-level caching available?
5. Clarify the backup policy: Frequency, retention period, off-server copy and dashboard restoration.
6. Check SSL and email: Does the certificate renew automatically, and are mailboxes included in the package?
7. Find out the data center location: Assess the distance to visitors and, if personal data is collected, the implications under KVKK.
8. Read renewal terms: Renewal price, contract duration and the route to a higher package.
9. Open the account in the business’s name: Billing, the dashboard and domain registration should use the business’s details.

Measuring TTFB against the old server after migration or a web hosting package change shows concretely whether the choice worked. The same comparison can also be monitored with real-user data in Search Console’s Core Web Vitals report.

A good web hosting package is the one combining the resources the website will actually use, current software, regular backups and accessible support rather than the one offering the most resources. Comparing criteria in writing also makes clear what a price difference represents.