Customer Complains About Slow Performance Due to Wrong Plan Selection or Insufficient Resources

 

 

 

Customer Complains About Slow Performance Due to Wrong Plan Selection or Insufficient Resources

This article explains how iCoreHosting handles performance complaints when a customer selected an unsuitable plan, or when the current plan is no longer sufficient for the customer current usage. We aim to make the experience smoother while keeping responsibilities clear.

Service Direction / Introduction / Scope

Service Direction

Even when a customer orders the wrong plan, or the current plan becomes insufficient due to growth, iCoreHosting aims to handle the complaint professionally and guide the customer to a smoother experience. We do not ignore the problem. We diagnose, explain, and provide the best next step to restore performance.

Introduction

Slow performance is often caused by insufficient resources for the actual workload. Some customers choose a plan based only on price or disk space, and later discover that CPU, RAM, disk I O, or database load exceeds the plan capacity. In other cases, the customer plan was suitable before, but usage grows over time and the same plan is no longer enough. When this happens, the customer may complain that the service is slow. This article defines how we respond and how to resolve it efficiently.

Scope

  • Applies to Shared Hosting, VPS, and Dedicated Server services.
  • Applies when the customer reports slowness and the root cause is plan mismatch or insufficient resources for current usage.
  • Applies to common systems such as company websites, shopping carts, CRM, accounting, and POS.

Service Transparency

iCoreHosting provides resources based on the ordered plan specification. Performance is influenced by the customer application design, workload, traffic pattern, and optimization level.

  • When the plan is too small for the workload, slow response can happen even if the server is working correctly.
  • When customer usage grows, a plan that was sufficient before may become insufficient later.
  • Our responsibility is to investigate, confirm the cause, and recommend the correct solution.
  • Our goal is to make the customer experience smoother by providing clear guidance and a fast path to improvement.

Definitions

  • Wrong Plan A plan that cannot support the customer real workload, causing frequent resource saturation or performance degradation.
  • Insufficient Resources A situation where the current plan was previously adequate, but due to growth in traffic, data, users, or background processing, the plan is no longer sufficient.
  • Resource Saturation CPU, RAM, disk I O, database connections, or inode usage reaching near limit, affecting response time.
  • Performance Complaint Customer reports slow website, timeout, failed tasks, delayed email, or unstable access.
  • Smooth Resolution A process where iCoreHosting helps the customer quickly understand the cause and choose the most effective fix.

Description of Content / Step-by-Step Guide

Step 1. Acknowledge the complaint and confirm scope

  • Confirm which domain or service is affected.
  • Confirm the time range of the slow issue.
  • Ask what changed recently such as new plugin, new campaign, data import, or new users.

Step 2. Check resource usage indicators

  • CPU usage peak and average trend.
  • RAM usage, swap activity, and out of memory events.
  • Disk space and disk I O wait.
  • Database load, slow queries, and connection spikes.
  • For shared hosting, check if account hits resource policy limits frequently.

Step 3. Determine the root cause category

  • Wrong plan selection Workload exceeds allocated CPU or RAM consistently from the beginning.
  • Plan no longer sufficient The plan was acceptable before, but growth in traffic, data, users, or tasks makes it insufficient now.
  • Application issue Heavy plugin, inefficient code, unoptimized database, malware, or attack traffic.
  • External dependency Slow third party API, payment gateway, DNS, or remote image hosting.

Step 4. Provide the fastest improvement path

  • If wrong plan selection or insufficient resources is confirmed, recommend an upgrade that matches the observed usage pattern.
  • If application issue is suspected, recommend specific actions such as caching, database cleanup, image optimization, or security hardening.
  • If external dependency is the cause, provide evidence and suggest alternative implementations.

Step 5. Make it smooth for the customer

  • Explain in simple terms why the current plan is not enough.
  • Provide an upgrade recommendation with clear benefit and expected outcome.
  • Offer a short term workaround when possible, such as temporary tuning or cleanup guidance.
  • Confirm next steps and what improvement the customer should expect after change.

Common Mistakes

  1. Customer chooses a plan based only on price or disk size and ignores CPU and RAM needs.
  2. Assuming a shopping cart, CRM, accounting, or POS can run smoothly on shared hosting.
  3. Launching without caching and database optimization.
  4. Adding many plugins or extensions without performance testing.
  5. No monitoring, no alerting, and only reacting after users complain.

Responsibility Breakdown

Customer Responsibility

  • Provide accurate system information and expected workload before ordering.
  • Choose a plan that matches the system type and reliability requirement.
  • Upgrade the plan when the system outgrows the current resources.
  • Maintain and optimize the application layer such as code, database, and plugins.

iCoreHosting Responsibility

  • Investigate the complaint and verify whether the server is delivering the ordered resources.
  • Provide clear evidence and explanation of the root cause in a customer friendly way.
  • Recommend the correct upgrade direction to restore smooth performance.
  • When possible, suggest quick improvements and best practices to reduce repeat incidents.

Important Note

When the root cause is wrong plan selection or the current plan is no longer sufficient, iCoreHosting can guide and recommend the best option, but the plan upgrade decision and upgrade cost belong to the customer.

Limitations

  • Shared Hosting is a shared environment and cannot guarantee constant performance under every condition.
  • Application design issues cannot be fully solved by upgrading resources only.
  • Third party integrations and external services may affect performance beyond hosting control.

FAQ

Q1. If I ordered the wrong plan or my plan is no longer enough, will iCoreHosting fix it for free
A1. We will investigate and explain the cause clearly. If the issue is plan mismatch or insufficient resources for your current usage, upgrading is the correct solution and the upgrade cost is borne by the customer. We will guide you to the most suitable upgrade option.

Q2. Why was it okay before, but now it becomes slow
A2. Workload often grows over time, such as more visitors, more data, more plugins, more users, or heavier background jobs. A plan that was enough earlier may become insufficient later.

Q3. Can you make it smooth without upgrading
A3. Sometimes basic optimization helps, such as enabling caching, cleaning database, reducing heavy plugins, and optimizing images. However, if CPU or RAM is consistently maxed, upgrading is the most reliable fix.

Q4. How do I avoid ordering the wrong plan again
A4. Share your system type, expected users, and peak usage pattern with us before ordering. We can recommend a suitable service type and starting plan.

Use Case

Scenario

A customer starts with a plan that is acceptable for early stage usage. Over time, more products, more visitors, and more background tasks are added. The website becomes slow and the customer complains.

iCoreHosting Action

  • Check usage trends and confirm resource saturation during peak periods.
  • Explain that current usage has outgrown the plan capacity, even though the plan previously worked.
  • Recommend an upgrade path to match the new workload level.
  • Provide optimization suggestions such as caching and database tuning to improve further after upgrade.

Expected Result

After upgrading to a suitable plan and applying recommended optimizations, the system response becomes stable and customer experience improves significantly.

Summary

  • When customers complain about slow performance, iCoreHosting will investigate and provide clear root cause explanation.
  • If the cause is wrong plan selection or the current plan is no longer sufficient for usage growth, we will guide the customer with the fastest path to restore smooth performance, usually by upgrading to the right plan.
  • iCoreHosting responsibility is to provide ordered resources and professional recommendations.
  • Customer responsibility is to choose and upgrade the plan to match the actual workload needs.
  • 0 Uživatelům pomohlo
Byla tato odpověď nápomocná?

Související články

Importance of Adding Google reCAPTCHA to Website Forms

Overview: To enhance the security of your website and prevent spam submissions, it is highly...

Standard Requirement – Google reCAPTCHA for Website Cybersecurity Compliance

To meet basic website cybersecurity standards and protect against automated abuse, all websites...

SME Web Hosting Plan Introduction

SME Web Hosting Plan Introduction The iCoreHosting SME Web Hosting Plan is an all-in-one package...

Understanding Traffic Spikes & Why AWS Auto Scaling Is Recommended

Understanding Traffic Spikes & Why AWS Auto Scaling Is Recommended 1. Table of Contents...

How AWS Auto Scaling Handles PHP, MySQL, Uploads, Images, Cache, and Sessions

How AWS Auto Scaling Handles PHP, MySQL, Uploads, Images, Cache, and Sessions 1. Table of...