1. Home
  2. Plans & Billing
  3. What Distinguishes Each Pagely Hosting…

What Distinguishes Each Pagely Hosting Plan From Another?

Each VPS plan is provided a predetermined set of CPU and memory capacity. With all of our plan options, customers receive a dedicated Amazon EC2 instance (see our comparison matrix for exact resource allotments) for serving your web requests.

What Metrics Does Pagely Use to Differentiate its Plans?

Our architecture is unique in the managed WordPress hosting space. With operating on dedicated AWS instances only, our dependencies are based purely on resource usage with the goal of making the most out your hardware here by leveraging our expert engineering brainpower.

There are no page view limits assigned to any Pagely hosting plan. That means no nefarious, unnecessary margins funneling to us, no shared hosting using the same pool of resources as others, and more flexibility and freedom to run your WordPress applications fast & effectively.

Here’s a chart gauging relative performance per each single-node plan:

As customers begin to move up our product line, we’re essentially doubling the number of CPU cores & RAM with each upgrade, and consequentially the number of PHP workers able to support larger volumes of concurrent traffic. Our plans also include guided flexibility with the number of PHP workers we can compile on your VPS without mandating a plan upgrade or added spend.

High Availability (HA) plans offer you mirrored web servers built for minimizing downtime with added redundancy and auto-failover features. Find more info on how our HA solutions work and when it’s appropriate to choose HA in the linked KB articles.

Evaluating WordPress Performance & Scaling

When scaling your website, much of your performance and stability is impacted by caching. Having the right caching tools in place is imperative for reaching optimal efficiency. Our PressCACHE system tuned specially for WordPress is designed with two main goals in mind:

  1. Increase deliverability speed of your WordPress website by storing your HTML rendered pages in cache.
  2. Enhance the scalability of your AWS configuration by absorbing and serving as much of your traffic volume as possible from cached assets. This is especially effective for pages returning a high cache hit rate.

In the event your website sees massive amounts of simultaneous traffic, even caching can fall short of delivering the adequate level of resources needed to remain steady. By upgrading to the next plan in line, you’re increasing the potential capacity to accommodate larger waves of both cached and non-cached traffic, all while magnifying performance.

Was this article helpful?