Overcoming the speed disadvantages of WordPress

While WordPress has its advantages, these often come at a performance penalty. Page speed is a challenge that scales linearly or even exponentially if the proper foundations are not put in place early.

WordPress is rarely slow by design. It gets slow by accumulation. Here is how I win the speed back on real agency builds.

WordPress has a reputation for being slow, and on plenty of sites it has earned it. But the platform itself is rarely the problem. Speed is lost one decision at a time: a heavy theme here, an extra plugin there, a hero image straight from a phone camera. Under agency conditions, with tight deadlines, handovers and clients who need just one more feature, those decisions pile up fast. The good news is that most of them can be reversed. This is the process I rely on.

The first step is measuring before you touch anything.

Resist the urge to install a caching plugin on day one. I once inherited a brochure site scoring in the 40s on mobile, and everyone’s first instinct was to add caching. A proper audit told a different story: a slider library loading on every page, three font families and a page builder shipping CSS for features nobody used. Lighthouse, Query Monitor and a network waterfall show you what is actually slow. Caching would have hidden the problem rather than fixed it.

The second is treating every plugin as a cost.

Every plugin adds queries, scripts and styles, whether or not the page needs them. Agency sites collect plugins over the years as different developers solve different problems. Audit them honestly. If a plugin does one small job, replace it with a few lines of custom code. If you need it, stop it loading everywhere by dequeuing its assets on pages that do not use it. On one WooCommerce build, removing a single plugin that existed only to show a sticky banner took a noticeable chunk off every page load.

The third is getting images right.

Largest Contentful Paint is usually an image, so images are usually where the biggest win sits. Serve modern formats such as WebP or AVIF, generate sensible sizes with srcset and set explicit dimensions to prevent layout shift. Lazy load everything below the fold but never the hero, which should be preloaded instead. A client will always upload a 4MB photo the week after launch, so build the resizing into the system and give editors a simple guideline rather than relying on goodwill.

The fourth is controlling JavaScript and render blocking.

Defer what you can, load scripts conditionally and question every third party tag. Chat widgets, tag managers and tracking pixels add up quietly, and they usually arrive after the site has been signed off. Self host fonts, limit the weights and use font-display swap. Where possible, avoid jQuery dependent code for new features. Each change is small, but together they are the difference between a green score and an orange one.

The fifth is caching and hosting, in that order of honesty.

Once the site is lean, caching makes it fast. Use full page caching, an object cache for dynamic sites and a CDN for static assets. Then look at hosting. I have seen a well optimised site held back by cheap shared hosting and an outdated PHP version, and a move to a properly configured host did more than a week of code tweaks. Cache last, never first.

Take the leap to go headless.

Sometimes a fully optimised WordPress site still is not fast enough for the brief. That is where a decoupled setup earns its place: WordPress as the content layer, a Next.js & Vercel frontend and WPGraphQL in between, with Incremental Static Regeneration serving pages almost instantly. It is not free. You take on more complexity and need to plan for previews and plugin compatibility. For performance critical builds the trade is often worth it, but for many brochure sites a lean classic build is the better answer.

Keeping it fast is the real job.

Launch day is the easy part. Editors upload large files, new plugins appear and scripts get added. Set a performance budget, test regularly and document the rules for the team and the client. Speed is not a one off project. It is a habit.

If your WordPress site is slower than it should be, get in touch. I audit, fix and rebuild for performance, from quick wins to full headless builds.