A slow website is usually caused by a resource limit on your hosting account, missing caching, large images, or too many active plugins. This article explains how to check what's causing it and how to fix the most common issues.

Check your resource usage first

Your hosting account has a set CPU, memory and process limit based on your plan. When your site regularly hits these limits, pages load more slowly, time out, or show an error until usage drops. Checking your current usage is the fastest way to find out if this is the cause.

cPanel

  1. Log in to cPanel from the client area at my.hostking.host.
  2. Go to the Metrics section and click Resource Usage.
  3. Open the Current Usage tab.
  4. Check the CPU Usage, Memory Usage and Entry Processes graphs against their limits.
  5. Adjust the timeframe shown to see when usage spiked, which can help you match slowdowns to specific events, such as a traffic spike or a backup running.

DirectAdmin

  1. Log in to DirectAdmin from the client area at my.hostking.host.
  2. Go to Advanced Features and click Resource Usage.
  3. Check the CPU usage, memory usage and concurrent connections graphs.
  4. Use the Dashboard view to see if any problems occurred in the last 24 hours.
  5. Use the Snapshot tool if an error occurred, to see what was causing it at that moment.

What a resource limit error means

If your account reaches 100% of its CPU, memory or process limit, new requests are queued until existing ones finish, which shows up as a slow or unresponsive site. In some cases visitors may see an error such as "Resource Limit Is Reached" (error 508) until usage drops back down. This only affects your account, not the whole server.

Speed up a WordPress site with caching

If your site runs on WordPress, enabling a cache plugin usually gives the biggest speed improvement. Hostking's servers run LiteSpeed Web Server, so the LiteSpeed Cache plugin works well and is free to install.

  1. In your WordPress dashboard, go to LiteSpeed Cache in the left-hand menu.
  2. Open the Presets option and choose the preset closest to your type of site, then fine-tune settings afterwards.
  3. Make sure Enable Cache is switched on, as every other caching feature depends on it.
  4. Turn on Cache favicon.ico so the server doesn't have to run PHP just to serve the site icon.
  5. Turn on Lazy Load Images and set a placeholder, so images load as visitors scroll rather than all at once.
  6. Enable Minify CSS and Deferred JavaScript, testing the site afterwards to confirm nothing breaks.
  7. If your site is database-heavy (for example a WooCommerce shop), consider enabling object caching with Redis or Memcached if your plan supports it, and disable it again if you notice stale content or cart issues.

Other things to check

  • Large, unoptimised images: resize and compress images before uploading them.
  • Too many active plugins or a heavy theme: deactivate anything you don't need and check if speed improves.
  • An outdated PHP version: check your PHP version in cPanel or DirectAdmin and update it if an older version is selected.
  • A recent traffic spike: compare your resource usage graph with your site's visitor statistics for the same period.

Troubleshooting

  • Site is slow for everyone, all the time: check resource usage first, then enable caching.
  • Site is slow only after a change: undo the last plugin, theme or setting change and test again.
  • Site is slow only for logged-in visitors or in wp-admin: this points to plugins or database queries rather than caching, since cached pages mainly help logged-out visitors.
  • Error 508 "Resource Limit Is Reached": this confirms your account has hit its CPU, memory or process limit; follow the resource usage steps above to find the cause.
  • Caching plugin causes layout or login problems: disable the specific setting that was changed (for example, cached login pages) and test again.

If your site is still slow after trying these steps, contact Hostking support via live chat on the website or by opening a support ticket from the client area.

Was this answer helpful? 0 Users Found This Useful (0 Votes)