Skip to main content
Submit a request

Why is my website slow?

Maxim Tsitsejev
Updated

Applies to: All plans (Self-Managed and Managed).

A slow site is almost always one of five things, in this order: no caching, an old PHP version, heavy plugins or slow database queries, large unoptimised images, or your account brushing up against its CloudLinux resource limits. Work down the list below — each step is quick, and most sites speed up dramatically after the first two.

Our servers run LiteSpeed with server-level caching, and each account is isolated with its own CloudLinux (LVE) resource allowance. That means your speed is mostly in your control — and so is the fix.

Symptoms

  • Pages take several seconds to load, or feel sluggish only at busy times.
  • The site is fast when logged out but slow in the admin area (or the reverse).
  • Occasional 508 "Resource Limit Reached" errors under load — a sign you're hitting your CPU, memory or process limit, not just "slow".
  • One page (a cart, search, or report) is far slower than the rest.

Common causes (most likely first)

  1. No page caching. Without a cache, the server rebuilds every page from scratch on each visit. This is the single biggest cause of slowness on WordPress and similar apps.
  2. An old PHP version. Older PHP runs your code far slower. A modern release (PHP 8.x) is usually a big, free speed gain.
  3. Heavy plugins or slow queries. A few badly written plugins, page builders, or un-indexed database queries can dominate your load time and your CPU usage.
  4. Large images and unoptimised assets. Multi-megabyte images, no compression, and no lazy-loading make pages feel slow even on a fast server.
  5. Resource limits. If your account exceeds its CloudLinux allowance, requests are briefly queued or rejected (a 508) and everything feels slow until usage drops.

Quick fixes

Work through these in order. Test your speed before and after each one so you can see what helped.

  1. Measure first. Run your site through a free tool such as Google PageSpeed Insights, GTmetrix or WebPageTest, and note the load time and the biggest items it flags (often images and render-blocking scripts). Re-run it after each change below.
  2. Turn on caching. This is the highest-impact step. On WordPress, install and enable the LiteSpeed Cache (LSCache) plugin — it pairs with our server-level cache and is the recommended caching path on our platform. For other apps, enable whatever full-page caching they offer. See the LSCache guide linked below.
  3. Update your PHP version. In cPanel, open the option labelled MultiPHP Manager, select your domain and switch it to a current PHP 8.x release. If something breaks, switch back and ask your developer which version the site needs. (Open cPanel from the client area: open your service, then Log in to cPanel.)
  4. Audit your plugins and themes. Deactivate anything you don't use. To find a slow plugin, deactivate them one at a time (or in batches) and re-test speed. Page builders, "all-in-one" security suites, and related-posts/analytics plugins are common offenders. Keep core, plugins and themes updated.
  5. Optimise your database. Slow, repeated queries hammer both speed and CPU. Remove unused plugins that write to the database, delete old post revisions and spam, and use an indexing/optimisation plugin if your app supports one. Our MySQL Governor smooths heavy database use, but reducing the work is what makes pages fast.
  6. Optimise images. Resize images to the dimensions they actually display at, compress them (an image-optimisation plugin or an export setting will do this), use modern formats like WebP, and enable lazy-loading. This alone often halves page weight.
  7. Check your resource usage. In cPanel, open the resource-usage / CloudLinux statistics tool (shown on the cPanel home page and under the metrics tools) to see whether you're hitting CPU, memory (PMEM), entry-process or IO limits. If you're regularly near the top, that's your bottleneck — see the resources article below.

Result: With caching on and a modern PHP version, most sites drop from several seconds to under a second or two. If you're still slow, the cause is usually a specific plugin, a heavy query, or your plan's limits.

If that did not work

  • You keep hitting resource limits. If you've cached, trimmed plugins and optimised but still see high CPU/memory or 508 errors, your site genuinely needs more headroom than your plan provides. Upgrading the plan raises your CloudLinux limits — see when to upgrade below.
  • One page is slow, the rest are fast. That points to a specific feature (search, cart, an API call, an un-cached dynamic page). Caching usually skips logged-in or cart pages by design, so focus your tuning there.
  • You'd like us to look. On Managed plans this is part of what we cover and we monitor 24/7. On Self-Managed, send us your findings and we'll point you in the right direction. Either way, include your domain, the slow page's URL, your before/after test results, and when it started.

Related articles

Comments

0 comments

Please sign in to leave a comment.