Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud Bangladesh India Best hosting in Bangladesh
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector
Deals Guides Speed up WordPress How we test

Guide · Updated November 2026

How to speed up WordPress

WPLegible editors9 min read

Speed work on WordPress is a sequence, not a plugin haul. Change one layer, measure, then decide if the next layer is worth it. Take a backup first — the backup list is the prequel to this page.

We do not publish millisecond tables yet. “Testing in progress” on product profiles means exactly that. The steps below are the ones that hold up without a lab number attached.

1. Measure the page you actually care about

Run the homepage and one slow template (a product, a long post) through your own WebPageTest or Chrome Lighthouse, from a location near your readers. Write down TTFB and LCP. If TTFB is most of LCP, you have a server or cache problem. If TTFB is fine and LCP is not, you have an image, font or CSS problem. Buying a new cache plugin will not fix the second one.

2. Put the site near the readers

A US shared server serving Dhaka will lose before any plugin runs. Pick a published region in India or Southeast Asia for a Bangladesh audience, or an edge cache if the pages are anonymous. The Bangladesh hosting list is that decision. The hosting finder asks for audience location on purpose.

3. Use one page cache, and the one your server understands

On LiteSpeed (common on Hostinger and several budget hosts), use LiteSpeed Cache and do not add WP Rocket. On Nginx or Apache without LiteSpeed, WP Rocket or FlyingPress is the paid path, and WP Super Cache is the plain free path for a simple blog. Two page caches fighting over the same HTML is a common reason a “faster” site gets slower and starts serving stale carts.

Exclude cart, checkout and account pages. WooCommerce will tell you, in lost orders, if you did not.

4. Compress images once

Pick ShortPixel, Imagify or Smush. Not all three. Convert to WebP or AVIF, stop uploading 4000-pixel camera originals into a 800-pixel column, and lazy-load below the fold. The hero image should not be lazy-loaded; that is an LCP own-goal.

5. Remove plugins that run on every page

Related posts, chat bubbles, share buttons, slider scripts and unused Jetpack modules are more expensive than they look. The stack builder is a ceiling: one SEO plugin, one cache plugin, one security plugin, one backup plugin, one forms plugin. If you have two in any of those jobs, delete one. SEO plugins in particular — Rank Math and Yoast together — duplicate meta tags. See Rank Math vs Yoast and keep one.

6. Check PHP and the theme before you buy another add-on

A current PHP version supported by your plugins is the boring win. A heavy theme or an Elementor page with five nested sections is the next one. GeneratePress, Kadence or Bricks are the direction if the theme is the weight. Rebuilding in a new builder is a project, not a Saturday toggle — back up, stage, then move.

7. A CDN is for distance, not for a broken origin

If TTFB is bad even from a test location next to the server, a CDN will not repair PHP. If TTFB is fine nearby and bad from another continent, a CDN (or Rocket.net’s edge setup, or the host’s built-in CDN) is the right tool. Do not stack a CDN plugin, a cache plugin’s CDN and Cloudflare’s orange cloud without knowing which one is the cache.

8. Stop when the template is fast enough

Chasing a perfect lab score with critical CSS generators and delayed JavaScript usually breaks a form or a checkout. Ship the region, the single cache, the image pass and the plugin diet. Re-measure. Only then look at font hosting and script delay.

A safe order for this afternoon

  1. Backup with a plugin from the backup list, stored off the server.
  2. Note TTFB and LCP for the homepage and one inner template.
  3. Confirm the server region in the host panel.
  4. Turn on one cache. Remove any other page cache.
  5. Compress the media library with one image plugin.
  6. Deactivate plugins you cannot explain. Re-test the contact form and, if you have one, checkout.

If the site is on an entry shared plan and TTFB stays high with caching on, the next purchase is hosting, not another plugin. Start with the hosting directory.

FAQ

What is the fastest WordPress host?

We have not published that lab result. Start with a server region near your readers and one cache plugin, then measure your own templates.

Which cache plugin should I install?

LiteSpeed Cache on LiteSpeed servers. One paid cache such as WP Rocket or FlyingPress otherwise. Never two page caches.