There’s a persistent problem with WordPress sites that no one takes clean ownership of. The developer hands over the site. The SEO audits it and flags performance issues. The developer says it’s not their job. The SEO says they can’t make code changes. The client sits in the middle wondering why their site is slow and their rankings aren’t improving.

This is WordPress performance optimisation: the work that technically belongs to everyone and practically belongs to no one.

Why WordPress Sites Slow Down

WordPress is the most widely used CMS in the world, which means it’s also the most widely abused. The ease of installing plugins, adding page builder layers and extending functionality through themes creates a particular set of performance problems that don’t appear on any other platform quite the same way.

Plugin Bloat

The average WordPress site has significantly more plugins installed than it needs. Each plugin adds PHP execution overhead, database queries and often its own CSS and JavaScript files, loaded whether they’re needed on that page or not.

Over time, plugins accumulate. A plugin is installed for a one-off campaign, the campaign ends and the plugin stays. Each one is a small drag on performance. Collectively, they can be substantial.

Plugin rationalisation, auditing what’s installed, removing what isn’t needed and finding lighter alternatives for core functions, is one of the highest-impact, lowest-glamour performance fixes available.

Database Bloat

WordPress stores a lot in its database: post revisions, transients, spam comments, unused metadata and orphaned rows from uninstalled plugins. On an established site, this accumulates into thousands of unnecessary rows that slow down every database query.

Regular database optimisation, removing post revisions, clearing expired transients and cleaning up orphaned data, keeps queries fast. It’s maintenance work rather than development work, but it’s rarely done unless someone specifically owns it.

DOM Complexity

Page builders, Elementor, Divi and WPBakery among them, generate HTML. A lot of it. The visual convenience of drag-and-drop layout comes at the cost of deeply nested, wrapper-heavy HTML structures that browsers have to parse and render.

A high DOM node count (Google flags anything over 1,400 nodes as a concern) increases memory usage, forces longer style calculations and contributes to poor Interaction to Next Paint scores. It’s a direct consequence of how most WordPress sites are built.

Unoptimised Assets

Large images, unminified CSS and JavaScript, scripts loaded globally rather than conditionally and fonts loaded from external sources without preloading all compound to produce the sluggish load behaviour that PageSpeed Insights flags.

The issue isn’t that these problems are hard to fix individually. It’s that fixing them requires someone who understands both the performance implications and the technical implementation in WordPress.

Why This Falls Through the Gap

SEO professionals are trained to identify performance issues. They know how to read a PageSpeed Insights report, understand what’s causing the problem and articulate what needs to change. But most SEOs don’t make direct code changes to clients’ sites. They hand over recommendations and wait.

Developers know how WordPress works. They can make the changes. But performance optimisation wasn’t part of the brief, and unless a developer has a specific interest in SEO, the nuance of why a particular fix matters in a search context can get lost in translation.

So the recommendation sits in a document. The developer adds it to the backlog. The client asks about rankings at the next review meeting. Nothing has changed.

What Effective Performance Optimisation Looks Like

Done properly, WordPress performance work involves:

• Audit first. Baseline measurements using PageSpeed Insights, GTmetrix or equivalent, capturing LCP, CLS, INP, TTFB and total page weight across key pages. Mobile and desktop, separately.
• Plugin audit. Full inventory of installed plugins against what’s actually being used. Removal recommendations and, where needed, lighter alternatives.
• Database clean-up. Removal of post revisions, transients, spam and orphaned data. Optimising database tables.
• Image optimisation. Compression, conversion to WebP or AVIF where appropriate, lazy loading for below-fold images and explicit dimensions to prevent layout shift.
• Script and style management. Deferring JavaScript, removing globally loaded assets that are only needed on specific pages and inlining above-the-fold CSS.
• Font optimisation. Self-hosting where possible, preloading and font-display: swap to prevent invisible text during load.
• Server and caching review. Object caching configuration, page caching and CDN setup where appropriate.
• Retest and document. Before-and-after measurements showing the improvement. Benchmarks for ongoing monitoring.

The Agency Angle

For agencies managing ongoing client relationships, site performance is a retainer conversation waiting to happen. A client whose site is visibly slow, flagged in Search Console for Core Web Vitals issues, or dropping in rankings for reasons that aren’t obviously content-related, has a problem you can solve.

The question is whether you have someone who can bridge the SEO knowledge and the WordPress implementation in one engagement, rather than requiring the client to coordinate between two separate specialists.

Nat20 Marketing offers WordPress performance optimisation as a standalone service or as part of a broader technical SEO engagement. The findings get implemented, not just reported. Get in touch to find out more.