33 questions in this topic
Expand a question to see the answer. The content is visible in HTML and can be indexed by search engines.
323. How to check CPU usage?
For the topic "how to check CPU usage", first check the setting in the LVE, cache and real page response time charts.
You can check CPU, RAM, Entry Processes and CloudLinux LVE limits in the hosting panel if the package provides resource graphs. Exceeding the limits may cause slowdowns or 503 errors.
The most important thing is to determine what is causing the spike: users, bots, cron, imports, CMS plugin, database or external integration.
324. How to check RAM usage?
For the topic "how to check RAM usage", first check the setting in the LVE, cache and real page response time charts.
You can check CPU, RAM, Entry Processes and CloudLinux LVE limits in the hosting panel if the package provides resource graphs. Exceeding the limits may cause slowdowns or 503 errors.
The most important thing is to determine what is causing the spike: users, bots, cron, imports, CMS plugin, database or external integration.
325. How to check Entry Processes/EP?
For the topic "how to check Entry Processes/EP", first check the setting in the LVE, cache and real page response time charts.
You can check CPU, RAM, Entry Processes and CloudLinux LVE limits in the hosting panel if the package provides resource graphs. Exceeding the limits may cause slowdowns or 503 errors.
The most important thing is to determine what is causing the spike: users, bots, cron, imports, CMS plugin, database or external integration.
326. How to interpret CloudLinux LVE charts?
For the topic "how to interpret CloudLinux LVE charts", first check the setting in the LVE, cache and real page response time charts.
You can check CPU, RAM, Entry Processes and CloudLinux LVE limits in the hosting panel if the package provides resource graphs. Exceeding the limits may cause slowdowns or 503 errors.
The most important thing is to determine what is causing the spike: users, bots, cron, imports, CMS plugin, database or external integration.
327. What does exceeding the resource limit mean?
For the topic "what does exceeding the resource limit mean", first check the setting in the LVE, cache and real page response time charts.
You can check CPU, RAM, Entry Processes and CloudLinux LVE limits in the hosting panel if the package provides resource graphs. Exceeding the limits may cause slowdowns or 503 errors.
The most important thing is to determine what is causing the spike: users, bots, cron, imports, CMS plugin, database or external integration.
328. What to do when your account reaches its limits?
For the topic "what to do when your account reaches limits", first check the setting in the LVE, cache and real page response time charts.
You can check CPU, RAM, Entry Processes and CloudLinux LVE limits in the hosting panel if the package provides resource graphs. Exceeding the limits may cause slowdowns or 503 errors.
The most important thing is to determine what is causing the spike: users, bots, cron, imports, CMS plugin, database or external integration.
329. How to diagnose high CPU/RAM?
For the topic "how to diagnose high CPU/RAM", first check the setting in the LVE, cache and real page response time charts.
You can check CPU, RAM, Entry Processes and CloudLinux LVE limits in the hosting panel if the package provides resource graphs. Exceeding the limits may cause slowdowns or 503 errors.
The most important thing is to determine what is causing the spike: users, bots, cron, imports, CMS plugin, database or external integration.
330. How to diagnose bot overload?
For the topic "how to diagnose bot overload", first check the settings in the LVE, cache and real page response time charts.
Bots can consume resources just like real users. They can be restricted by robots.txt, application rules,.htaccess, rate limiting and geo-blocking via MaxMind databases, if available.
Country and bot blocks must be used carefully so as not to cut off legitimate customers, payment systems or integrations.
331. How to block resource-consuming bots?
For the topic "how to block resource-consuming bots", first check the setting in the LVE, cache and real page response time charts.
Bots can consume resources just like real users. They can be restricted by robots.txt, application rules,.htaccess, rate limiting and geo-blocking via MaxMind databases, if available.
Country and bot blocks must be used carefully so as not to cut off legitimate customers, payment systems or integrations.
332. How to block AI bots?
For the topic "how to block AI bots", first check the setting in the LVE, cache and real page response time charts.
Bots can consume resources just like real users. They can be restricted by robots.txt, application rules,.htaccess, rate limiting and geo-blocking via MaxMind databases, if available.
Country and bot blocks must be used carefully so as not to cut off legitimate customers, payment systems or integrations.
333. How to use robots.txt to limit crawlers?
For the topic "how to use robots.txt to limit crawlers", first check the setting in the LVE, cache and real page response time graphs.
Bots can consume resources just like real users. They can be restricted by robots.txt, application rules,.htaccess, rate limiting and geo-blocking via MaxMind databases, if available.
Country and bot blocks must be used carefully so as not to cut off legitimate customers, payment systems or integrations.
334. How to use rate limiting if available?
For the topic "how to use rate limiting if available", first check the setting in the LVE, cache and real page response time charts.
Bots can consume resources just like real users. They can be restricted by robots.txt, application rules,.htaccess, rate limiting and geo-blocking via MaxMind databases, if available.
Country and bot blocks must be used carefully so as not to cut off legitimate customers, payment systems or integrations.
335. How does MaxMind database country blocking work?
For the topic "how does country blocking work based on MaxMind databases", first check the settings in the LVE, cache and real page response time charts.
Bots can consume resources just like real users. They can be restricted by robots.txt, application rules,.htaccess, rate limiting and geo-blocking via MaxMind databases, if available.
Country and bot blocks must be used carefully so as not to cut off legitimate customers, payment systems or integrations.
336. Can the client block countries himself?
For the topic "can the client block countries itself", first check the setting in the LVE, cache and real page response time charts.
Bots can consume resources just like real users. They can be restricted by robots.txt, application rules,.htaccess, rate limiting and geo-blocking via MaxMind databases, if available.
Country and bot blocks must be used carefully so as not to cut off legitimate customers, payment systems or integrations.
337. When does support do a country block?
For the topic "when a country block is done by support", first check the setting in the LVE, cache and real page response time charts.
Bots can consume resources just like real users. They can be restricted by robots.txt, application rules,.htaccess, rate limiting and geo-blocking via MaxMind databases, if available.
Country and bot blocks must be used carefully so as not to cut off legitimate customers, payment systems or integrations.
338. How does Redis work?
For the topic "how Redis works", first check the setting in the LVE, cache and real page response time charts.
Redis and Memcached speed up applications via in-memory caching, PHP-FPM and OPcache speed up PHP, and QUIC/HTTP/3 can improve load times on the protocol side. Effectiveness depends on application and configuration.
339. How does Memcached work?
For the topic "how Memcached works", first check the setting in the LVE, cache and real page response time charts.
Redis and Memcached speed up applications via in-memory caching, PHP-FPM and OPcache speed up PHP, and QUIC/HTTP/3 can improve load times on the protocol side. Effectiveness depends on application and configuration.
340. How to enable Redis/Memcached?
For the topic "how to enable Redis/Memcached", first check the setting in the LVE, cache and real page response time charts.
Redis and Memcached speed up applications via in-memory caching, PHP-FPM and OPcache speed up PHP, and QUIC/HTTP/3 can improve load times on the protocol side. Effectiveness depends on application and configuration.
341. How does LiteSpeed Cache/LSCache work, if available?
For the topic "how does LiteSpeed Cache/LSCache work if available" first check the setting in the LVE, cache and real page response time charts.
Redis and Memcached speed up applications via in-memory caching, PHP-FPM and OPcache speed up PHP, and QUIC/HTTP/3 can improve load times on the protocol side. Effectiveness depends on application and configuration.
342. How does QUIC/HTTP/3 work?
For the topic "how QUIC/HTTP/3 works", first check the setting in the LVE, cache and real page response time charts.
Redis and Memcached speed up applications via in-memory caching, PHP-FPM and OPcache speed up PHP, and QUIC/HTTP/3 can improve load times on the protocol side. Effectiveness depends on application and configuration.
343. How to diagnose TTFB?
For the topic "how to diagnose TTFB", first check the setting in the LVE, cache and real page response time charts.
TTFB, PageSpeed and cache analysis help distinguish a slow hosting from a slow application. Check HTML response time, image size, browser cache, number of scripts, database queries and LVE load.
In the case of WordPress/WooCommerce and PrestaShop, it is worth configuring the application cache, optimizing images, limiting heavy plugins and checking for bots and crons.
344. How to use PageSpeedQuality.aspx?
For the topic "how to use PageSpeedQuality.aspx" first check the setting in the LVE, cache and real page response time charts.
TTFB, PageSpeed and cache analysis help distinguish a slow hosting from a slow application. Check HTML response time, image size, browser cache, number of scripts, database queries and LVE load.
In the case of WordPress/WooCommerce and PrestaShop, it is worth configuring the application cache, optimizing images, limiting heavy plugins and checking for bots and crons.
345. How to distinguish free hosting from free application?
For the topic "how to distinguish free hosting from free application", first check the setting in the LVE, cache and real page response time charts.
TTFB, PageSpeed and cache analysis help distinguish a slow hosting from a slow application. Check HTML response time, image size, browser cache, number of scripts, database queries and LVE load.
In the case of WordPress/WooCommerce and PrestaShop, it is worth configuring the application cache, optimizing images, limiting heavy plugins and checking for bots and crons.
346. How to optimize images?
For the topic "how to optimize images", first check the setting in the LVE, cache and real page response time charts.
TTFB, PageSpeed and cache analysis help distinguish a slow hosting from a slow application. Check HTML response time, image size, browser cache, number of scripts, database queries and LVE load.
In the case of WordPress/WooCommerce and PrestaShop, it is worth configuring the application cache, optimizing images, limiting heavy plugins and checking for bots and crons.
347. How to optimize cron and imports?
For the topic "how to optimize cron and imports", first check the setting in the LVE, cache and real page response time charts.
TTFB, PageSpeed and cache analysis help distinguish a slow hosting from a slow application. Check HTML response time, image size, browser cache, number of scripts, database queries and LVE load.
In the case of WordPress/WooCommerce and PrestaShop, it is worth configuring the application cache, optimizing images, limiting heavy plugins and checking for bots and crons.
348. How to set cache for WordPress/WooCommerce?
For the topic "how to set cache for WordPress/WooCommerce", first check the setting in the LVE, cache and real page response time charts.
TTFB, PageSpeed and cache analysis help distinguish a slow hosting from a slow application. Check HTML response time, image size, browser cache, number of scripts, database queries and LVE load.
In the case of WordPress/WooCommerce and PrestaShop, it is worth configuring the application cache, optimizing images, limiting heavy plugins and checking for bots and crons.
349. How to set cache for PrestaShop?
For the topic "how to set cache for PrestaShop", first check the setting in the LVE, cache and real page response time charts.
TTFB, PageSpeed and cache analysis help distinguish a slow hosting from a slow application. Check HTML response time, image size, browser cache, number of scripts, database queries and LVE load.
In the case of WordPress/WooCommerce and PrestaShop, it is worth configuring the application cache, optimizing images, limiting heavy plugins and checking for bots and crons.
350. What is worth knowing about CDN and integration with the cache service?
For the topic "what is worth knowing about CDN and integration with the cache service", first check the setting in the LVE, cache and real page response time charts.
TTFB, PageSpeed and cache analysis help distinguish a slow hosting from a slow application. Check HTML response time, image size, browser cache, number of scripts, database queries and LVE load.
In the case of WordPress/WooCommerce and PrestaShop, it is worth configuring the application cache, optimizing images, limiting heavy plugins and checking for bots and crons.
10217. How to solve the problem: what happens if I exceed the server's space?
Once the disk space is exceeded, the account may stop accepting mail, saving files, creating backups or updating the database. The customer should check cPanel → Disk Usage and Email Disk Usage, delete unnecessary backups/caches/logs/old messages or increase the package. Important: local copies on the same account also consume the limit, so it is best to keep backups off the server.
10230. How to solve the problem: hosting package load limit exceeded?
Exceeding the load limit means that the account has used more CPU/RAM/IO/processes than the package allows. Symptoms include slow performance, 508/503, intermittent crons, or slow response times. The client should check Resource Usage, error_log, recent CMS changes, cron jobs and bot traffic. The solution is to optimize the application, cache, remove the infection or change the package to a higher one.
10278. How to block the operation of indexing robots?
Crawlers can be restricted by the robots.txt file in the domain root, the noindex meta tag in HTML, or the X-Robots-Tag header. For technical blocking, you can use .htaccess, CDN or WAF, but you must be careful not to block users. Robots.txt is a request to robots, not a security feature - malicious bots can ignore it.
10314. How to block resource-sipping bots?
Bots saturating resources should first be identified in access logs: IP, user-agent, URL and frequency. Then you can limit traffic via robots.txt, .htaccess rules, IP/UA blocking, rate limiting in the application, CDN/WAF and reporting to support for blocking in CSF/Imunify360. You should not blindly block popular user-agents, because you may cut off legitimate users or search engine bots.
10393. How to solve the problem: blocking AI bots from accessing websites?
AI bots can be limited by robots.txt, e.g. separate rules for known user-agents, and technically by .htaccess, WAF/CDN or IP/UA blocks. Please note that robots.txt is voluntary and will not stop malicious bots. First, it is worth analyzing access logs to block specific user-agents or networks without harming SEO and legitimate users.