# Why is my WordPress site slow? A guide to diagnosing and fixing performance issues > A slow WordPress site is one of the most common issues we hear about, and the good news is that it is almost always fixable. This guide helps you identify the most likely cause and points you to the right next step. Source: https://www.kualo.com/knowledgebase/wp-troubleshooting/why-is-my-wordpress-site-slow-a-guide-to-diagnosing-and-fixing-performance-issues Updated: 2026-06-16 --- Our servers run fast CPUs and NVMe storage, so if your WordPress site feels slow the bottleneck is almost never the hardware. In our experience, slowness nearly always comes down to something at the application level - a missing caching layer, unoptimised images, too many plugins, a misconfigured environment, or a PHP version that is past its best. Work through the checks below and you will almost always find the cause. The good news is that it is almost always fixable. This guide is a triage tool to help you identify the most likely cause and points you to the right next step, whether that is a self-serve fix or a conversation with our support team. ## Start with a baseline measurement Before you change anything, run a free speed test using a tool such as [GTmetrix](https://gtmetrix.com), [Pingdom](https://tools.pingdom.com), or Google PageSpeed Insights. Note the score and the load time. This gives you something concrete to measure against after each change you make. If you are not sure how to read the results, our guide on [how to read speed reports](/knowledgebase/perf-speed/how-to-read-speed-reports-gtmetrix-pingdom-pagespeed) explains what each metric means. :::tip Always test in an incognito or private browser window with your browser cache cleared. A cached version of your site will look faster than it really is, which makes it harder to spot a genuine problem. ::: ## Understand the two types of slowness Slowness generally falls into one of two categories, and it helps to know which you are dealing with. **Server-side slowness** is caused by something on the hosting account itself - PHP processing, database queries, resource limits, or a lack of caching. This is the area where we can help most directly, and where the fixes in this guide will have the biggest impact. **Front-end slowness** is caused by what the browser has to download and process once the server has responded - large images, unminified JavaScript, too many third-party scripts, and so on. This is largely in your hands as the site owner, because it comes down to how the site has been built and what assets it loads. Caching tools such as LiteSpeed Cache help with both: they reduce the work the server has to do and can also optimise the assets sent to the browser. But no amount of caching will fully compensate for a theme that loads three megabytes of images on every page, or a plugin that runs dozens of slow database queries. ## Common causes and what to do about each one ### No caching in place By default, WordPress builds every page from scratch on each visit, running PHP and database queries every time. Caching stores a ready-made version of each page and serves it to subsequent visitors without that overhead. Our hosting stack uses LiteSpeed, so [LiteSpeed Cache (LSCache)](/knowledgebase/wordpress-optimisation/configuring-litespeed-cache-with-wordpress) is the caching plugin we recommend - it integrates directly with the server and is significantly more effective than generic caching plugins. :::warning Do not run more than one full-page caching plugin at a time. LiteSpeed Cache and another caching plugin running simultaneously will conflict and can produce unpredictable results, including broken pages. If you are switching to LSCache, deactivate any other caching plugin first. ::: If you are new to the concept of caching and want to understand how it works before diving in, our [beginner's guide to caching on WordPress](/knowledgebase/wp-getting-started/understanding-caching-on-wordpress-a-beginner-s-guide) is a good starting point. ### Too many or poorly coded plugins Every active plugin adds code that runs on every page load. A site with fifty plugins will almost always be slower than one with fifteen, even if none of the individual plugins is obviously broken. Poorly coded plugins can also run expensive database queries or load large assets unnecessarily. Our guide on [managing and auditing WordPress plugins for performance](/knowledgebase/wordpress-optimisation/managing-and-auditing-wordpress-plugins-for-performance) walks you through how to identify the culprits. :::tip If you suspect a specific plugin is causing slowness, deactivate plugins one at a time rather than all at once. Disabling everything on a live site can cause it to break for visitors, and you will not know which plugin was responsible. ::: For general plugin management, see [how to manage your plugins in WordPress](/knowledgebase/wp-using/how-to-manage-your-plugins-in-wordpress). ### Unoptimised database Over time, your WordPress database accumulates clutter: post revisions, expired transients, spam comments, and orphaned data left behind by deleted plugins. This makes queries slower and the database larger than it needs to be. Our article on [understanding and reducing database query load in WordPress](/knowledgebase/wordpress-optimisation/understanding-and-reducing-database-query-load-in-wordpress) explains how to identify and address this, and our guide on [WordPress transients](/knowledgebase/wordpress-optimisation/understanding-wordpress-transients-what-they-are-and-how-to-manage-them) covers one of the most commonly overlooked sources of database bloat. ### Unoptimised images Oversized or uncompressed images are one of the most frequent reasons WordPress sites feel sluggish. A single full-resolution photograph uploaded straight from a camera can be several megabytes, and a page with ten of them will be painfully slow for visitors on any connection. Our guide on [how to optimise WordPress images for faster loading](/knowledgebase/wordpress-optimisation/how-to-optimise-wordpress-images-for-faster-loading) covers the practical steps, including compression, resizing, and lazy loading. ### Outdated WordPress core, themes, or plugins Running old versions of WordPress, your theme, or your plugins is not just a security risk - it also means you are missing performance improvements that have been added in newer releases. Keeping everything up to date is one of the simplest things you can do. See [how to update your WordPress installation](/knowledgebase/wp-using/how-to-update-your-wordpress-installation) and [WordPress auto updates - how they work and best practice](/knowledgebase/wp-security/wordpress-auto-updates-how-they-work-and-best-practice) for guidance. ### Old PHP version PHP is the language WordPress runs on, and newer versions are measurably faster than older ones. Running PHP 7.4 instead of PHP 8.4, for example, can have a noticeable impact on page generation times. You can check and change your PHP version using the "Select PHP Version" tool in cPanel (this is the CloudLinux PHP Selector). Our guide on [how to manage the PHP version in cPanel](/knowledgebase/cpanel-php/how-to-manage-the-php-version-in-cpanel-using-the-select-php-version-tool) explains how. :::warning Changing your PHP version can occasionally cause compatibility issues with older plugins or themes. Before making the change, take a backup using [WP Toolkit](/knowledgebase/wp-toolkit/backing-up-your-wordpress-website-with-wp-toolkit), and consider testing on a staging copy first. See [creating staging websites with WP Toolkit](/knowledgebase/wp-toolkit/creating-staging-websites-with-wp-toolkit) for how to set one up. ::: For more detail on which PHP settings affect performance, see [optimising WordPress PHP settings for performance](/knowledgebase/wordpress-optimisation/optimising-wordpress-php-settings-for-performance). ### Heavy or poorly coded theme Page-builder-heavy themes often load a large amount of CSS, JavaScript, and web fonts on every page, even on pages that do not use those features. If you suspect your theme is a significant contributor to slowness, a quick test is to temporarily switch to a default WordPress theme such as Twenty Twenty-Four and re-run your speed test. If the score improves substantially, the theme is likely part of the problem. Do this on a staging site rather than your live site if possible. Our guide on [how to install and manage WordPress themes](/knowledgebase/wp-getting-started/how-to-install-and-manage-wordpress-themes) covers how to switch themes safely. For more on reducing the impact of JavaScript and CSS assets, see [minifying and combining CSS and JavaScript in WordPress](/knowledgebase/wordpress-optimisation/minifying-and-combining-css-and-javascript-in-wordpress) and [deferring and lazy-loading JavaScript in WordPress with LiteSpeed Cache](/knowledgebase/wordpress-optimisation/deferring-and-lazy-loading-javascript-in-wordpress-with-litespeed-cache). ### Slow PHP code (advanced) If you have worked through the common causes above and your site is still slow, the problem may be in the PHP code itself rather than in configuration or assets. Xdebug is a PHP debugging and profiling extension that can generate a detailed trace of exactly which functions are taking the most time on each request - useful when you need to pinpoint a slow plugin, theme function, or custom code rather than guessing by disabling things one at a time. Xdebug is an advanced tool aimed at developers. Enabling it on a live site will slow it down noticeably, so it should only be used on a staging copy or a local development environment. Our guide on [profiling slow PHP requests with Xdebug](/knowledgebase/dev-cli/profiling-slow-php-requests-with-xdebug) explains how to enable it and interpret the results. ## Hosting-level factors If you have worked through the causes above and your site is still slow, the issue may be at the hosting level rather than within WordPress itself. Every shared hosting account runs within CloudLinux resource limits (known as LVE limits), which cap the CPU, memory, and concurrent connections available to your account. If your site is consistently hitting those limits - for example, during a traffic spike or because of a resource-hungry plugin - it may be throttled and will appear slow. You can get an overview of your current resource usage in cPanel; see [understanding resource usage in cPanel](/knowledgebase/cpanel-account/understanding-resource-usage-in-cpanel) for how to read it. If you believe you are hitting your limits regularly, contact our support team. If you are experiencing unusual latency that does not seem related to any of the causes above - for example, slow response times even for a completely uncached, minimal page - please raise a support ticket. Shared IP and server-level issues are ours to investigate and resolve. You can also use the [Resource Boost feature in cPanel](/knowledgebase/cpanel-account/how-to-use-resource-boosts-in-cpanel) to temporarily increase your account's resources for up to 72 hours per month at no extra cost, which can be useful during a traffic spike while you work on a longer-term fix. ## What to do if you are still stuck If you have worked through the steps above and your site is still slower than you would expect, here is a quick decision guide: - **Tried image optimisation, caching, plugin audit, database cleanup, PHP version update, and theme testing** - and still slow? Contact our support team. - **Seeing high resource usage in cPanel** - contact our support team; we can investigate whether your account limits need adjusting. - **Seeing slow response times on a near-empty page** - contact our support team with your speed test results and a note of what you have already tried. To raise a ticket, see [how to create a support ticket in MyKualo](/knowledgebase/getting-started/how-to-create-a-support-ticket-in-mykualo). The more information you can include - speed test URLs, what you have already changed, and when the slowness started - the faster we can help. --- _Source: Kualo Knowledgebase — https://www.kualo.com/knowledgebase/wp-troubleshooting/why-is-my-wordpress-site-slow-a-guide-to-diagnosing-and-fixing-performance-issues · © Kualo Ltd._