Why WordPress Sites Get Slower Over Time

The Three Sources of WordPress Slowdown

WordPress sites get slower over time for three reasons that compound:

• **Plugin creep:** more plugins are added over time, each one adds weight
• **Theme drift:** themes accumulate features and bloat through updates
• **Database growth:** the database grows with revisions, transients, and spam

Each one is real. Together they explain almost every case of a WordPress site that "used to be fast and now isn't."

Plugin Creep (The Biggest Culprit)

A typical small business site launches with 8 to 12 plugins. Two years later, it has 20 to 35.

How does this happen?

• Marketing decides they want a popup, plugin
• Owner sees a chat widget on a competitor's site, plugin
• Accounting wants Stripe, plugin
• SEO consultant recommends Yoast or RankMath, plugin
• Cookie banner requirement, plugin
• "Just one more contact form," plugin
• Booking widget, plugin
• Social share buttons, plugin
• Spam filter, plugin
• Backup plugin (for the database that grew because of the other plugins), plugin

Each plugin loads its own scripts, styles, and database queries. Most of them load on every page, whether they're needed there or not.

A WordPress site I audited recently had 31 active plugins, each loading scripts on the homepage. The homepage was 4.2 MB.

The killer is that plugin authors get paid based on adoption, not on performance. A "lightweight" plugin in their description rarely measures lightweight in practice.

Theme Updates and Feature Drift

Themes also bloat over time. Theme developers add new features in updates because they're competing on feature lists for sales. A theme that started lightweight in 2020 has often gained:

• Header builder (extra JavaScript)
• Footer builder (extra JavaScript)
• Mega menu support (extra CSS and JS)
• Animations library
• Page builder integrations
• Block editor extras
• Demo content importer
• Customizer panels for things you don't use

Each update brings new features, new code, new dependencies. You can't easily strip these out because the theme is one piece.

Database Growth

WordPress stores everything in a MySQL database. Over time, this grows:

• **Post revisions:** every save creates a new revision. A 50-post blog can have 500+ revisions.
• **Plugin settings:** even removed plugins often leave their settings behind.
• **Transients:** temporary cached data that doesn't always clean itself up.
• **Comment spam:** sites without filtering accumulate thousands of spam comments.
• **Tracking tables:** some plugins create their own tables that never get cleaned up.

A WordPress site that started with a 5 MB database is often 100 MB plus after two years. Every page load runs database queries against this larger database. Most of the queries are slower as a result.

Database optimisation can recover 20 to 40 percent of lost performance, but only temporarily.

Hosting Throttling and Caching

Most small business WordPress sites run on shared hosting. As more sites join the same server, your share of the resources shrinks. Performance you had on day one isn't necessarily what you have on day 365.

Many shared hosts also throttle CPU or database queries during peak times. This isn't usually disclosed clearly. The site just gets slower at certain times of day and nobody knows why.

Caching plugins help, but they're a band-aid. They serve a snapshot of the page to anonymous visitors, which speeds things up. They don't actually fix the underlying weight, and they often break in subtle ways (logged-in users see different content, forms misbehave, and so on).

The Visible Symptoms

What does the slowdown look like from the outside?

• PageSpeed Insights mobile score drops from 75 to 50 over 18 months
• Largest Contentful Paint creeps from 2.1 seconds to 3.8 seconds
• Time to First Byte gets worse (often from 400ms to 900ms)
• The site feels "stickier" when you click around as an owner
• Customers occasionally mention "your site was slow"
• Google Search Console flags more pages as having "poor Core Web Vitals"
• Rankings slip slightly without any obvious content reason

The slope is gradual, which is what makes it dangerous. You don't notice it day to day. You notice it when you finally compare the site to a competitor's.

What You Can Do About It

The patches, in order of effort vs reward.

**Low effort:**

• Delete every plugin you don't actively need (most sites can lose 30 to 50 percent)
• Run a database cleanup (use WP-Optimize or similar; back up first)
• Compress images that aren't already compressed
• Switch to a lighter theme

**Medium effort:**

• Move to managed WordPress hosting (£25 to £80 a month)
• Install a proper caching plugin and configure it correctly
• Use a CDN like Cloudflare
• Remove unused features from your theme

**High effort (questionable return):**

• Custom code to load plugins only on pages where they're needed
• Custom theme to replace your current one
• Migration to a static site generator that uses WordPress as a headless CMS

You can usually claw back 15 to 25 PageSpeed points with the low-effort items. After that, it gets expensive in time or money for diminishing returns.

When To Stop Patching and Start Over

There's a point where patching WordPress costs more than rebuilding. Signs you're there:

• You've already done the low-effort cleanup and still score under 70
• You'd need a new theme to fix the design issues
• Half the plugins are there to fix problems caused by the other half
• Every change requires testing because something always breaks
• You haven't updated the site in months because it scares you

At that point, a clean hand-coded rebuild (which can pull your existing content in via migration) often delivers better results in less time than a major WordPress overhaul. For the broader case, see WordPress vs hand-coded websites.

A Pragmatic Closing Thought

WordPress is fine if you're prepared to maintain it like you would any other piece of business software. That means quarterly plugin audits, regular database cleanups, hosting upgrades when needed, and probably an hour a month of admin.

Most small businesses aren't prepared to do this. They want a website that works without constant attention. For them, WordPress's slow degradation isn't a quirk. It's a structural mismatch between what the platform needs and what the owner is willing to give it.

A hand-coded site has no plugins to update, no database to bloat, no theme to drift. It just stays the speed you launched at.