How to Speed Up a WordPress Website Without Installing Too Many Plugins

You can also see this in the GTmetrix waterfall on a simple page. Look for JS or CSS files from plugins that have no role on that page type.

What you can do:

• Check plugin settings for an option like "load assets only where used" or "disable on pages where plugin is inactive." Many well-maintained plugins include this.
• If no such setting exists, a developer can conditionally prevent loading with wp_dequeue_script() and wp_dequeue_style() in functions.php.
• If a plugin has no way to control where it loads and adds heavy assets site-wide, that is a strong signal to look for a leaner replacement.

Plugins worth auditing first: slider plugins, contact form plugins, social sharing plugins, chat widget plugins, popup plugins. These most commonly load assets on every page by default.

Step 7: Reduce External Font Requests

Every Google Fonts declaration adds a DNS lookup, a connection request, and a font file download before your text can render. On a clean page, this can add 100 to 300ms to first visible text.

Option 1: Host fonts locally

Download your Google Font files from google-webfonts-helper. This tool packages the font files with the correct CSS declarations for self-hosting. Upload the files to your server and reference them in your stylesheet instead of loading from Google's servers.

Some themes include a "local fonts" toggle that does this for you automatically. Check your theme customizer or typography settings.

Option 2: Use a system font stack

System fonts are already installed on the visitor's device. No download, no external request, no latency. They load instantly. A modern system font stack:

font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif;

This is the fastest option and produces clean readable results across all modern operating systems.

Option 3: Add font-display: swap

If you continue loading external fonts, add font-display: swap to your font-face declarations. This tells the browser to show system text immediately and swap in the web font when it finishes loading. It prevents invisible text during the font download.

Many themes expose this as a setting in the customizer. Check your typography panel.

Step 8: Clean Up the Database

A bloated database adds to server response time. Every page load runs database queries. Unnecessary rows increase the work involved.

Take a database backup before running any cleanup.

Post revisions:

Every time you save or update a post, WordPress stores a revision. A post edited frequently over several months can accumulate hundreds of revisions. Most sites do not need unlimited revision history.

To limit future revisions, add this line to wp-config.php above the line that reads /* That's all, stop editing! */:

define('WP_POST_REVISIONS', 3);

This limits each post to 3 saved revisions going forward. Existing revisions stay in the database until cleaned separately.

To remove existing revisions, you can use WP-CLI if your host provides it:

wp post delete $(wp post list --post_type=revision --posts_per_page=500 --format=ids) --force

Run this in small batches on large sites. Test on staging first.

Expired transients:

Plugins store temporary data in the database using WordPress transients. After plugins are removed or updated, expired transients can accumulate in the wp_options table.

Clean expired transients safely with WP-CLI:

wp transient delete --expired

Spam, trash, and auto-drafts:

Remove from the WordPress admin area:

• Comments > Spam > Empty Spam
• Comments > Trash > Empty Trash
• Posts > Trash > Empty Trash
• Pages > Trash > Empty Trash

Auto-draft posts accumulate if you started drafts and abandoned them. Remove them from the All Posts or All Pages list filtered by "Draft" status.

Autoloaded options:

Data stored in wp_options with autoload=yes is loaded on every single page request. Plugins sometimes leave large autoloaded records behind after deactivation.

Check the total size of your autoloaded options with this SQL query in phpMyAdmin or your host's database tool:

SELECT SUM(LENGTH(option_value)) AS total_bytes
FROM wp_options
WHERE autoload = 'yes';

If the result is above 1MB, investigate which option names contribute the most. A developer can identify and remove abandoned plugin records safely.

Step 9: Measure Again

After completing the steps that apply to your site, run PageSpeed Insights again on the same pages you tested in Step 1.

Compare:

• Performance score before and after
• LCP before and after
• TTFB before and after
• CLS before and after

Also run GTmetrix again. Compare the number of requests, total page weight, and which scripts still appear in the waterfall.

A clean set of changes (compressed images, host-level caching enabled, one fewer remote font request) can produce a 10 to 30 point score improvement without adding any optimization plugin.

If This Does Not Work

TTFB is still slow after addressing hosting. If you are on shared hosting and cannot move to a managed plan, full-page caching (via Cloudflare or a caching plugin) reduces the number of PHP and database executions per request. This is the most practical option until a hosting upgrade is possible.

LCP element is a CSS background image, not an HTML img tag. CSS background images cannot receive loading="lazy" or standard lazy loading treatment. A developer can add fetchpriority="high" to the correct element, or restructure the hero section to use an HTML img tag with the correct priority hint.

CLS is high and does not respond to image fixes. Check: late-loading ads or embeds that do not reserve layout space, web fonts swapping in visibly after text appears, and elements that shift when JavaScript loads. Each has a specific targeted fix.

All these steps are done and the score is still under 70. The remaining problem is likely a specific slow plugin. Use the guide to finding which plugin is slowing down your site to isolate it systematically.

Common Mistakes to Avoid

• Installing multiple caching or optimization plugins. Two caching layers often create stale content and make debugging harder, not faster. Choose one layer: host-level caching or a plugin, not both.
• Optimizing without a baseline. Without a before score, you cannot confirm whether a change helped or hurt. Always record before and after.
• Treating the PageSpeed score as the only metric. The score is a lab simulation. The "Field Data" section of the same PageSpeed report shows real visitor experience from the Chrome UX Report. Both matter.
• Loading Google Fonts without font-display: swap. Text is invisible until the font loads. This hurts user experience and FCP.
• Skipping the revision limit. The wp-config.php setting only limits future revisions. Without it, the count grows indefinitely with every post edit.
• Running database cleanup without a backup. Cleanup queries are irreversible. Always back up first.
• Removing a plugin without checking what data it stores. Plugins that handle forms, bookings, or orders store business data. Review what is in the database before a full removal.

When to Ask for Help

Stop and contact a developer or your host's support team when:

• TTFB stays above 2 seconds after moving to a managed hosting plan.
• Updating the PHP version causes white screens or errors you cannot trace to a specific plugin.
• The database autoloaded data is above 3MB and you cannot identify what is causing it.
• The LCP element is inside a complex page builder template and cannot be addressed without code changes.
• Your site handles live transactions (bookings, payments, subscriptions) and requires zero downtime during testing or changes.

For performance issues that survive these steps, server-level tools such as New Relic or your hosting provider's APM dashboard can identify bottlenecks invisible at the WordPress admin layer.

Final Checklist

• Baseline PageSpeed score recorded (LCP, INP, CLS, TTFB all noted)
• PHP version checked and updated to 8.1 or higher if needed
• Images compressed and converted to WebP before upload
• Hero or featured image under 200KB at intended display size
• Explicit width and height on all images in the editor
• Host-level caching confirmed or Cloudflare added (or one caching plugin if neither is available)
• Theme audited for unnecessary stylesheets, icon fonts, and remote font requests
• Plugin assets scoped to pages where plugins are actually active
• Google Fonts replaced with locally hosted fonts or a system font stack
• Post revision limit set in wp-config.php
• Expired transients, spam, and trash emptied
• Autoloaded options size checked; any large abandoned records identified
• Final PageSpeed score recorded and compared to baseline

For ongoing performance upkeep, database cleanup and speed checks belong in your regular maintenance routine. The WordPress website maintenance checklist covers these as recurring tasks alongside backups, updates, and security checks.

If the score still lags after all these steps and you suspect plugin stack overlap is part of the problem, the WordPress plugin stack audit guide helps you evaluate load, overlap, and maintenance risk across your active plugins.