5 min read
To improve WordPress speed, you need to find what’s slowing the site down. Advice such as “use fewer plugins” or “install WP Rocket and compress images” gives you a starting point. Like “eat less and exercise more” for weight loss, it leaves a lot unexplained. After 20+ years optimising WordPress sites for local Newcastle businesses and international eCommerce stores, I’ve learnt to start with some detective work.
Where I look for WordPress speed problems
Hosting and server response
Your hosting provider’s Time To First Byte (TTFB) matters more than most plugins. I’ve seen clients struggling with 3-second load times on expensive hosting because the server was slow to respond. At Baltic Design, I use WPX and Kinsta because their server caching and CDN integration consistently provide sub-200ms TTFB.
Database bloat
WooCommerce sites are particularly prone to this. Every product variation, abandoned cart and plugin deactivation leaves data behind. I use Query Monitor and Kinsta APM to find the queries holding things up, often uncovering 500+ unnecessary database calls on a single page load.
Plugin conflicts
Plugin combinations deserve a closer look than the plugin count alone. I’ve seen sites with 50+ plugins running smoothly, and others with 10 plugins crawling. You need to understand how those plugins interact at code level.
How I improve WordPress speed
1. Find the bottleneck with performance monitoring
I start with Kinsta APM or New Relic to find the actual bottlenecks. GT Metrix and Lighthouse give you scores, but those scores don’t tell you whether you’re dealing with PHP memory limits, database queries or render-blocking resources.
For eCommerce sites, I check:
- Product page load times at different inventory levels
- Cart and checkout performance with different payment gateways
- Search speed, especially with large catalogues
2. Configure plugins around the site
Installing WP Rocket is only the start. I work through its settings to suit the site:
- Set up minification without breaking custom CSS
- Exclude dynamic content, such as user accounts and cart contents, from caching
- Schedule database cleanups so they don’t interfere with business operations
I pair it with Perfmatters to disable WordPress and WooCommerce features the site doesn’t need. That might mean removing emoji scripts from a B2B site or disabling comments on an eCommerce store.
3. Sort image sizing, loading and delivery
I use Imagify for compression and WebP conversion. I also check how images reach the visitor:
- Set up lazy loading without breaking above-the-fold content
- Size images correctly at upload, rather than relying on compression to fix oversized files
- Use CDN delivery that adapts to the visitor’s connection speed
4. Fix inefficient code
Sometimes an inefficient plugin needs replacing with custom code. I’ve built custom plugins for clients such as Stairparts Direct to handle complex product configurations without database overhead. Experience helps you judge when to improve existing code and when to replace it.
Two WooCommerce problems that needed a closer look
Product variations causing 8+ second loads
One client’s product pages took 8+ seconds to load, but only for products with multiple variations. Their theme loaded all variation data upfront instead of fetching it on demand. I wrote custom PHP to change how that data was queried and cached.
Fast browsing followed by a 15-second checkout
Another client’s shop was very quick to browse, yet checkout took 15 seconds to load. Payment gateway plugins were making external API calls without proper timeout handling. I added custom error handling and local caching for non-critical payment features.
Settings that can make things worse
I regularly fix sites where well-meaning business owners have:
- Overdone the caching and broken user account features
- Minified CSS and JavaScript so aggressively that forms stop working
- Installed several optimisation plugins that conflict with each other
- Deleted “unnecessary” files that specific features depend on
Change settings carefully and check the features people need to use. A cache setting that breaks an account page or checkout needs fixing, whatever the speed score says.
What the improvements meant for two clients
For Stairparts Direct, reducing product page load times from 4.2 seconds to 1.8 seconds increased the conversion rate by 23%. Their mobile bounce rate also fell by 31%. Most of their traffic comes from mobile devices, so that was particularly useful.
The Renown Group saw similar improvements. Their biggest gain was the experience during busy periods: the site now handles 3x the concurrent users without performance degradation.
Seeing technical work make an immediate difference to a business is the rewarding bit for me. Faster sites improve the user experience and directly affect conversion rates, search rankings and revenue.
What my diagnostic tools tell me
- Kinsta APM: Shows actual server resource usage and database query performance. Google PageSpeed gives theoretical optimisation suggestions, which serve a different purpose.
- Query Monitor: Gives real-time insight into which plugins and themes are causing database overhead, with more detail than basic debug plugins.
- New Relic: Provides application-level performance monitoring beyond built-in analytics, revealing issues before they affect users.
Signs it’s worth getting help
- Your site is fast on desktop but slow on mobile. This often points to server or caching configuration issues.
- Performance changes dramatically throughout the day. Resource limits or plugin conflicts may be involved.
- Speed optimisation plugins have made the site slower. That usually suggests a deeper technical issue.
- Your eCommerce checkout has unexplained delays. Payment gateways and database problems are common causes.
I enjoy complex WordPress optimisation work because each site needs technical investigation and an understanding of how the business uses it. Your hosting, WordPress setup and business requirements all affect the right approach. That judgement comes from hands-on experience.
If basic fixes haven’t solved your speed problems, or you need the site to cope with growth, I’d be happy to discuss your specific situation. A quick audit can reveal simple fixes or show where more substantial work would help.








