Explanation of Resource Usage – Hosting
ℹ️ Note: This article applies to our Web and Reseller Hosting packages.
Maximum Capacity Reached
Solving Capacity Issues
Viewing Resource Usage
Solving Common Capacity Problems
Need Assistance?
Each hosting package includes a guaranteed amount of server capacity, such as CPU and memory resources.
When the limit is reached, your website may slow down or become temporarily unavailable. Possible causes:
Plugin or script: A faulty or memory-intensive plugin may enter a loop.
Cronjob: Incorrectly configured cronjobs can consume all server resources.
Poorly built website: Inefficient coding or too many plugins can overload your hosting resources.
High visitor numbers: A sudden spike in traffic can fully consume your server capacity.
Ask yourself:
Has anything recently changed on your website?
When did the issues start?
Is there a lot of traffic from a single IP address?
Are there many error messages in the Error Log?
Do you have a backup from before the issues started?
Follow these steps:
Log in at https://voorbeeld.cc:2222 (or use SSO).
Click on Extra Features > Resource Usage.
Click Details to view the exceeded limits.
You will see graphs and a 30-day history overview.
Check error logs
Fix any errors listed in your Error Log.
Use an up-to-date PHP version
Always use the latest stable PHP version for better performance.
Analyze and optimize:
Plugin or script
Disable all plugins, then re-enable them one by one.
Cronjob
Temporarily disable cronjobs and check if the issue resolves.
Consider disabling WP_CRON for WordPress.
Poorly built website
➔ Minimize the number of plugins.
➔ Implement caching (Redis, LiteSpeed Cache, Opcache).
➔ Regularly optimize the database.
High visitor numbers
Block suspicious IP addresses via .htaccess:
Problem-solving is included with our WordPress Hosting packages.
For other packages, you can use our additional ‘Problem Solving’ service.
🔄 Remember to replace voorbeeld.cc with your own website address.
Maximum Capacity Reached
Solving Capacity Issues
Viewing Resource Usage
Solving Common Capacity Problems
Need Assistance?
Each hosting package includes a guaranteed amount of server capacity, such as CPU and memory resources.
🚦 Maximum Capacity Reached
When the limit is reached, your website may slow down or become temporarily unavailable. Possible causes:
Plugin or script: A faulty or memory-intensive plugin may enter a loop.
Cronjob: Incorrectly configured cronjobs can consume all server resources.
Poorly built website: Inefficient coding or too many plugins can overload your hosting resources.
High visitor numbers: A sudden spike in traffic can fully consume your server capacity.
🛠️ Solving Capacity Issues
Ask yourself:
Has anything recently changed on your website?
When did the issues start?
Is there a lot of traffic from a single IP address?
Are there many error messages in the Error Log?
Do you have a backup from before the issues started?
🔎 Viewing Resource Usage
Follow these steps:
Log in at https://voorbeeld.cc:2222 (or use SSO).
Click on Extra Features > Resource Usage.
Click Details to view the exceeded limits.
You will see graphs and a 30-day history overview.
🧹 Solving Common Capacity Problems
Check error logs
Fix any errors listed in your Error Log.
Use an up-to-date PHP version
Always use the latest stable PHP version for better performance.
Analyze and optimize:
Plugin or script
Disable all plugins, then re-enable them one by one.
Cronjob
Temporarily disable cronjobs and check if the issue resolves.
Consider disabling WP_CRON for WordPress.
Poorly built website
➔ Minimize the number of plugins.
➔ Implement caching (Redis, LiteSpeed Cache, Opcache).
➔ Regularly optimize the database.
High visitor numbers
Block suspicious IP addresses via .htaccess:
order allow,deny
deny from 123.456.789.000
allow from all🤝 Need Assistance?
Problem-solving is included with our WordPress Hosting packages.
For other packages, you can use our additional ‘Problem Solving’ service.
🔄 Remember to replace voorbeeld.cc with your own website address.
Updated on: 23/05/2025
Thank you!