How to Move from LiteSpeed Cache to FastPixel (The Easy Way)

Switching performance plugins sounds like the kind of thing that ruins an already bad day.

Cache conflicts. Critical CSS regenerating endlessly. Settings to map across, exclusions to remember, page speed fluctuating for a few hours while everything settles. That’s the usual fear with plugin migrations.

This one is different.

The migration itself is simple: clear LiteSpeed’s cache, check whether you use QUIC.cloud, deactivate LiteSpeed Cache, activate FastPixel, choose the Fast preset, and you’re done. There’s no settings export, no JSON file to import, no migration assistant to run.

FastPixel works on presets, so once it’s active, it configures everything automatically and starts optimizing.

This guide walks through the steps in detail, what to expect after the switch, and the handful of small things worth checking once you’re on the other side.

Why people consider the switch

LiteSpeed Cache is a capable plugin with a huge install base, and if your site is on a LiteSpeed server and everything is humming along, the results can sometimes be good.

People usually look at FastPixel when they want a simpler approach, better Core Web Vitals, more speed or independence from a specific server stack.

LiteSpeed Cache is tightly coupled to LiteSpeed and OpenLiteSpeed servers. Its exclusive features, including server-level page caching, ESI, private cache for logged-in users, and advanced purge rules, only work when the site runs on LiteSpeed-powered hosting.

Move to a host running Nginx or Apache without LiteSpeed and you lose the core of what makes the plugin fast. The page optimization features still work, but you’re then relying mostly on QUIC.cloud’s online services rather than the server cache.

FastPixel processes everything in the cloud, regardless of what your host runs. Pages are cached and optimized in FastPixel’s infrastructure along with the images, CSS, JS and fonts and everything is delivered via CDN. Your hosting handles less, and you’re not tied to any particular server stack.

There’s also a difference in how the two are configured. LiteSpeed Cache exposes a deep settings panel, with dozens of tabs covering cache, CDN, image optimization, page optimization, crawler, ESI, toolbox, and more.

The flexibility is real, but so is the time it takes to get a configuration that actually performs well. Guides for “the ideal LiteSpeed Cache settings” run thousands of words for a reason.

FastPixel bundles image optimization (powered by ShortPixel), CDN delivery, Critical CSS, font optimization, and page caching into a single plugin on every plan, including the free one. You can configure things manually or you can choose a preset which will configure everything for you.

FastPixel currently shows leading real-world results among the best WordPress performance plugins, according to the HTTP Archive Core Web Vitals Technology Report. The report compares the percentage of origins passing Core Web Vitals across LCP, INP, and CLS. That’s worth a look if you’re weighing the move.

Before you start

Two minutes of prep saves you the only realistic source of friction during the switch.

Note any custom exclusions in LiteSpeed Cache. If you’ve added specific URLs, scripts, or CSS files to LiteSpeed’s exclusion lists, or made changes to the Tuning and Toolbox tabs, note them down. You probably won’t need them, since FastPixel handles most exclusion cases automatically. But it’s useful to have the list in case something specific needs adjusting later.

Back up your .htaccess file. LiteSpeed Cache writes its own rules into .htaccess. Having a backup makes it easy to clean up the leftover # BEGIN LSCACHE block if it stays behind after uninstall.

Know your starting numbers. Run your site through PageSpeed Insights and save the scores. This gives you a clean before/after comparison once FastPixel is running.

That’s it. No settings to export, no migration file to import, no compatibility checklist to work through.

The actual migration

Six short steps, maybe 2 minutes if you’re not in a rush.

Step 1: Clear LiteSpeed’s cache

Open the LiteSpeed Cache dashboard, go to Toolbox, and run Purge All. If you use QUIC.cloud services like Critical CSS or Unique CSS, those have their own purge options in the same area. You can skip purging them if you plan to disconnect QUIC.cloud in the next step.

This gives you a clean handoff and avoids any confusion between old cached files and the new optimized version FastPixel will generate.

Step 2: Review your QUIC.cloud connection

If you’ve never set up QUIC.cloud or only used LiteSpeed Cache for local server caching, you can skip this step entirely.

If you do use QUIC.cloud services like Image Optimization, Critical CSS, or the CDN, it’s worth reviewing the connection before deactivating the plugin. Under LiteSpeed Cache > General, you’ll see your domain key and any active services. Disconnecting before removal keeps things tidy and avoids leaving unused services connected to your site.

If you are using QUIC.cloud CDN and your DNS is pointed to QUIC.cloud’s nameservers, update your DNS or CDN setup before deactivating LiteSpeed Cache, so traffic continues to reach your site. If you only used LiteSpeed Cache locally, you can skip this part.

Step 3: Deactivate LiteSpeed Cache

Go to Plugins > Installed Plugins, find LiteSpeed Cache, and click Deactivate.

You don’t need to delete it immediately. Keeping it installed but inactive for a day or two gives you an easy rollback option while you test FastPixel. Once you’re sure you’re staying with FastPixel, you can delete the plugin. If you notice a leftover # BEGIN LSCACHE block in your .htaccess file, you can remove it after confirming LiteSpeed Cache is no longer active.

Step 4: Install and activate FastPixel

From Plugins > Add New, search for FastPixel, install the plugin, and activate it.

You’ll be prompted to connect to a FastPixel account. The free plan covers the full optimization stack, within the free plan limits: CDN, image optimization, Critical CSS, and page caching. You can complete the migration without a paid plan.

Paid plans are available for higher pageview volumes, while the core optimization features are also available on the free plan.

Step 5: Choose a preset

FastPixel offers three presets: Safe, Balanced, and Fast.

The Fast preset is generally the best preset for performance and Core Web Vitals. Once you choose it, FastPixel configures all the settings automatically for the best performance possible.

That’s the configuration step done. No tab-by-tab review, no toggles to second-guess.

Step 6: Let FastPixel process your pages

FastPixel adds your primary pages to the optimization queue and optimizes the other pages as they’re visited. On the unoptimized pages the first request may trigger processing, while later visitors receive the optimized version instantly.

What’s included out of the box

One of the practical differences after the switch is that you don’t need to manage QUIC.cloud quotas, domain keys, or a separate CDN setup. The full optimization stack ships in the box:

• Page caching, through FastPixel’s cloud infrastructure
• CSS Critique, generated per page and updated when content changes
• CSS and JavaScript optimization, including minification and deferral
• Optimisation des images through ShortPixel’s cloud, with WebP conversion and delivery
• LCP image preloading, so above-the-fold images load with priority
• Font optimization, including font-display handling
• CDN delivery, for CSS, JS, images, and fonts

If your host offers Redis or Memcached, FastPixel also supports Object Cache for an extra boost on dynamic sites like WooCommerce stores or membership areas.

After the switch: what to check

Make sure your pages have the green Cached status in the FastPixel Dashboard.

Run PageSpeed Insights again. Compare to your starting numbers. You’re looking for improved LCP, similar or better CLS, and fewer “opportunities” in the report.

Spot-check key pages visually. Open your homepage, a blog post, your most important landing page, and a checkout or contact page if you have one. Just a quick look to make sure that everything looks good.

Check your .htaccess if needed. If you removed LiteSpeed Cache entirely and notice a leftover # BEGIN LSCACHE section in .htaccess, you can remove it for a cleaner setup. Leaving it in place won’t usually cause issues on a non-LiteSpeed server.

Check the FastPixel dashboard. It shows which pages have been optimized and surfaces any pages that need attention. If something specific isn’t optimizing the way you expect, you’ll see it here.

What changes for your workflow

After the migration, there’s not much to do.

FastPixel doesn’t require ongoing tuning. When you publish new content, it gets optimized automatically. When you update a page, the cache invalidates and regenerates without you doing anything. There’s no domain key to renew, no QUIC.cloud quota to monitor, no settings panel to revisit every few months when a new option appears.

For many users, that’s the quieter benefit of the switch. Better Core Web Vitals are nice, but spending less time thinking about your performance plugin is often what makes it stick.

FAQs

Can I run LiteSpeed Cache and FastPixel at the same time?

No, that would not work. Two caching plugins running in parallel will conflict, double-process your assets, and likely produce worse performance than either one alone. Deactivate LiteSpeed Cache before activating FastPixel. If you want to test FastPixel without committing fully, use a staging site.

Do I need to be on LiteSpeed hosting to use FastPixel?

No. FastPixel works on any host: LiteSpeed, Nginx, Apache, managed WordPress hosting, shared hosting, anything. That’s actually one of the reasons people switch. With LiteSpeed Cache, the most powerful features depend on running on a LiteSpeed server, so if you ever change hosts you may lose them. FastPixel doesn’t have that dependency.

Will FastPixel replace LiteSpeed Cache image optimization too?

Yes. FastPixel includes image optimization powered by ShortPixel, with WebP conversion and CDN delivery built in, so you don’t need LiteSpeed Cache’s image optimization or QUIC.cloud’s image services after switching. Everything happens automatically in the cloud, with no domain key to manage or queue to monitor.

Do I need to manually migrate my LiteSpeed Cache settings to FastPixel?

No. The two plugins are configured very differently. LiteSpeed Cache has dozens of granular settings across multiple tabs, while FastPixel uses presets designed to cover the configurations most sites need without manual tweaking. That’s the main reason people choose it.