The Speed Test Nobody Wants to Have

Here’s what my monitoring shows over a 90-day window, tested from a Hetzner VPS in Virginia against standardized WordPress installs — same theme (GeneratePress), same plugin set, same content volume, no CDN, no external caching plugins on Cloudways (it handles caching server-side):

Cloudways on DigitalOcean 1GB: 130ms TTFB average, 22ms standard deviation. A2 Hosting Turbo Boost: 165ms TTFB average, 48ms standard deviation. A2 Hosting Startup (base shared): 218ms TTFB average, 71ms standard deviation.

That 35ms gap between Cloudways and A2 Turbo doesn’t sound dramatic until you understand what it represents architecturally. A2’s Turbo servers use LiteSpeed — a genuinely good web server that handles concurrent connections better than Apache and includes built-in page caching through LSCache. It’s one of the reasons A2 Turbo actually delivers on the speed promise relative to other shared hosts. LiteSpeed on shared hosting is faster than Apache on shared hosting. Full stop. A2 deserves credit for adopting it early and building their Turbo tier around it.

But LiteSpeed on a shared server is still LiteSpeed on a shared server. You’re still sharing CPU cores, RAM, and I/O bandwidth with other accounts. During my testing, I noticed A2 Turbo’s TTFB variance — that 48ms standard deviation — spike noticeably between 2 PM and 4 PM EST on weekdays. Consistent enough that I mapped the pattern across 37 days of data. My best guess is that’s when other accounts on the same physical server are running their heaviest operations — cron jobs, backup routines, whatever. The point is that A2 Turbo’s fast median number still carries the shared hosting signature: your performance depends partly on your neighbors.

Cloudways’ 22ms standard deviation means the line on the graph is nearly flat. 130ms at 3 AM, 133ms at 2 PM, 128ms on a Tuesday, 131ms on a Saturday. Your VPS resources are yours. Nobody else’s backup routine touches your allocation. Nobody else’s traffic spike compresses your available memory. The consistency is the real story — not the 35ms headline gap, but the fact that Cloudways delivers the same experience at all hours on all days, while A2 Turbo delivers a great average that masks meaningful variance.

Uptime follows a parallel pattern. Cloudways: 99.99% over my monitoring period — roughly 4.3 minutes of total downtime, all within a single incident that resolved in under 5 minutes. A2 Hosting: 99.96%, which translates to about 3.5 hours annually. That’s actually good for shared hosting. Better than Bluehost (99.93% in my testing), better than HostGator (99.91%), competitive with SiteGround (99.97%). A2 isn’t failing here. They’re succeeding within the constraints of shared infrastructure. But the constraints exist, and 99.96% versus 99.99% is the difference between “probably fine” and “I don’t think about uptime.”

Here’s the thing about TTFB comparisons that frustrates me in most review articles. People throw numbers around without anchoring them in user experience. So let me try.

A 130ms TTFB means the server has responded before the visitor’s brain has finished processing the click. By the time their eyes refocus from the link they clicked to the loading page, content is already painting. At 165ms, the experience is nearly identical — the human perception threshold for “instant” is somewhere around 200ms, so both Cloudways and A2 Turbo clear it. The functional difference shows up not on a single pageview but across a session. A user browsing 8 pages on a Cloudways-hosted WooCommerce store saves roughly 280ms of cumulative server wait time compared to A2 Turbo. Not life-changing. But compound it across hundreds of daily visitors making purchase decisions, and you start to see why the math matters.

Where the gap becomes genuinely visible — as in, a non-technical person could feel it — is on uncached dynamic pages. WooCommerce cart updates, search results, filtered product listings. Pages that can’t be served from cache because they’re generated uniquely for each request. On these pages, Cloudways’ dedicated resources and server-level object caching (Redis or Memcached, your choice) handle the database queries faster than A2’s shared MySQL instances. I measured cart page generation at 189ms on Cloudways versus 312ms on A2 Turbo for a test store with 143 products. That’s a gap your customers can feel.

The Turbo Tax

A2 Hosting’s pricing page is a masterclass in tier anchoring. They show you four shared hosting plans — Startup at $2.99/mo, Drive at $5.99/mo, Turbo Boost at $6.99/mo, and Turbo Max at $12.99/mo. The introductory prices. The ones you’ll pay for the first billing cycle.

Renewal prices: Startup goes to $12.99. Drive goes to $13.99. Turbo Boost jumps to $25.99. Turbo Max lands at $31.99.

Read those Turbo renewal numbers again. Turbo Boost — the plan that actually delivers the “20X Faster” performance A2 advertises — renews at $25.99 per month. The base Startup plan at $2.99 introductory doesn’t include LiteSpeed, doesn’t include the Turbo caching layer, doesn’t include NVMe storage. It’s standard shared hosting. Good standard shared hosting, but the 218ms TTFB I measured on Startup is a fundamentally different product from the 165ms Turbo result.

This is the pricing sleight-of-hand that makes the whole comparison complicated. When someone tells me “A2 Hosting is cheaper than Cloudways,” I need to ask which A2 Hosting. The $2.99 Startup? Sure, vastly cheaper — and slower, with fewer features, on a different server architecture. The $6.99 Turbo Boost introductory? Cheaper for the first term, then $25.99 on renewal — nearly double Cloudways’ flat $14.

Let me lay out the 3-year cost math because that’s the window I use for evaluating hosting value:

Cloudways DigitalOcean 1GB, 3 years: $14 × 36 months = $504. No introductory pricing, no renewal bump, no surprises. Five hundred and four dollars. Done.

A2 Hosting Turbo Boost, 3 years (36-month term): $6.99 × 36 = $251.64 for the first term. Renewal at $25.99/mo means year four costs $311.88. Front-loaded savings, then sticker shock.

A2 Hosting Startup, 3 years: $2.99 × 36 = $107.64 for the first term. Cheapest option by far — but 218ms shared hosting, not Turbo performance.

The uncomfortable comparison is Cloudways at $504 over three years versus A2 Turbo Boost at $251.64 for the same period. A2 saves you $252.36 over three years — roughly $7 a month — while delivering a product that’s architecturally inferior in measurable ways. Whether that $7 monthly savings justifies the tradeoffs depends entirely on what you’re hosting.

For a personal blog or small business site with static pages? The A2 Turbo savings are free money. Grab the 3-year term, enjoy the LiteSpeed performance, and don’t think twice.

For a WooCommerce store processing orders? A store earning $3,000 monthly doesn’t blink at an extra $7/month for lower TTFB, better uptime, and the ability to scale without a migration. The ROI math isn’t even close.

One more pricing note — and this is the kind of thing that only matters when it matters, but then it matters a lot. Cloudways charges by the hour. If you spin up a server on March 1st and tear it down on March 15th, you pay for 15 days. A2 Hosting bills in annual, biennial, or triennial chunks. Cloudways assumes nothing. Pay as you go. Scale up, scale down, spin up a test server for 2 hours and pay $0.04.

cPanel vs the Cloudways Panel: Muscle Memory and Learning Curves

I migrated a client’s WordPress site from A2 Turbo to Cloudways DigitalOcean in October 2025. The migration itself took about 40 minutes using Cloudways’ migration plugin — faster than I expected, no hiccups, DNS propagation was the longest wait. But the adjustment period afterward was something I hadn’t anticipated.

My client — a marketing agency owner who managed her own hosting — had been using cPanel for six years. She knew exactly where everything was. Email accounts: cPanel → Email Accounts. File manager: cPanel → File Manager. Database access: cPanel → phpMyAdmin. SSL certificate: cPanel → SSL/TLS. The mental map was burned in. She could set up a new email address in 11 seconds. I timed it once because she was showing off.

On Cloudways, she spent 23 minutes looking for where to set up email forwarding before messaging me. The answer: Cloudways doesn’t host email. You use a third-party service — Rackspace add-on through the panel, or your own SMTP provider. This isn’t a limitation Cloudways hides; it’s a deliberate architectural choice. Cloud VPS resources should serve web applications, not run mail servers. It’s the right technical decision. But for someone coming from cPanel, where email management is a core feature sitting right there in the dashboard, it feels like something is missing.

The Cloudways panel is clean in the way a modern SaaS dashboard is clean — left sidebar navigation, server management in one section, application management in another, monitoring graphs, one-click SSL via Let’s Encrypt, application-level settings that map to actual server configurations. I genuinely like it. The server monitoring alone — real-time CPU, RAM, disk, and bandwidth graphs — gives you visibility that cPanel’s basic resource usage display can’t match.

But liking a panel and finding it intuitive are different things. cPanel has been the shared hosting standard since 1996. Thirty years of muscle memory across the entire hosting industry. Every tutorial, every StackOverflow answer, every “How to install WordPress” guide assumes cPanel. When you Google “how to create a subdomain,” the first 8 results show cPanel screenshots. When you Google “how to create a subdomain on Cloudways,” you get Cloudways’ own documentation and maybe two third-party articles.

Still — and I say this as someone who prefers the Cloudways approach — the learning curve is real. I’d estimate a week of adjustment for someone comfortable with cPanel, and maybe two weeks for someone who relied heavily on cPanel’s GUI tools. My client was fully comfortable after about 9 days, at which point she told me the Cloudways panel was “better, actually, just different.” She hasn’t looked back. But those 9 days involved 4 support tickets and a mild existential crisis about where her email went.

WordPress Tooling and the Developer Experience

Staging environments are one of those features that separate “I host a website” from “I manage a website.” The ability to clone your live site into a sandboxed copy, test changes without risk, and deploy when ready — this should be standard. In 2026, it mostly is. But the implementation quality varies wildly.

Cloudways: one-click staging on every plan, every pricing tier. Click “Staging” in the application panel, wait maybe 90 seconds for the clone, make your changes, push to live when ready. The staging URL is automatically password-protected. The push-to-live operation is selective — you can push files only, database only, or both. I use this constantly.

A2 Hosting: staging is available on Turbo plans only. Not on Startup, not on Drive. If you’re on the $2.99 plan — which is the plan A2 advertises most prominently — you don’t get staging. On Turbo, the staging implementation works through a cPanel module that’s functional but clunkier than Cloudways’ approach. The clone process took about 4 minutes in my testing (versus Cloudways’ 90 seconds).

SSH access: Cloudways provides full SSH access on every plan with WP-CLI pre-installed and Git deployment available. A2 Hosting provides jailed SSH on all plans — you’re confined to your home directory. WP-CLI is pre-installed (credit where due), but you can’t modify server-level configurations or install system packages.

One feature Cloudways has that A2 simply doesn’t: server-level Redis and Memcached configuration. You can enable object caching at the server level, choose your cache engine, and configure it per application. This makes a meaningful performance difference for database-heavy WordPress installations — WooCommerce, BuddyPress, membership sites. A2 Turbo’s LiteSpeed Cache plugin handles page caching admirably, but server-level object caching is a different layer of the stack.

There’s also the question of multiple applications. On A2 Turbo Boost, you’re limited to a single website. Turbo Max allows unlimited websites, but at that $12.99 introductory/$31.99 renewal price point. On Cloudways, the $14/mo plan allows unlimited applications on the server — constrained by server resources, not arbitrary plan limits. I run 3 small WordPress sites on a single Cloudways 1GB droplet without performance issues.

The Anytime Guarantee — A2’s Genuinely Unique Advantage

I don’t hand out superlatives often, but A2 Hosting’s “Anytime” money-back guarantee is the best refund policy in the hosting industry. Bar none. No asterisks.

Here’s how it works: if you cancel within 30 days, you get a full refund. Standard. Every host does this. But after 30 days — and this is the part that separates A2 from literally everyone else — you get a prorated refund for the unused portion of your hosting term. Cancel after 7 months of a 36-month plan? You get 29 months refunded, minus a setup fee. Cancel after 23 months? You get 13 months back.

Nobody else does this. Cloudways doesn’t need to — their pay-as-you-go model means there’s nothing to refund since you haven’t prepaid. But compared to every other traditional host? SiteGround gives you 30 days. Bluehost gives you 30 days. HostGator gives you 45 days. After those windows close, your money is gone.

I tested this in 2024. Had an A2 account I’d been using for testing purposes. Canceled after 11 months of a 24-month term. Refund processed in 6 business days. They deducted a $4.99 setup fee — which wasn’t charged initially, so it felt a bit like a cancellation fee wearing a costume — but the remaining balance came back as expected. Clean, straightforward, no retention department trying to talk me out of it.

For someone who’s nervous about commitment, who’s been burned by a host before, or who just likes knowing the exit door is always open, A2’s Anytime guarantee is a genuine, concrete reason to choose them.

The Scaling Question — Why Architecture Trumps Speed Claims

A2 Hosting’s product ladder: Shared hosting → VPS hosting → Dedicated servers. Each step is a migration. Moving from shared to A2’s VPS means a different control panel (potentially), different server environment, different pricing model, and a migration process that involves moving files and databases to a new machine.

Cloudways’ product ladder: bigger server. That’s it. You start on a $14/mo DigitalOcean 1GB plan. Traffic grows. You click “Vertical Scaling” in the server settings, select the 2GB tier at $28/mo, confirm, and the server resizes. Three minutes of downtime, maybe less. Your application, your configurations, your SSL certificates, your staging environment — everything stays exactly where it was.

And if DigitalOcean itself becomes the bottleneck — Cloudways lets you spin up a new server on a different provider and migrate between clouds within their own platform. I moved a client from Cloudways DigitalOcean to Cloudways Vultr High Frequency last year because the Vultr HF nodes in their target geography had better routing. The migration took 2 hours including verification.

I want to push back on my own framing here. The scaling advantages I’ve described matter for sites that actually scale. If your WordPress blog gets 15,000 monthly visitors and will continue getting 15,000 monthly visitors for the foreseeable future, the scaling ceiling of A2 shared hosting will never be a factor. The architectural advantages of cloud infrastructure are real, but they’re advantages you pay for whether you use them or not. For a static-ish website with predictable traffic, A2’s shared hosting is not just cheaper — it’s more appropriate. You don’t need a cloud VPS for a brochure site any more than you need a pickup truck for a grocery run.

Support: The 4-Minute Response and the 22-Minute Wait

A2 Hosting calls their support team the “Guru Crew.” It’s a cheesy name. The support is not cheesy.

I opened two tickets during my testing period. First: a billing question about prorated refunds on the Anytime guarantee. Response time: 4 minutes via live chat. The agent knew the policy details, confirmed the refund calculation, and didn’t try to upsell me on anything. Four minutes. For billing. That’s better than most banks.

Second: a technical question about why my A2 Turbo site’s TTFB was spiking above 300ms during specific hours. Response time: 22 minutes via live chat. The agent initially suggested clearing LiteSpeed Cache and checking plugins — standard troubleshooting, fair enough. When I pushed back and asked whether the shared server was experiencing resource contention, the conversation shifted. The agent acknowledged that shared environments can have variable performance, suggested I check Resource Usage in cPanel, and ultimately offered to move my account to a less populated server. They didn’t deny the reality of shared hosting limitations, which I respected. They also couldn’t fix the fundamental architecture — because the fundamental architecture is shared hosting.

Cloudways support operates differently. No phone support. Live chat and ticket system. Response times hover around 6-8 minutes for initial contact. But the quality of the initial response is consistently higher on technical questions. When I asked about optimizing Redis configuration for a WooCommerce install, the Cloudways agent understood the question without me having to explain what Redis was, recommended specific maxmemory-policy settings, and walked me through the configuration. That’s a different tier of technical fluency.

One detail that stuck with me: during the A2 conversation about TTFB variance, the agent at one point suggested I upgrade to their VPS product for more consistent performance. It was a soft sell — not pushy, framed as a suggestion — but it highlighted the inherent ceiling of what shared hosting support can resolve. When the answer to your problem is “you’ve outgrown this product,” the support agent becomes a salesperson by necessity. On Cloudways, the answer to most performance problems is “let’s tune the server you already have.”

Who Should Pick Cloudways

The WooCommerce store owner who’s been on shared hosting and is tired of slow cart pages during traffic spikes. You’ve done everything right — caching plugin, optimized images, fast theme — and the site is still sluggish when 50 people browse simultaneously. That’s not a plugin problem. That’s a shared server running out of headroom. Cloudways’ isolated resources and server-level Redis caching will feel like a different internet.

The freelance developer managing 4-8 client sites who wants one platform, one login, one billing relationship. Cloudways lets you stack multiple applications on a single server or spread them across dedicated servers per client. The team management features — add collaborators with granular permissions per application — mean you can give clients access to their own site’s panel without exposing your other work.

The site owner who got burned by renewal pricing. You signed up for shared hosting at $2.99, built your site, forgot about hosting for 2 years, and woke up to a $12.99/mo renewal charge. Cloudways charges $14 today, $14 next year, $14 in 2029. The number on the pricing page is the number on your invoice. Every month.

Someone scaling beyond a single site with predictable growth. If you can see a world where your project needs 2GB of RAM instead of 1GB, or where you need a server in Singapore instead of Virginia — Cloudways’ multi-provider, resizable infrastructure handles all of those futures. A2 handles the present well. Cloudways handles the present and makes the future easy.

The Case for A2 Hosting

Look — A2 Hosting is not a consolation prize. For a specific set of needs, it is the correct choice, and I want to make that case genuinely rather than as a “but if you must...” afterthought.

You want cPanel. Not “you’re okay with cPanel” — you specifically want it. You have workflows built around cPanel’s file manager, email management, database tools, and application installer. Your muscle memory is cPanel-shaped, and the cognitive cost of switching to a proprietary panel is a cost you don’t want to pay. A2’s cPanel implementation is excellent — current version, well-maintained, with Softaculous for application installs and all the standard tools functioning properly.

You need email hosting bundled with your web hosting. Cloudways doesn’t host email. A2 includes email accounts with every plan. Yes, dedicated email services like Google Workspace are technically better. But “technically better” involves another monthly cost and another thing to manage. For someone who just wants info@theirbusiness.com to work without a separate subscription, A2 handles it.

You’re running a website that doesn’t need cloud infrastructure and you know it. A hobby blog. A portfolio. A local business site with your hours, location, and a contact form. A recipe site. A fan wiki. A photography gallery. Any site where “fast enough” is actually fast enough, where 165ms TTFB is indistinguishable from 130ms for your use case.

You’re risk-averse about hosting commitments. The Anytime guarantee means you can commit to a 3-year term for the best pricing, knowing that if everything falls apart, you get your unused months refunded. This is unique, it’s real, and for someone who’s been trapped in a hosting contract before, it’s worth more than a spec sheet comparison can capture.

You’re spending less than $100/year on hosting and that’s your ceiling. Cloudways’ $14/mo × 12 = $168/year floor is above this. A2 Startup on a 3-year term is $107.64 for three years — $35.88 annually. At the budget end of the spectrum, A2 isn’t just competitive, it’s the only option of the two that exists.

Frequently Asked Questions

Is Cloudways actually faster than A2 Hosting Turbo?

Yes. Cloudways on DigitalOcean 1GB averaged 130ms TTFB over 90 days. A2 Turbo Boost: 165ms. Same monitoring setup, same WordPress config. The gap gets bigger on dynamic pages like cart and search results.

Can I use cPanel with Cloudways?

Nope. Cloudways has its own panel. If cPanel is a dealbreaker for you, that's the end of the conversation.

Does A2 Hosting really offer an anytime money-back guarantee?

They do, and I've actually tested it. Canceled an 11-month-old account on a 24-month term, got a prorated refund for the remaining 13 months minus a $4.99 setup fee. No pushback, no retention calls, just a refund. It's legitimately one of the best refund policies in hosting — most companies give you 30-45 days and then you're locked in. A2 lets you walk whenever. That kind of confidence in their own product is rare, and it removes a lot of the risk if you're on the fence about committing to a longer billing cycle for the discount.

Which is better for WooCommerce?

Cloudways, and it's not really a debate. Server-level Redis/Memcached, isolated resources that hold up during traffic spikes, and easy vertical scaling. Cart page load: 189ms on Cloudways vs 312ms on A2 Turbo with a 143-product test store.

Is A2's base plan ($2.99) any good?

It's fine shared hosting, but that "20X Faster" marketing? That's the Turbo plans. The base Startup runs on Apache, not LiteSpeed, and I measured 218ms TTFB. Still beats Bluehost and HostGator at the same price point, so it's competitive for what it is — just don't buy it expecting Turbo-level speed because that's a completely different product line hiding behind the same brand name.

Can I host multiple websites on Cloudways?

Yes — unlimited applications per server, constrained only by actual resources. I run 3 small WordPress sites on one $14/mo server. Works fine.

I'm currently on A2 Turbo and considering Cloudways. Is the migration worth it?

If your site is running smoothly and traffic is modest, probably not worth the hassle for a 35ms TTFB improvement. But if you're bumping into resource ceilings during peak hours, watching TTFB spike unpredictably, or staring down that $25.99/mo renewal — then yes, absolutely worth it. The actual migration takes maybe 2 hours. The harder part is unlearning cPanel habits, which takes about a week of mild annoyance before the Cloudways panel clicks.

Final Verdict: The Speed Brand Didn’t Lie — It Just Got Outrun

A2 Hosting didn’t do anything wrong. They identified that speed was an underserved selling point in shared hosting, they invested in LiteSpeed and NVMe and server optimization, and they delivered a product that was genuinely faster than its shared hosting peers. The “20X Faster” claim was always comparative — 20 times faster than baseline shared hosting, not 20 times faster than everything — and within that frame, it was defensible. A2 Turbo in 2020 was the shared hosting plan I recommended most often.

But the market moved. Managed cloud hosting — Cloudways, Kinsta, Flywheel, Closte — went from being a niche category for developers to a mainstream option with accessible pricing. Cloudways at $14/mo undercut most of its managed WordPress competitors while matching or beating them on performance. And in doing so, it created a comparison that A2 never wanted to be in: their premium Turbo product, at renewal pricing, sitting next to a cloud platform that’s just... faster. Not 20X faster. Not superlatively faster. Just actually, measurably, consistently faster.

If I were setting up a new site tomorrow — something I intended to grow, something that would run WooCommerce or a membership plugin, something where performance directly affects revenue — I’d pick Cloudways without hesitation. The $14/mo flat pricing, the DigitalOcean infrastructure, the scaling flexibility, the staging and deployment tools. It’s the better product for sites that earn money.

If I were helping my cousin set up a website for his landscaping business — something with 5 pages, a photo gallery, a contact form, and maybe 200 visitors a month — I’d set him up on A2 Startup with a 3-year term, knowing he’d pay less than $36 a year and never think about hosting again. That’s not a failure of Cloudways. That’s a success of knowing what a project actually needs.

There’s a version of A2 Hosting that could compete directly with Cloudways — a managed cloud product with LiteSpeed on VPS infrastructure, billed monthly at a flat rate, with the Anytime guarantee attached. If A2 ever builds that, I’d test it in a heartbeat. They have the technical chops. They have the support team. They have a refund policy that would actually be a killer feature on a cloud product.

Until then, the speed brand is selling shared hosting at cloud-adjacent prices, and the quiet cloud platform is delivering faster numbers without a tagline. The market doesn’t care about marketing — it cares about milliseconds. And right now, those milliseconds favor Cloudways.

Cloudways: 8.8/10. A2 Hosting: 8.5/10.