Speeding Up a Slow WordPress Site: A Non-Technical Checklist

A slow WordPress site is rarely one problem. It is usually five small problems stacked on top of each other: bloated images, a dozen plugins nobody remembers installing, cheap hosting, and a page builder rendering more code than the page needs. This checklist walks through diagnosis first, then fixes in the order that actually moves the needle, so you are not spending money on the wrong thing first.

Step one: diagnose before you touch anything

Guessing at what is slow wastes both time and developer hours. Run these two free tools before changing a single setting.

PageSpeed Insights (pagespeed.web.dev) gives you a 0 to 100 score for mobile and desktop, plus the three Core Web Vitals that matter most for both user experience and Google's ranking signals.

• Largest Contentful Paint (LCP): how long it takes the biggest visible element, usually a hero image or headline, to fully load. Under 2.5 seconds is good, over 4 seconds is a real problem.
• Interaction to Next Paint (INP): how quickly the page responds when someone clicks or taps something. Under 200 milliseconds is good, over 500 milliseconds feels sluggish to a visitor.
• Cumulative Layout Shift (CLS): how much content jumps around as the page loads. Under 0.1 is good. This is the "I was about to click and the button moved" problem.

GTmetrix adds a waterfall chart showing exactly which files are slowing the page down, which is more useful than PageSpeed Insights once you know something is wrong and need to find what.

Run both tools on your homepage and your two or three highest-traffic inner pages, since performance often varies wildly by page depending on what plugins and content blocks are loaded there. Write down the scores. You will want a before and after comparison once you start fixing things.

The fix list, in order of impact

Not all fixes are equal. Fixing hosting before fixing images is like replacing the engine before checking if there is air in the tires. Work through this list roughly in order.

1. Hosting quality

Expected improvement: often the single biggest jump, sometimes cutting load time by half on its own. DIY or developer: DIY to switch plans with your current host, developer recommended for a full migration to a new host. Rough cost: $25 to $150/month for managed WordPress hosting, plus $150 to $500 for a one-time migration if changing providers.

Shared hosting plans throttle CPU and memory the moment your traffic or plugin count grows past what the plan was priced for. If your site is on a $5 to $10/month shared plan and is genuinely slow, this is very likely the root cause, not a symptom you can plugin your way out of.

2. Image sizes and formats

Expected improvement: typically 20 to 40 percent reduction in page weight, often the biggest LCP improvement after hosting. DIY or developer: DIY with a plugin. Rough cost: free to $10/month for a compression plugin like ShortPixel or Imagify.

Uploading camera-resolution or full-size stock photos directly into WordPress is the most common cause of slow load times on content-heavy sites. Convert images to WebP or AVIF format, resize them to the actual display dimensions before upload, and enable lazy loading for anything below the fold.

3. Plugin audit and removal

Expected improvement: 10 to 30 percent improvement, plus fewer security and conflict risks. DIY or developer: DIY for identifying and deactivating, developer recommended if functionality depends on the plugin being removed. Rough cost: free, or a few hours of developer time if replacing a removed plugin's function with custom code.

Deactivate every plugin, then reactivate one at a time while checking load times. Anything you cannot explain the purpose of, anything duplicated (two SEO plugins, two caching plugins), and anything not updated in over two years should be a candidate for removal. Fifteen or more active plugins on a small business site is usually a sign of accumulated bloat rather than actual need.

4. Caching

Expected improvement: can cut server response time dramatically for repeat visitors, often the fastest win for the effort involved. DIY or developer: DIY with a plugin like WP Rocket or W3 Total Cache. Rough cost: $0 to $60/year for the plugin, often included with managed hosting.

Without caching, WordPress rebuilds every page from the database on every single visit. A caching plugin generates static versions of pages so repeat visits and most first visits load from a saved copy instead. If your managed host includes server-level caching, a plugin can sometimes conflict with it, so check with your host before installing one.

5. Database cleanup

Expected improvement: modest on its own, 5 to 15 percent, but compounds with caching. DIY or developer: DIY with a plugin like WP-Optimize. Rough cost: free to $50/year.

Years of post revisions, spam comments, and abandoned draft content bloat the database, slowing down every query the site makes. Clean this out quarterly rather than as a one-time fix.

6. Fonts

Expected improvement: modest but helps INP and reduces render blocking. DIY or developer: developer recommended. Rough cost: $150 to $600 for a developer to self-host and optimize font loading.

Loading five weights of two different Google Fonts from an external server adds render-blocking requests before any text can appear. Self-hosting fonts and trimming down to the two or three weights actually used in the design removes this delay.

7. Render blocking scripts

Expected improvement: meaningful improvement to LCP and INP, harder to quantify without testing. DIY or developer: developer recommended, some caching plugins offer a DIY toggle. Rough cost: included in a $500 to $2,000 performance optimization engagement, or free as a setting in WP Rocket.

Scripts loaded in the page head before content, tracking pixels, chat widgets, and some analytics tools, block the browser from rendering the page until they finish loading. Deferring or delaying non-critical scripts until after the page paints is a targeted, technical fix best handled by someone comfortable testing that nothing breaks.

8. Page builder bloat

Expected improvement: can be substantial, 20 to 50 percent, but requires rebuilding pages. DIY or developer: developer recommended. Rough cost: $1,500 to $6,000 depending on page count, as part of rebuilding key templates.

Elementor, Divi, and similar builders generate significantly more HTML and CSS than a hand-coded or block-editor page for the same visual result. On a site where speed genuinely matters, converting high-traffic pages like the homepage and top landing pages away from a heavy builder is one of the more disruptive but effective fixes.

9. CDN

Expected improvement: noticeable for visitors far from your server, minimal if your audience is regional and your host is already close to them. DIY or developer: DIY setup, developer recommended for advanced rules. Rough cost: free (Cloudflare free tier) to $20 to $200/month for premium tiers.

A content delivery network serves static assets like images, CSS, and JavaScript from servers physically closer to each visitor, which matters more for a business with a national or international audience than a purely local one.

When the site is beyond optimization

Sometimes the honest answer is that the site needs a rebuild, not another round of fixes. Signs it is time to stop optimizing and start over: the site is running on a theme or framework that was abandoned by its developer years ago, it has been rebuilt piecemeal by three different freelancers with conflicting approaches, the page builder is so deeply embedded that removing it would mean recreating every page from scratch anyway, or you have already spent $2,000 to $3,000 on optimization work and gained less than a 20 percent improvement.

At that point, a properly scoped WordPress development rebuild on a lean, modern foundation, paired with digital marketing work to make sure the faster site actually converts better, is usually the more cost-effective path than continuing to patch an aging structure. You can see examples of this kind of turnaround in our case studies.

FAQ

How fast should my WordPress site actually load?

Aim for under 2.5 seconds for Largest Contentful Paint on mobile, since that is the threshold Google treats as "good" and it roughly matches what most visitors will tolerate before bouncing. Desktop can often load faster with the same setup, and most business sites we test land between 1.5 and 4 seconds before optimization.

Will a caching plugin fix a slow site on its own?

Sometimes it helps significantly, but caching cannot fix a site slowed down by bloated images, poor hosting, or an excessive number of plugins. Treat it as one fix among several rather than a single solution.

How much should I expect to pay for a full performance optimization pass?

A thorough pass covering hosting review, image optimization, plugin audit, caching, and script cleanup typically runs $800 to $3,000 depending on site size and how much custom work is needed, versus $150 to $600 for a lighter DIY-plus-plugin approach.

Can I do all of this myself without hiring a developer?

Steps one through six on this list are genuinely DIY-friendly with the right plugins and about a weekend of focused work. Fonts, render blocking scripts, and page builder changes carry real risk of breaking the site's layout, so those are worth a developer's time even on a tight budget.

If you have run the diagnostics and are not sure which fixes are worth paying for, book a free 1-hour strategy call through our contact page and we will tell you honestly where the time and money should go.