Managed WordPress hosting for sites leaving A2 Hosting.
A2 runs LiteSpeed, and the caching plugin that comes with it only works on LiteSpeed. Move the site anywhere else and it becomes an inert plugin with a full settings screen.
The parts of the stack that only exist on A2.
Nothing here is A2 doing anything wrong. It is that several of their optimisations are tied to a web server you are leaving.
A cache plugin with nothing behind it
LiteSpeed Cache talks to the LiteSpeed server. On any other web server the settings screen still works, the toggles still save, and no page is ever cached.
Rewrite rules that do nothing
LSCache writes a block of directives into .htaccess. Those are read by LiteSpeed and by nothing else, so they are cleaned out rather than carried across as dead configuration.
Images it converted for you
LSCache can generate WebP versions and serve them by rewrite. Remove it carelessly and the originals are still there but the optimised versions stop being served, which shows up as a sudden jump in page weight.
The A2 Optimized plugin
It applies server-level settings and turns on other plugins on your behalf. What it actually changed is worth establishing before it is removed, because some of it is worth keeping.
A cPanel account underneath
Underneath the managed layer this is cPanel, which means addon domains, panel-level cron and mailboxes can all be attached to the same account.
Take the optimisation, leave the server it needed.
The goal is not to strip the site back to defaults. It is to keep the outcomes A2's stack produced and stop depending on the specific server that produced them.
- LSCache and its .htaccess block removed together
- WebP delivery preserved through the change
- A2 Optimized changes documented before removal
- cPanel extras enumerated
Caching that does not depend on the web server.
LiteSpeed is genuinely fast. The trap is that the speed belongs to the server, so the site gets slower the moment it runs anywhere else unless the caching is replaced deliberately.
What we change when a site arrives from A2 Hosting
Almost all of it is separating a fast site from the specific web server that made it fast.
| Setting | What we do | Why |
|---|---|---|
| LiteSpeed Cache | Removed entirely, with caching taken over in-stack | The plugin only functions against a LiteSpeed server, so on any other host it keeps a full settings interface while silently caching nothing at all. |
| Rewrite directives | The LSCache block in .htaccess cleaned out | Those directives are only interpreted by LiteSpeed, so carrying them across leaves a file full of configuration that no web server on the new host will ever read. |
| WebP delivery | Converted image serving re-established before the old one is removed | LSCache serves generated WebP files by rewrite rule, so removing it without a replacement quietly reverts every page to the heavier original images. |
| A2 Optimized | Recorded, reviewed, then removed | The plugin changes server settings and enables other plugins on your behalf, so pulling it without knowing what it did takes working configuration with it. |
| cPanel account contents | Addon domains, panel cron and mailboxes enumerated | The managed WordPress layer sits on an ordinary cPanel account, which routinely holds a second site or a mailbox that nobody remembered was there. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Can I keep using LiteSpeed Cache after moving?
Will my site get slower without LiteSpeed?
What happens to the WebP images LSCache generated?
Should I remove A2 Optimized before the migration?
I am on a Turbo plan. Does that change anything?
Keep the speed, drop the dependency.
Free migration, LiteSpeed-specific software unwound properly, and image delivery preserved.