Why is my WordPress site slow? In most cases it comes down to one of four things: slow hosting, missing caching, oversized images, or too much code from plugins, page builders and third-party scripts. Usually it is a mix of several.
I’ve fixed slow WordPress sites for years, most of them while working at digital marketing agencies. The cause is rarely mysterious once you measure first and guess second.
Here is how to find yours, then the nine causes I see most often.
First, measure before you change anything
Run your homepage and one inner page through Google PageSpeed Insights. Test on mobile, because that is the score Google uses for most sites.
Note three numbers. They are Google’s Core Web Vitals, and each has a “good” threshold:
- Largest Contentful Paint (LCP): 2.5 seconds or less. How long the main content takes to appear.
- Interaction to Next Paint (INP): 200 milliseconds or less. How quickly the page responds to a tap or click.
- Cumulative Layout Shift (CLS): 0.1 or less. How much the layout jumps around while loading.
Also look at Time to First Byte in the diagnostics. If the server takes more than about 0.8 seconds just to start responding, start with causes 1 and 2.
9 reasons your WordPress site is slow
1. Your hosting is underpowered
Cheap shared hosting puts hundreds of sites on one server. When a neighbour gets busy, your site waits.
Fix: move to a host with modern PHP, server-level caching and a data centre near your visitors. For customers in the Philippines, a server in Singapore usually beats one in the United States.
2. There is no page caching
Without caching, WordPress runs PHP and database queries to build every page for every visitor.
Fix: turn on your host’s cache, or install one well-supported caching plugin. Use one only; two caching plugins fight each other.
3. Images are too large
A photo straight from a phone can be several megabytes. A page with a few of them crawls on mobile data.
Fix: resize images to the size they are shown at, convert them to WebP and let WordPress lazy-load anything below the fold. Never lazy-load the main image at the top of the page; it delays LCP.
4. Plugins load code on every page
Sliders, form builders and social feeds often load their scripts and styles site-wide, even on pages that don’t use them.
Fix: on a staging copy, deactivate plugins one at a time and re-test. Remove what you don’t need, and replace heavy plugins with lighter ones.
5. The theme or page builder is heavy
Multipurpose themes and page builders add wrapper elements, CSS and JavaScript to every page. The cost is highest on older sites built before these tools improved.
Fix: turn on the builder’s performance settings, and use the block editor for new pages. I compare the two in Elementor vs Gutenberg.
6. Third-party scripts
Chat widgets, tracking pixels, embedded maps, videos and external fonts all load from other servers that you don’t control.
Fix: remove the ones nobody uses, load the rest after the page is interactive, and host fonts on your own server.
7. An outdated PHP version
Newer PHP versions run WordPress noticeably faster than old ones, and old versions stop receiving security fixes.
Fix: check your PHP version in Tools → Site Health, and upgrade through your hosting panel after a backup and a test on staging.
8. A bloated database
Years of post revisions, spam, expired transients and tables left by deleted plugins make queries slower, especially in the dashboard.
Fix: limit revisions, clear spam and expired transients, and remove orphaned tables. Take a backup first.
9. No CDN for visitors far from the server
Every image, stylesheet and script travels from your server to the visitor. The further away they are, the longer each request takes.
Fix: a content delivery network keeps copies of your files around the world. Many hosts include one.
Which fixes to try first
Work from the biggest, cheapest wins down. In my experience, this order fixes most sites:
- Turn on page caching.
- Compress and resize the images on your most visited pages.
- Remove unused plugins and third-party scripts.
- Update PHP.
- Upgrade hosting if Time to First Byte is still slow.
Re-test after each change, so you know what made the difference.
Keep it fast
Speed drifts. New plugins, bigger images and new scripts slowly undo the work, which is why a quarterly speed test is on my WordPress maintenance checklist.
If you’d rather hand it over, speed checks are part of my WordPress support and maintenance, and a new build through WordPress development starts fast from day one.
Frequently asked questions
How fast should a WordPress site load?
Aim for the main content to appear within 2.5 seconds on a phone. That is Google’s “good” threshold for Largest Contentful Paint, one of the Core Web Vitals.
Will a caching plugin fix a slow WordPress site?
It often helps a lot, because it stops WordPress building every page from scratch. It will not fix slow hosting, oversized images or heavy scripts, so treat it as one step, not the whole fix.
Do too many plugins slow down WordPress?
The number matters less than what each plugin does. One badly built plugin that loads scripts on every page can do more damage than twenty small ones.
Why is my WordPress admin slow but the site is fast?
Visitors usually get cached pages, but the dashboard is never cached. A slow admin points to the server, a heavy plugin running in the background, or a large database.
About the author
Vincent Earl Panoncial is a WordPress developer and the founder of VEP Studio. He has built and maintained 100+ WordPress websites, most of them at digital marketing agencies, and now works directly with businesses on development, maintenance and webmaster services.
Need a hand with your WordPress site?
Tell me what your website needs and you’ll get a clear plan and an honest answer on cost before any work starts. Get a free consultation →
Featured photo by Chris Liverani on Unsplash.