How I Speed Up Every WordPress Site: My Exact Step-by-Step Checklist

The worst WordPress site I ever had to optimize was loading in a painful 10 to 12 seconds.

It had a heavy theme, 40+ plugins, and weak hosting. The previous developer had clearly just kept adding features without ever checking the impact on server performance. By the time it reached my desk at CubeCod Technologies, the site was virtually unusable on mobile devices.

After running it through my full optimization pipeline which I am going to share with you today that exact same site came down to a 4 to 5-second load time. The Google PageSpeed score jumped from a failing 20 to a solid 85-95. That is roughly a 70% performance improvement, and it came from following the exact same checklist I use on every single WordPress deployment I touch.

This isn’t generic advice. This is my exact operational process, in the exact order I execute it.

Why Order Matters More Than People Think

Before getting into the steps, I want to address a major flaw that most speed optimization guides get completely wrong.

Most tutorials tell you to jump straight to caching plugins and image compression. While those things matter, if you do them before checking your hosting infrastructure, you are building on a broken foundation. I have personally optimized images, deployed a CDN, minified CSS/JS, and done everything right only to find the site was still slow.

The reason? The server response time was terrible. Weak hosting is a fundamental bottleneck, and no amount of front-end optimization will fix a struggling server.

The order of this checklist is not random. It is engineered to produce actual, measurable results.

Step 1: First, Check Your Hosting (TTFB)

This is the step almost everyone skips, yet it is the most critical.

To check if your hosting is the bottleneck, look at your TTFB (Time To First Byte). You can find this metric using GTmetrix or Google PageSpeed Insights. TTFB tells you exactly how long it takes for the server to start responding after a browser requests your site.

If your TTFB is consistently above 600ms to 1 second even after basic optimization, your hosting is weak. At that point, it doesn’t matter how well you compress images or set up caching; the server itself is the problem, and the site will remain slow until you migrate.

Cheap shared hosting providers often pack thousands of websites onto a single server and spend very little on maintenance. At CubeCod, I’ve seen this cause severe client issues: slow response times, frequent downtime, and security vulnerabilities. Good hosting costs a bit more, but it is the single biggest factor in your site’s speed ceiling.

Once I confirm the hosting is acceptable, I move forward to the front-end.

Step 2: Audit Your Plugins Without Mercy

Before touching caching or code, I audit every installed plugin one by one. I am specifically hunting for four things:

1. Inactive plugins just sitting in the directory.

2. Duplicate plugins doing the same job (e.g., two caching plugins or two SEO plugins).

3. Plugins with heavy scripts loading on every single page.

4. Plugins that haven’t been updated in over six months.

Every plugin adds backend overhead. Even deactivated ones take up database space. Active plugins that aren’t optimized silently load CSS and JavaScript on pages where they aren’t even being used, dragging down your global load time.

My golden rule: If a plugin’s function can be replaced with 5 to 10 lines of custom PHP in the functions.php file, I remove the plugin and write the code myself. I keep only the lightest options available and delete duplicates without mercy.

This step alone yields a visible speed boost on almost every site I audit.

Step 3: Check The Theme Architecture

Not all themes are engineered equally. Some themes look beautiful but load dozens of unnecessary CSS files, bloated JavaScript libraries, and features you will never use all executing on every single page load.

Lightweight themes, on the other hand, load only what the specific page requires. The result is that the exact same content on a lightweight theme can load in 1 to 2 seconds, while a bloated theme might take 4 to 5 seconds.

When I review a theme, I check its script payload and whether its built-in features could be handled more efficiently by an isolated plugin. If the theme is the root problem and the client is open to a redesign, migrating to a lightweight framework is often the biggest performance leap I can make.

Step 4: Optimize The Images (WebP & Lazy Loading)

Images are usually the largest files on any WordPress page. Unoptimized media is the most common reason websites fail Core Web Vitals.

My process here has two phases: fixing existing media and establishing a rule for new uploads.

1. Compress Existing Media: I identify the heaviest files using GTmetrix or Chrome DevTools. Then, I compress them using tools like TinyPNG or ShortPixel. These tools reduce file size drastically without noticeable quality loss.

2. Convert to WebP: I convert images to WebP format wherever possible. WebP files are typically 20% to 50% smaller than standard JPGs or PNGs at the same visual quality. Since almost every modern browser supports WebP, there is no excuse not to use it. My rule is simple: any new image uploaded to a site must be WebP by default.

3. Enable Lazy Loading: This ensures that images below the fold (outside the visible screen area) do not load until the user actually scrolls down to them. This drastically speeds up the initial page render. Plugins like WP Rocket or native WordPress features handle this seamlessly.

Step 5: Setup Page & Browser Caching

Caching sounds highly technical, but its function is straightforward.

Without caching, every time someone visits a page, the WordPress server has to build that page from scratch pulling data from the database, executing PHP, and assembling the HTML. With caching, a static, ready-made version of the page is saved and served instantly.

There are two primary types of caching you must deploy:

• Browser Caching: Saves static files (logos, CSS) on the visitor’s device so that when they navigate to another page, those files don’t need to be downloaded again.

• Server/Page Caching: Saves a pre-built HTML version of your pages on the server itself.

I typically use WP Rocket or W3 Total Cache to enable page caching, browser caching, and file minification all at once. After enabling it, I always run a speed test to confirm the site hasn’t broken visually.

Note: Whenever you make design changes that don’t appear on the live site, always clear your cache first.

Step 6: CSS and JavaScript Minification

Every CSS and JS file contains spaces, line breaks, and comments that make the code readable for human developers but add unnecessary weight for browsers. Minification strips out all that extra formatting, making the files smaller and faster to execute.

This is easily handled by caching plugins like WP Rocket or Autoptimize. Enable the option, but test immediately afterward aggressive JS minification can sometimes break interactive site features (like sliders or mobile menus).

Additionally, I defer render-blocking JavaScript. This forces the browser to load the visible page content first and execute heavy scripts afterward, making the site feel much faster to the end-user.

Step 7: Clean Up The Database

Over time, a WordPress database accumulates massive amounts of junk: old post revisions, spam comments in the trash, orphaned data from deleted plugins, and expired temporary data (transients).

None of this is useful, but it bloats your database and slows down query execution times.

I use Advanced Database Cleaner to remove excessive post revisions, clear trashed comments, drop orphaned tables, and wipe expired transients. On older sites with active blogs, this single step can free up hundreds of megabytes of dead database weight.

Step 8: Deploy a Global CDN

A Content Delivery Network (CDN) stores copies of your site’s static assets on edge servers located around the world. When someone visits your site, they download the heavy files from the server geographically closest to them, rather than your main hosting server.

I use Cloudflare for most deployments because the DNS setup is straightforward, it offers excellent caching rules, and the base security features are unmatched. For premium client projects where performance is the absolute priority, I deploy Bunny.net.

Adding a CDN consistently yields a 20% to 50% speed improvement for global traffic, especially for visitors geographically distant from your origin server.

Step 9: Final Testing and Verification

Once the checklist is complete, I run a final, comprehensive speed test using both GTmetrix and Google PageSpeed Insights.

I check the load time, the TTFB, and the Largest Contentful Paint (LCP). If a tool flags a remaining issue, I trace it back through the checklist logically rather than guessing at random fixes. This final verification gives clients a clear before-and-after data report, which is vital when providing optimization as a professional agency service.

What Kind of Improvement Can You Realistically Expect?

On a poorly optimized site, executing this exact checklist typically produces a 40% to 80% speed improvement. A site loading in 10 seconds can realistically drop to 2 seconds, depending heavily on the origin hosting quality.

On average projects with decent hosting and a reasonable theme, a 50% performance leap is the standard expectation. The exact numbers depend entirely on the initial diagnosis. You cannot optimize what you haven’t correctly diagnosed.

The One Thing People Get Wrong After Optimization

Speed optimization is not a one-time job.

Clients frequently ask me, “Once we’ve optimized the site, is it done forever?”

The honest answer is No. New images get uploaded without compression. New plugins get installed. Core updates shift performance metrics. Databases naturally bloat over time.

My recommendation is a strict monthly maintenance checkup. Run a speed test, audit for unnecessary plugins, optimize new media, clear the cache, and sweep the database. This takes roughly one hour per month and keeps the architecture running exactly how it should.

If you are about to optimize a WordPress site, follow this checklist in this exact order. Start with your hosting TTFB. Everything else builds on that foundation. Skip it, and you will spend hours compressing images only to wonder why the site still feels sluggish.