WordPress caching plugins compared: LiteSpeed Cache, WP Rocket and more (2026)

What a caching plugin does

Every time someone opens a WordPress page, the server runs PHP code and asks the database for the content, then builds the page. A caching plugin saves the finished page and hands that copy to the next visitor, so the server skips most of the work. WP Super Cache’s plugin page puts it simply: “This plugin generates static html files from your dynamic WordPress blog.”

Caching is one of three levers for a fast WordPress site. The other two are images and where your files are served from (a CDN). We build on WordPress every week, and the order we’d fix things in is hosting first, then images, then caching. A caching plugin can’t rescue a slow server or a 5 MB photo.

Before you install anything, run your key pages through Google PageSpeed Insights and note the scores and Core Web Vitals. You’ll want a before-and-after.

First, check what your host already does

Some hosts cache pages for you, and a few block caching plugins because they clash with the host’s own system:

• SiteGround lists “Multilevel caching” on its plans and says its Speed Optimizer plugin handles “caching and compression automatically,” per its hosting page.
• Hostinger says it uses “LiteSpeed servers and smart caching,” per its WordPress hosting page. That makes LiteSpeed Cache the natural fit there.
• WP Engine lists W3 Total Cache, WP Super Cache and several other caching plugins as disallowed, saying such plugins “conflict with our platform’s built-in caching structure,” per its disallowed plugins page.

If your host has built-in page caching, adding a second page cache on top usually adds problems, not speed. Ask your host which plugin, if any, it recommends. Our web hosting hub covers the hosts’ plans and renewal prices.

Caching plugins compared

The biggest difference isn’t features. It’s which server each one needs.

How to find out which server you’re on

Three quick ways, easiest first:

1. Read your plan page or help center. Hosts that run LiteSpeed tend to say so, as Hostinger does.
2. Look in WordPress. Go to Tools, Site Health, then the Info tab, and open the Server section. It shows the web server software your site reports, such as Apache, Nginx or LiteSpeed.
3. Ask support. Ask two questions: which web server do you run, and do you cache pages at the server level?

The answer decides most of this page. LiteSpeed server: LiteSpeed Cache. Host-level caching: maybe nothing. Neither: pick from the other three.

LiteSpeed Cache

LiteSpeed Cache is free, with 7+ million active installs. Its main feature, server-level page caching, needs a LiteSpeed server. The plugin page says “LiteSpeed Exclusive Features require one of the following: OpenLiteSpeed, commercial LiteSpeed products,” LiteSpeed-powered hosting or the QUIC.cloud CDN. On an Apache or Nginx host, you lose that page cache.

Some parts work anywhere. Image optimization, CSS and JavaScript minification, and database cleanup “do not require the use of a LiteSpeed web server,” per the same page. Some QUIC.cloud services, such as its CDN and image optimization, “require payment at certain usage levels,” with prices in your QUIC.cloud dashboard.

Right for: anyone on a LiteSpeed host. It’s free and built for that server.

WP Rocket

WP Rocket is a paid option that works on most hosts. Its pricing page shows Single (1 site) at $3.49 a month, Plus (3 sites) at $6.99 and Multi at $17.49, each marked 30% off ($5, $10 and $25 before the discount). The page has a 1-year and 3-year switch and the note “Billed yearly. Billed upfront for the first 3 years,” while the FAQ says “All our Licenses are valid for 12 months” and renew every year by default. Neither page prints the checkout total or the later renewal price, so check the total before you pay.

There’s no free version. The FAQ offers a full refund within 14 days, and says that if your license lapses, “The latest version of WP Rocket released at this point will continue to operate,” but updates and support stop.

Right for: owners who want good results with few settings, on a host that isn’t LiteSpeed and doesn’t block it.

W3 Total Cache

W3 Total Cache, from BoldGrid, has 900,000+ active installs. The free version covers page, object and database caching, minification, lazy loading and CDN links, per its plugin page. Pro costs $99 a year for 1 site, $350 for 5 or $500 for 10, per BoldGrid’s page, and “Each WordPress installation needs a unique W3 Total Cache license.”

Right for: people who like to tune settings and test. The number of options is the strength and the risk.

WP Super Cache

WP Super Cache is free, made by Automattic, with 1+ million active installs. It saves static HTML copies of pages for visitors who aren’t logged in. Simple mode is the recommended setting for most sites; Expert mode is faster but uses Apache rewrite rules that are easier to get wrong.

Right for: simple blogs and brochure sites that want a free cache with few choices.

Cloudflare APO

Cloudflare’s Automatic Platform Optimization “allows Cloudflare to serve your entire WordPress site from its edge network,” per its docs. It needs the Cloudflare for WordPress plugin. On Cloudflare’s plans page, APO costs $5 a month on the Free plan and is included with Pro ($20 a month billed annually, $25 billed monthly) and higher.

Right for: sites with visitors across the country or abroad, already using Cloudflare DNS. It can sit alongside a host cache or a caching plugin.

What caching won’t fix

Page caching helps most for visitors who aren’t logged in, viewing pages that look the same for everyone. It helps much less with:

• Logged-in users, carts and checkouts, which are personal to each visitor and usually skip the page cache.
• Third-party scripts such as chat widgets, ad tags, video embeds and tracking pixels, which load from other companies’ servers.
• Heavy themes and page builders that send a lot of code to every page.
• Slow hosting, which shows up as a slow first response even before the page starts to draw.

If PageSpeed Insights flags scripts or large images after caching is on, that’s where the next gain is.

What speed costs over 3 years

Same baseline as the rest of the site: WordPress on Bluehost Starter ($3.99 x 36 = $143.64), a domain after the free first year ($36.96) and one Google Workspace inbox ($252), for $432.60 over 3 years.

The WP Rocket lines are estimates: they use the $3.49 rate for all 36 months, since WP Rocket doesn’t publish the checkout total or the renewal price. W3 Total Cache Pro assumes today’s price each year.

Images: the other half of speed

Big photos are a common reason a page fails the Largest Contentful Paint test. WordPress already helps:

• Since WordPress 5.5, images with width and height set are lazy-loaded by default, meaning off-screen images load only as the visitor scrolls (per the 5.5 announcement).
• WordPress 5.8 added WebP uploads, per the core team.
• WordPress 6.5 added AVIF, “as long as your hosting environment supports AVIF,” per the 6.5 post. Check under Tools, Site Health, Info, Media Handling.

The free habit that matters most: resize photos before upload to about the largest size they’ll display at. A plugin can compress images, but it can’t fix a phone photo uploaded at full size and shown as a thumbnail. Your theme matters too; our WordPress themes guide compares lightweight options.

Do you need a CDN?

A CDN keeps copies of your files on servers in many cities, so visitors download from somewhere close. Many hosts include one: SiteGround lists a free CDN on all plans, Bluehost lists a CDN on its shared plans, and Hostinger lists one on its plans (with “CDN included” on the higher tiers). Cloudflare’s Free plan also works as one. For a local business whose customers are nearby, a CDN helps less than good hosting and small images. For national or global traffic, it helps more.

How to set up caching safely

1. Back up first. Caching plugins write to server files such as .htaccess. See our backup plugins guide.
2. Use one page-caching plugin. Two caches fight. If your host caches pages, ask before adding a plugin.
3. Turn on the basics, then test. Start with page caching. Add minification and script delays one at a time, since they’re the settings most likely to break menus, sliders or forms.
4. Test as a visitor. Open the site in a private window. Check the contact form, cart and checkout if you have one, and log in to make sure the dashboard works.
5. Measure again. Rerun PageSpeed Insights three times and compare with your before numbers.
6. Clear the cache after changes. Edits, plugin updates and security cleanups can leave an old copy showing until you do.

Speed and security share a server, so a heavy security scanner can slow a small host. Our WordPress security guide covers the lighter options.

What to do next

• Find out if your host runs LiteSpeed or caches pages for you, then pick from the table above.
• Run a before-and-after test with PageSpeed Insights.
• Compare hosts on speed features and renewals on our web hosting hub.