Home › Knowledgebase › KB-1223

How to optimise shared hosting resources for my small business website

Summary

This guide helps you troubleshoot and resolve: How to optimise shared hosting resources for my small business website. Follow the steps below to fix the issue.

Quick Tip: Need immediate assistance? 💻 Open a Ticket

Common Causes

Shared hosting is an economical way for small businesses to establish an online presence, but it comes with finite server resources shared among multiple accounts. When a website begins to outgrow its allocated resources, visitors may experience slow page load times, intermittent timeouts, or periods of unreliability. Optimising these resources involves identifying bottlenecks, streamlining website assets, and determining if your current hosting plan still meets your operational demands.

Warning: Always create a full backup of your website files and database before editing your .htaccess file or making any server-level changes. Incorrect syntax in your .htaccess file can cause your website to become inaccessible.

Quick Fix Steps

  1. Log in to your hosting control panel (cPanel or Plesk).
  2. Clear your website cache and browser cache to ensure you are viewing the most recent version of your site.
  3. Compress large images and optimise media files to reduce page weight.
  4. Disable or remove unused plugins, themes, and modules that consume server memory.
  5. Identify and terminate runaway scripts or processes that are monopolising CPU resources.
  6. Review your hosting control panel for resource usage alerts or throttling notifications.

Detailed Instructions

Identifying Resource Bottlenecks

Common signs that your shared hosting resources are being exhausted include:

Interpreting Resource Usage Alerts

To check resource usage in cPanel:

  1. Log in to cPanel.
  2. Navigate to Metrics > Resource Usage.
  3. Review the Current Usage table to see if CPU, physical memory, or entry processes are hitting their limits.
  4. Click Details on any resource that is consistently at 100% to view a snapshot of the processes causing the spike.

To check resource usage in Plesk:

  1. Log in to Plesk.
  2. Navigate to Websites & Domains > Resource Usage.
  3. Review the graphs for CPU and RAM consumption over the last 24 hours.
  4. Look for sharp spikes that correlate with slow site performance or error reports.

Identifying Runaway Scripts and Processes

Runaway scripts are often caused by poorly coded plugins, stuck cron jobs, or compromised files. To identify them:

  1. In cPanel, go to Metrics > CPU and Concurrent Connection Usage.
  2. Review the Snapshot section to see a list of the most resource-intensive processes currently running.
  3. Look for repeated entries of the same script (e.g., wp-cron.php or a custom PHP script) consuming high CPU percentages.
  4. Check your error logs via Metrics > Errors to see if specific scripts are repeatedly failing or timing out.
  5. If you use a CMS like WordPress, disable all plugins and reactivate them one by one to identify if a specific plugin is causing the resource spike.

Checking for Malware and Compromised Scripts

High resource usage can be a sign that your website has been compromised. Malicious scripts often run in the background to send spam or mine cryptocurrency.

  1. Run a malware scan using your hosting control panel's security tool or a reputable security plugin for your CMS.
  2. Review your file manager for recently modified files that you do not recognise, particularly in /wp-content/ or /public_html/ directories.
  3. Check for unknown user accounts in your CMS administrator panel.
  4. If malware is detected, restore your site from a clean backup taken before the compromise occurred.

Optimising Website Assets

  1. Audit your media library and compress images using tools that reduce file size without sacrificing visual quality.
  2. Enable browser caching and compression (such as Gzip or Brotli) via your .htaccess file or hosting control panel settings.
  3. Minify CSS, JavaScript, and HTML files to reduce the amount of data transferred per page load.
  4. Implement a Content Delivery Network (CDN) to cache static assets closer to your Australian visitors, reducing geographical latency.

Reviewing Hosting Plan Alignment

If optimisations do not resolve performance issues, your business may have outgrown its current plan. Consider the following:

Troubleshooting

Slow Page Load Times

  1. Run a speed test using a tool such as Google PageSpeed Insights or GTmetrix to identify specific assets causing delays.
  2. Check your server response time; if it exceeds 200ms, the bottleneck is likely server-side rather than client-side.
  3. Review error logs in your hosting control panel for repeated failed requests or script timeouts.

Intermittent Timeouts

  1. Monitor your site during different times of the day to see if timeouts correlate with traffic spikes.
  2. Check for cron jobs or automated backups running during business hours that may consume excessive resources.
  3. Contact your hosting provider to request a resource usage report for your account.

Resolving 504 Gateway Timeout Errors

  1. Refresh the page after a few minutes; a 504 error often indicates a temporary upstream server issue.
  2. Check if a long-running script or database query is causing the server to time out.
  3. Temporarily disable recently installed plugins or modules to see if the error persists.
  4. If the error continues across all pages, Open a Ticket for our Brisbane team to investigate server-side connectivity.

Resolving 508 Resource Limit Is Reached Errors

  1. Wait a few minutes and refresh the page; this error usually occurs when entry processes or CPU limits are momentarily exceeded.
  2. Navigate to Metrics > Resource Usage in cPanel to confirm which limit was reached.
  3. Reduce the number of concurrent processes by disabling heavy background tasks or scheduled jobs.
  4. Optimise your database tables to reduce query execution time.
  5. If 508 errors occur frequently during normal traffic, your site likely requires a plan upgrade.

Regularly updating your Content Management System (CMS), plugins, and themes can improve efficiency and reduce resource overhead caused by outdated code.

Avoid making significant changes to your production website without a full backup. Test optimisations in a staging environment where possible to prevent downtime.

Verifying Optimisations

After implementing changes, verify that your optimisations were successful:

  1. Run a speed test using Google PageSpeed Insights or GTmetrix and compare the results to your baseline measurements.
  2. Monitor your resource usage in cPanel or Plesk for 24 to 48 hours to ensure CPU and memory usage have stabilised.
  3. Visit your website during peak traffic times to confirm that 504 and 508 errors no longer appear.
  4. Check your server response time to ensure it remains under 200ms.

When to Contact Support

You should Open a Ticket and contact our Brisbane support team if:

Remember — If you host with us, you don't need to do this yourself — just Open a Ticket and our Brisbane team will get it sorted.

Still Having Issues?

Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.

💻 Open a Ticket