Web hosting is space on a server plus the software to serve a website from it. On Ahosting that means a cPanel account on a LiteSpeed server, with a free dedicated IP, free SSL and free migration included, from $2.79/month.
This is an orientation: what you get, what the limits actually are, and what to do first.
What the account gives you
cPanel to manage everything: files, databases, email, SSL, backups. Your one control panel.
LiteSpeed with LSCache. The web server holds cached pages, so a cached request never starts PHP at all. This is the single largest performance advantage on the plan and it needs enabling to be useful.
Free SSL issued automatically once the domain points here.
A free dedicated IP, which most shared plans charge for.
Free migration from another host, done for you by support.
The limits worth knowing
Disk is the visible one and rarely the binding one. The constraint that actually limits a busy site is how many PHP requests may execute simultaneously.
Beyond that number, requests queue rather than fail. The symptom is a site that is fast at night and slow in the afternoon, pages that hang and then load, rather than errors.
Caching is the fix and it is dramatic, because every cached page is a request that never occupies a process. Monitoring your hosting resources explains reading the numbers and recognising which limit you are hitting.
What shared hosting will not do
You cannot install system software, change server-wide settings, or run anything requiring root. Those affect every account on the server.
If you need them, that is a VPS: along with responsibility for maintaining the operating system, which is real ongoing work instead of a one-time cost. Comparing the tiers goes over that trade honestly.
The one rule about files
Your website lives in public_html. Files there are served to the internet; files above it are not.
That explains both directions of the usual confusion: a file uploaded one level too high never appears on the site, and a database export left inside public_html can be downloaded by anyone who guesses the name.
First five things
- Log into cPanel and change the password.
- Set the contact address to a mailbox not on this account: quota warnings go there.
- Get the site on the server: uploading your website files.
- Point the domain here, then run AutoSSL. Certificates cannot be issued before the domain resolves here.
- Set up backups that store a copy off the server, and test a restore once.
Getting started with your account walks through that sequence in full, including why testing before the DNS change costs nothing.
Where to go next
For the control panel itself, the cPanel introduction deals with the sections that matter. For a WordPress site, the one-click installer is two minutes. And when something breaks, the error log usually holds the answer, understanding cPanel error logs.
What decides whether a plan is enough
Not disk space, usually. The limit most sites reach first is how many PHP requests the account may run at the same time.
Requests beyond that queue rather than fail, so the symptom is a site that hangs and then loads during busy periods, which reads as slow code rather than a ceiling. The tell is timing: a queue is slow when there is traffic and fine at night, while genuinely slow code is slow consistently.
Caching changes that number dramatically, because a cached page never occupies a process at all. There is more on the sequence in How to Speed Up a Website in the Right Order.
Domains, hosting and email are three separate things
They arrive together and they are not the same purchase, which is the source of a lot of confusion later.
The domain is a registration you renew, and it can point at any host. The hosting is the space and processing that serves your site. Email can come from your hosting account or from somewhere else entirely, and it follows MX records in place of the website.
The practical consequence: moving hosts does not move your domain, and pointing a domain at a new host moves your mail too unless you plan for it.
What arrives in the first email
Your control panel address and login, the server name, and often temporary details for reaching the site before DNS points at it.
Keep that message. It contains the nameservers you will need when the domain is registered elsewhere, and it is the fastest reference when something needs checking a year from now.
Two settings worth changing on day one
The contact address. Quota warnings, security alerts and expiry notices go there. Point it at an address that is not on a domain hosted in this account, otherwise a full or suspended account stops the very warning that would have told you.
Two-factor authentication, on both the billing login and cPanel. They are separate logins and both are worth protecting. There is more in How to Secure Your Hosting Account.
Backups: what is provided and what is yours
Most hosting includes some backup arrangement, and the details matter more than the fact.
Find out how far back they go, how often they run, and whether a restore is self-service. A daily backup kept for a week does not help with a problem discovered after a fortnight, and compromises are usually discovered late.
Then keep at least one copy of your own, somewhere that is not this server. That is the copy that survives a mistake at the hosting level as well as at yours.