Before you start
List themes, plugins, file and database sizes, mail accounts and the access you already have. Never include passwords in a sales enquiry. Check requirements for the specific versions you intend to run.
Describe what the site actually does
A portfolio mostly serves pages and images. A shop also writes orders, stock changes and customer records. Note busy periods and scheduled work such as product imports, messages and thumbnail generation. Visitor totals alone cannot size an environment. A cached article and a logged-in checkout do not place the same load on PHP and SQL. Include administration work in your assessment rather than measuring only the public homepage.
Check dependencies before moving
WordPress currently recommends PHP 8.3 or later, MariaDB 10.11 or MySQL 8.0 or later, and HTTPS. Individual plugins may have additional requirements. Check PHP extensions, upload limits and theme compatibility on a test copy before changing production. These technical recommendations do not establish which runtime versions are included in a CubixServ commercial proposal. Confirm the actual environment and the application together rather than assuming a newer version fixes every issue.
Budget for files, SQL and email
Add media, application files, database storage and the copies needed for recovery. Say whether email is hosted with the site or by another provider. A small database can still be expensive to query. Measure slow requests before assuming more disk or RAM will solve the problem. Leave room for updates and growing media libraries. Keep mail quotas distinct from website space when comparing the limits of different proposals.
Agree who maintains each component
Ask who updates WordPress, themes and plugins, who checks backups and who performs restores. Files and SQL need to represent a consistent recovery point. Keep an independent copy according to your requirements and practise restoration before you need it. HTTPS protects connections; it does not replace patches, access controls or application filtering. A network DDoS service also does not establish that every malicious HTTP request will be blocked.
Choose an environment you can operate
Web hosting can spare a beginner full system administration. A Linux VPS makes sense when you can maintain the server and need root access, custom services or specific dependencies. It adds responsibility for security, updates and recovery. Do not default to a VM for a simple website. A dedicated server answers different physical resource and administration requirements. Choose the smallest maintainable arrangement that satisfies the project, rather than buying complexity for its own sake.
Compare the complete proposal
Compare the actual billed total, term, renewal price, resources and limits. Confirm email, migration assistance, backup retention and the support boundary. Use CubixServ’s Web Hosting page to prepare an enquiry: scope and price are agreed in a proposal. A prepared enquiry does not order or reserve resources and does not guarantee a delivery date. Keep a record of the agreed responsibilities so the person maintaining the site can follow them.
For your situation
| Situation | Next check |
|---|---|
| A first site or association | Describe the CMS, media and email requirements. Agree who will maintain the application. |
| An active shop | Prepare a test copy and arrange a window to freeze new orders before migration. |
| A custom application | List dependencies and your Linux administration capability before comparing a VPS. |
Official sources
These documents describe the relevant protocols and software. Your service terms and configuration still need to be checked.