How much RAM, CPU and storage does your website need?

Sift website hosting resources

Check the application before the allocation

A static site serves prepared files. A dynamic application may run server-side code, query a database or create a response for each visitor. Write down the framework or CMS, its version, build command and any services it depends on before comparing plans.

Ask Sift to confirm compatibility with that exact setup. A resource table is not proof that a particular database, runtime, control panel or managed application service is included. Keep domains, email, certificates and backup arrangements on your checklist and confirm each separately before paying.

Read RAM and vCPU as separate limits

RAM is working memory for the processes your application needs. CPU handles computation. A site can run short of either resource, so buying more memory is not a substitute for investigating a slow request or an expensive task.

If the website already runs elsewhere, collect representative memory use, CPU activity, request timings and error reports. Include busy periods, scheduled tasks and the number of applications sharing the plan. Without those measurements, a fixed promise of how many visitors an allocation supports would be guesswork.

Budget storage for more than the homepage

Count the files your deployment actually keeps: application code, generated assets, uploaded images and documents, logs, and any database files or backup copies stored in the allocation. Leave room for normal growth and clarify which items count towards your storage limit.

NVMe describes the storage technology; it does not tell you how much space is available or promise a particular page-load time. Large downloads and video also raise transfer questions that a storage figure alone cannot answer. Confirm transfer conditions rather than assuming they are included without limits.

Website count does not multiply the resources

Sift’s Launch, Grow and Scale tiers allow one, five and ten websites respectively. Compare the RAM, vCPU and storage listed beside those limits. A higher website allowance does not mean every website receives a separate copy of the plan’s resources.

Describe the whole group of sites in your request. A collection of quiet portfolios and several active applications are different workloads. If the combined requirements do not fit a listed tier, use a custom quote and ask how the resources and limits will apply.

Separate hosting load from browser performance

A large image or heavy browser script can make a website feel slow even when the server has spare resources. Check representative pages on mobile as well as desktop, and separate server response problems from loading, interaction and layout issues in the browser.

Use lab tests to investigate a specific page and real-user measurements to understand the experience visitors actually have. A single successful test is not a guarantee for every device, connection or traffic level, and a hosting upgrade should address a measured constraint.

Send a request that can be checked

Choose a web-hosting plan and your billing currency, then include the application, website count, current storage use, expected growth and preferred region in the request. Add useful measurements if you are moving an existing project. Keep passwords, API keys and private customer data out of the notes.

Sift confirms the software, resources, availability and payment details on Discord. The displayed selected-currency monthly amount is the plan’s billing price; a custom plan needs its own quote. Confirm the final scope before agreeing the order.

Documentation and further reading

• MDN: static sites and dynamic applications
• MDN: hosting, domains and bandwidth are separate considerations
• Google web.dev: measuring loading, interaction and layout stability

For your Sift order, confirm the software, resources and region with us before paying.

Continue planning your project

• Paper, Fabric or Forge: which Minecraft server should you run?
• How much RAM does your Minecraft server need?
• Prepare your Node.js or Python bot for hosting.
• Choose a server location around your players.