A slow WordPress site costs you twice: visitors leave before the page loads, and search engines treat poor page experience as a signal against you. The good news is that WordPress can be very fast. Performance problems almost always come from what has been added on top of it — and they can be measured and fixed systematically. This is the approach we use.
1. Measure before changing anything
Start with field data from real users (the Chrome UX Report, visible in Search Console and PageSpeed Insights), then use lab tools to reproduce problems. Measure the three Core Web Vitals — LCP, INP and CLS — on your most important templates: home, a service or product page, an article and any checkout or form. Then profile the server side with a tool such as Query Monitor to see slow queries, hooks and external calls.
2. Cache in layers
- Page cache at the server or CDN so anonymous visitors get static HTML.
- Persistent object cache (Redis or Memcached) so repeated database lookups are served from memory.
- Browser and CDN caching for images, CSS, JS and fonts, with long cache lifetimes and versioned file names.
Caching should be the last step of optimisation, not the only one: logged-in users, search and carts bypass it.
3. Fix the database and queries
Large wp_options tables with autoloaded data, unindexed meta queries, expensive related-posts plugins and runaway revisions are common causes of slow page generation. We clean autoloaded options, add indexes where safe, replace expensive queries and move heavy work to scheduled background jobs.
Caching hides slow code. Performance work removes it.
ESS ENN Associates Web Team
4. Make the front end light
- Serve images in modern formats (WebP or AVIF) at the right size, with explicit dimensions and lazy loading below the fold.
- Self-host fonts, subset them and preload the critical one.
- Remove unused CSS and JavaScript, defer non-critical scripts, and load third-party tags only where needed.
- Replace heavy page builders with native blocks where possible.
5. Audit plugins
For every plugin, ask what it does, whether it loads assets on every page, and whether a few lines of custom code would do the same job. Removing or replacing a handful of heavy plugins is often the single biggest improvement on a mature site.
6. Right-size the hosting
Current PHP versions, enough PHP workers for your traffic, an object cache and a CDN are the baseline. If the site is still slow after application fixes, the platform may be the bottleneck — see our managed WordPress hosting guide.
7. Keep it fast
Performance degrades as content, plugins and tags accumulate. Add performance budgets, monitor Core Web Vitals continuously and review them in your regular maintenance cycle, covered in WordPress maintenance and support.
Speed is also an SEO lever; for the wider picture, read SEO services for websites and e-commerce. Our web development team runs WordPress performance audits and fixes. To find out what is slowing your site, contact us.