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. Your web servers operate on dedicated AWS EC2 (Elastic Compute) instances, with separate database resources for optimized performance. Your sites’ speed and scale are limited only by the amount of hardware in your plan, along with our expert WordPress optimization expertise.

There are no page view limits assigned to any Pagely hosting plan. That means no nefarious, unnecessary margins funneling to us, and more flexibility and freedom to run your WordPress applications fast & effectively.

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

As customers begin to move up our product line, we are essentially doubling the number of CPU cores & RAM with each upgrade, and consequently, 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.

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 are increasing the potential capacity to accommodate larger waves of both cached and non-cached traffic, all while magnifying performance.

Was this article helpful?