Shared hosting: the neighbor's site is sometimes closer than your contractor

Shared hosting is normal for a landing and a small company site. The problem is not that it is "bad". The problem is treating it as a fireproof cabinet. There is one panel per account. Other projects, or your old ones, may sit beside it. The panel password matches the mail password. In that setup a tidy new site does not save you if the panel sign-in is shared.

What is worth doing on any plan

• A separate panel password and a second factor, if the host offers one.
• Do not keep other people's sites and old sites in the same account as the live store.
• A backup that does not live only on this same server. Otherwise the neighbor's trouble takes it too.
• Clarity on whether the host updates your CMS or only its platform. Often only the platform.

Moving to a separate server is not the first step for a business card site. The first step is access, extra sites in the account and a backup. A store with an account area should separately discuss where the orders sit and who else is a panel admin. A WAF on shared hosting is often limited by the plan itself: that is not a reason to buy one blindly.

In an audit Lexora separates "the host answered for the platform" from "your account is open". The basic audit is free for new clients. If the panel is already someone else's, that is incident response: access changes, a file review, a backup that can still be saved. We put a pentest of the storefront code second, not first, while the host panel is open.