What reserved resources on hosting actually mean

What reserved resources on hosting actually mean - What reserved resources on hosting actually mean

On hosting your site lives on a server together with other sites. The right question is not whether you share the server, but what happens when a neighbour has a busy day. Three pieces make the difference.

CloudLinux: each account with its own resources

Without CloudLinux, a single account going wild can slow down the whole server. CloudLinux puts each account in its own isolated environment and gives it a slice of RAM and CPU of its own.

That means two things. First, a busy neighbour cannot take your resources. Second, just as important: you cannot exceed your own slice either, and if you hit it often, your site slows down. That is why our plans state RAM and CPU explicitly rather than promising unlimited resources.

LiteSpeed and LSCache: how pages reach the visitor

LiteSpeed Enterprise is the web server that delivers the pages. Together with LSCache, enabled on every account, already generated pages are served from cache instead of going through PHP and the database on every visit.

For WordPress, the LiteSpeed Cache plugin handles cache invalidation itself when you publish or edit something, so there is nothing to purge by hand.

Imunify360: the security part

Imunify360 runs with antivirus on every hosting account. It scans files, blocks known attacks and quarantines what it finds infected.

It does not replace basic hygiene: updated themes and plugins, different passwords, few administrator accounts. A WordPress site two years out of date stays a target, however good the scanning is.

What stays your responsibility

Daily backups run automatically on hosting, but a copy outside the server is still worth having: if you delete something and notice a week later, you want an older version.

Application updates are yours too. We keep the server, the system, LiteSpeed and the platform's security; you keep the site updated.