Improving WHMAZ Performance

If the admin portal has become sluggish, work through these in order of impact.

1. Enable OPcache

The single biggest improvement available, and it takes a minute. In php.ini:

  • opcache.enable — set to 1
  • opcache.memory_consumption — set to 128
  • opcache.max_accelerated_files — set to 10000

Restart the web server afterwards.

2. Clear out old log files

The application/logs/ directory grows indefinitely. A directory holding years of logs slows down writes and consumes disk. Keep the last month and archive or delete the rest:

find /path/to/whmaz/application/logs -name "*.php" -mtime +30 -delete

Also confirm you are not still running in development mode, which logs far more heavily.

3. Optimise the database tables

Tables that see constant inserts and deletes accumulate overhead:

mysqlcheck -o -u your_db_user -p your_db_name

4. Raise the PHP memory limit

Reports and large customer lists are the usual culprits. 256M is a reasonable baseline; 512M if you have a large install.

5. Use a current PHP version

PHP 8.x is substantially faster than 7.4 for the same code. If your host offers a PHP selector, test a newer version on a staging copy and move up.

6. Serve static assets efficiently

Enable gzip or Brotli compression and set long cache lifetimes for CSS, JavaScript and images. A CDN in front of static assets helps if your customers are geographically spread.

If it is still slow

Check whether the server itself is the constraint. Sustained high load, exhausted memory or a saturated disk will not be fixed by any application-level change.

Was this article helpful?