Web hosting is the service that keeps your website's files, and where needed its database, on an internet-connected server. When someone visits your domain, that environment makes the site available to their browser. Choosing hosting, however, takes more than comparing storage allowances. Your software, simultaneous requests, backup arrangements and the support you actually receive all matter.
Whether you are launching a business website, running WordPress or moving an existing project, this guide gives you a practical way to evaluate a plan. The aim is to find enough capacity for today's workload, a sensible upgrade path and clear responsibilities—not simply to buy the largest package.
A quick starting point: A compatible web hosting plan can suit a small company website. For a project handling sales, reservations or intensive database work, investigate application compatibility, processing limits and recovery options before focusing on disk space.
What does web hosting actually do?
A website consists of assets such as images, style sheets and application code. Some sites deliver mostly prepared files. Others query a database to build pages containing articles, products or reservations. A hosting account provides the environment in which those components run.
The page a visitor sees and the work happening on the server are different parts of that process. A design that opens on your own computer is not automatically available to customers online. Similarly, buying a domain does not create a server for your application. The WordPress guide to preparing an installation distinguishes the hosting company from the server that runs the software.
You are therefore selecting a working environment, not just a place to keep files. Depending on your site, that environment may need a particular PHP version, database, certificate configuration, file access method or scheduled task facility. Treat those requirements as a set.
Domain, hosting, DNS and SSL: the differences
These terms describe separate functions. You do not necessarily need to buy them from the same company.
- Domain name: The address people use to find your business online.
- Hosting: The service providing an environment for your website's files and application.
- DNS: Records directing your domain to the services it uses, including potentially separate web and email servers.
- SSL/TLS: The certificate and encryption arrangement used to establish an HTTPS connection between browser and server.
You can keep a domain with one registrar and use hosting from another provider if the records are configured correctly. A, AAAA, CNAME, MX and TXT records have different roles; Cloudflare's DNS record reference explains them.
For a business, the practical risk is changing the website's destination while unintentionally interrupting email. When moving nameservers, check the complete set of records in the new DNS zone, including email verification records. Knowing who controls domain registration, DNS management and hosting renewals prevents confusion during a move.
Hosting types: compare the architecture, not just the name
Providers use package names differently. Two products labelled “cloud hosting” or “business hosting” may have different resources and management arrangements. This comparison describes infrastructure approaches; it does not imply that Vericod sells every option listed.
| Hosting approach | Often considered for | Ask before buying |
|---|---|---|
| Shared hosting | Company websites, blogs and compatible small applications | What are the per-account CPU, memory, process and file limits? |
| VPS / virtual server | Projects needing more configuration control or custom services | Who manages updates, security and backups? |
| Dedicated server | Workloads requiring broader control over physical hardware | What management, hardware response and capacity planning are included? |
| Cloud-based hosting | Projects needing flexible resources or several infrastructure components | How do scaling, billing and failure recovery actually work? |
The word “cloud” is not, by itself, a promise of uninterrupted service. A VPS is not automatically a managed server either. Establish who monitors resource use, applies updates and handles an incident. Those operational responsibilities can matter as much as the advertised capacity.
WordPress hosting is not a separate hardware architecture. It may combine resources, caching, management or support configured around WordPress. Read the actual service description rather than relying on the label.
The resources to examine before storage capacity
CPU and memory: Rendering pages, searching, generating reports and running background jobs require computing resources. Heavy plugins or database queries can consume substantial capacity even when visitor numbers are modest. Ask about account limits and what happens when they are reached.
Concurrent requests and application workers: A plan's ability to process several requests at once matters for dynamic websites. Many visitors submitting forms during a campaign create a different workload from people viewing cached images throughout the day. A monthly visitor figure alone cannot describe that difference.
Storage and file counts: Alongside a capacity allowance, an account may have an inode limit covering the number of files and directories. Large numbers of small cache files or email messages can reach that limit before storage is full. Check whether backups count towards the same allowance.
SSD and NVMe: Storage technology is one part of the system, not a complete performance result. CPU sharing, database behaviour, caching and application design also affect response times. Do not rank plans purely by a drive label.
Database and runtime compatibility: Confirm the database type, supported versions and relevant size limits. A custom application may also need specific PHP extensions, scheduled tasks, file permissions or outbound API connections. Verify these before paying, especially if the software was previously running elsewhere.
Estimating disk space and data transfer
Start with an inventory: website files, images, database, email and the backups you intend to retain. Then consider the material you expect to add over the coming months. Leave room to grow rather than choosing a package whose allowance exactly matches today's files.
Data transfer is different from stored data. As a deliberately simplified example, loading a page that transfers 2 MB a total of 10,000 times represents roughly 20 GB of transfer. Real usage depends on pages per visit, downloads, images, bots and caching. That calculation is a planning example, not a guarantee of visitor capacity.
If you see “unlimited traffic”, read the fair-use conditions, processing limits and permitted uses. Ask before putting a large video collection or download archive on a standard website account. Keeping bulky media in a suitable separate storage service may make the project easier to manage.
Website speed, server location and SEO
Audience location matters, but a server being in a particular country does not guarantee a fast website. Network routing, caching, page weight, external scripts and application queries all contribute. If you serve customers in Tirana or elsewhere in Albania, test with the devices and connections those customers actually use.
Test more than your home page. Product pages, articles, contact forms and reservation flows can behave very differently. A fresh, nearly empty installation is not a reliable substitute for testing the real site with its images, plugins and content.
Google's Core Web Vitals guidance gives good-experience thresholds of 2.5 seconds for LCP, 200 milliseconds for INP and 0.1 for CLS. Assessment uses the 75th percentile of visits, with mobile and desktop evaluated separately.
Hosting supplies the foundation; it does not automatically fix oversized images, unnecessary plugins or expensive JavaScript. Google's page experience guidance also makes clear that good scores do not guarantee top search rankings. Treat hosting as one contributor to a dependable website, rather than the whole of an SEO strategy.
SSL, security and DDoS protection
HTTPS requires a valid certificate and correct configuration. Ask whether installation and renewal are included and who manages them. The Let's Encrypt getting-started guide distinguishes provider-managed certificates from running a certificate client yourself.
A certificate does not repair vulnerable application code or restore lost information. Unique passwords, appropriate permissions, updated software and secure file access remain separate responsibilities. Check whether SFTP or another encrypted access method is available.
For DDoS protection, ask what traffic is covered, how the origin server is protected and how the provider responds during an attack. A web application firewall, malware scanning and DDoS mitigation perform different jobs. The presence of one does not establish that all are included.
You can review Vericod's relevant options on the DDoS-protected hosting page. Compare the described scope with the needs of your project instead of assuming protection is unlimited.
Backups: recovery matters as much as keeping a copy
Get clear answers to four questions: what is backed up, how often, for how long and where the copies are stored. If a dynamic site's files are copied but its database is excluded, the backup may not be enough to restore the working site.
A daily backup does not necessarily preserve orders received after the last successful copy. Decide how much recent information the business could afford to lose and how quickly the website needs to return. Ask about the scope and cost of the provider's restore service.
Files and database copies also need to be consistent with one another. Restoring old application files alongside a newer database can leave a site unable to run. During a recovery test, check logins and ordering workflows, not just whether the home page opens.
For important information, plan a separately protected copy and a recovery test. CISA's backup guidance emphasises protecting critical backups and testing recovery. A successful restore is more useful evidence than a dashboard that merely says a backup exists.
Choosing hosting for WordPress
Check WordPress's current environment recommendations alongside the compatibility of your theme and plugins. Being able to run on an older PHP release does not make that release the best choice. Consult the official WordPress requirements when planning a new installation or upgrade.
Caching and staging environments can be useful, but they are not automatically included with every package. Pay particular attention to personalised pages such as shopping carts, account screens and reservation forms. Applying the same cache rule everywhere can produce incorrect content or behaviour.
Clarify whether support covers only the server or also includes help with the application. Theme development, plugin licences and repairing poorly written extensions may be separate work. When comparing WordPress hosting plans, assess the service boundaries as carefully as the resource allowances.
Matching a starting plan to your business
A company information site or personal blog: A compatible web hosting account can be a reasonable starting point for a site publishing pages and images without complex processing. Prioritise backups, HTTPS, a usable control panel and an upgrade path.
A business using WordPress: Resources must suit your theme and plugins, while the runtime and update process need to remain manageable. Do not make the decision entirely on a “WordPress compatible” badge.
A reservation or sales website: Simultaneous requests, data integrity, recovery arrangements and application support become more important. Our guide to choosing car rental software offers a further checklist for reservation-based businesses.
A custom application or a fast-growing project: Background workers, custom services and integrations may not fit a standard shared account. Share the technical requirements and establish the appropriate environment. If the requirements are unclear, talk to our team before choosing a package.
Comparing total cost, renewals and support
Separate an introductory offer from the renewal price. Monthly and annual billing, any commitment, upgrades and optional services can all change the total cost. Applicable taxes and charges should be clear in the breakdown before payment.
Do not assume the price includes domain registration, business email, application licensing, migration or restoring a backup. Check whether a free feature lasts only for the first term. Read the cancellation and refund conditions before purchase rather than relying on a headline discount.
Ask what “24/7 support” means in practice: the ability to submit a ticket, continuous access to a person or intervention for certain incidents? A first response is not the same as a resolution. Know which channel to use for downtime, email trouble and application faults, and which work falls outside the hosting agreement.
Uptime and service commitments: If availability is expressed as a percentage, check how it is measured, whether scheduled maintenance is excluded and what remedy applies. For illustration, 99.9% calculated across an entire 30-day month corresponds to 43 minutes and 12 seconds of time. That is a mathematical example to explain the percentage, not a Vericod service commitment. The measurement period and exclusions in the actual agreement are what matter.
A sensible migration sequence for an existing website
- Inventory files, databases and email services, and create a verified backup before making changes.
- Check runtime and extension compatibility on the new environment; test the site before directing visitors to it.
- Try forms, logins, reservations, payment return flows and email, keeping test activity separate from real transactions.
- Compare DNS records and plan the web, email and verification records together.
- Decide how new orders will be handled during the transition so information does not become split across two databases.
- After switching, check HTTPS, important URLs and real user workflows. Keep the old service available until the checks are complete.
DNS caches can mean a change becomes visible at different times for different visitors. Plan around the existing records and their TTL settings rather than relying on a universal promise that every move finishes in a fixed number of hours.
Frequently asked questions
Can I buy hosting if my domain is with another company?
Yes. You can update the relevant DNS records or nameservers while keeping the domain with its existing registrar. Preserve email-related records if the domain is used for mail. A registrar transfer is not inherently required to change web hosting.
Does buying hosting mean someone will build my website?
Hosting supplies the environment in which a website runs. Design, writing, software licensing and installation may be offered separately. Check the package description so you understand the difference between creating a site and hosting it.
Is the most expensive hosting always the fastest?
No. The relevant resources and configuration matter. Paying for capacity your application cannot use, or services you do not need, may leave the original performance problem unchanged. Test the actual workload and investigate its bottleneck.
Does a CDN remove the need for hosting?
A CDN can deliver suitable copies of content from distributed locations. It does not automatically replace the origin running an existing application's files and database. Cloudflare's CDN explanation describes that delivery layer. Platforms that also host the application should be assessed according to their separate service scope.
Should I pay monthly or annually?
Annual billing may reduce the effective price, while monthly billing offers a shorter initial evaluation period. Consider how certain your requirements are, the renewal cost and cancellation terms. A discount alone should not decide the infrastructure for a business-critical site.
What is the first question to ask a hosting provider?
Start with: “Can this environment run this application, with this workload and this tolerance for data loss?” Then compare the resource limits, backup arrangements and division of support responsibilities in writing.
Explore hosting options with Vericod
Review web hosting, WordPress hosting and DDoS-protected hosting as distinct options. Use the current package descriptions as the reference for capacity, prices and included services.
Before deciding, note your software, approximate disk use, email requirements and any reservation or sales processes. Share those details with Vericod to discuss a suitable starting plan and an upgrade path. The right package is the one that runs your application under clear, manageable conditions—not simply the one with the longest feature list.
