Portfolio Measurement
Reseller hosting for agencies — An agency's speed problem is variance across forty sites, not one slow page
You are accountable for client sites nobody has touched in months, and nothing in your inbox tells you which of them has quietly got slower since March.
The short answer
Measure the whole client list in one pass, then buy an account that lets you cap resources per package, so one client's runaway plugin cannot spend another client's concurrency — that means WHM with a cPanel per client, and Reseller 1 at $14.99 a month plus $0.40 per active user carries the first hundred accounts.
Specify it that way because an agency's performance problem is never a single site. It is the spread across forty of them, and spread is invisible from inside any one control panel. A shell loop over your own domain list, run monthly and kept, is the only performance report an agency actually needs.
By the HostingFast team · Reviewed 24 August 2026
24/7
Support, any hour of the night
1-click
WordPress into any account
Free
SSL on every client site
Daily
Backups on every account
Most reseller comparisons are written around margin, and margin is the easy half. What decides whether the arrangement survives its second year is whether you can tell, without asking anybody, which client site got slower this month and roughly when it happened.
That is a measurement problem with a cheap answer: one text file, one loop, one dated log. Below are the figures worth collecting, the WHM settings that keep one account's bad afternoon local, and what each reseller tier actually specifies.
Instrument every client domain in a single pass
Keep a plain text file of client domains, one per line, and loop curl over it with -w time_starttransfer and time_total. Two figures per site, about thirty seconds for a list of forty, and no dashboard to log into.
Request each domain twice and read the second result. The first may be a cache miss, and comparing a cold response on one site against a warm one on another produces a week of chasing noise.
Add a header check to the same loop — curl -sI, then look for x-litespeed-cache. A client site that never reports a hit is booting WordPress for every anonymous visitor, and the cause is usually a plugin setting a cookie rather than anything about the platform.
Save the output with a date on it. Next month's run is the report: it shows movement, and movement is what a client is really describing when they say the site feels slower than it was.
The package limits that stop one client spending another's CPU
In WHM, resources are allocated per package rather than per server, and that is the setting that decides whether trouble stays local. The entry-process ceiling caps how many PHP requests one account can have in flight; memory and I/O caps cover the rest.
Set them before the first account exists. Raising a limit later takes two minutes; lowering one on a live client site is a phone call you would rather not make.
Overselling is enabled on these plans, and it is an accounting lever rather than a performance one. You may sell more disk than the plan holds because most sites use a fraction of their allowance — but CPU and processes stay governed by the caps you configured, so treat the two as separate decisions.
Reseller 1 provides 30 GB of NVMe, 300 GB of bandwidth and 100 client accounts. When the monthly loop shows aggregate transfer climbing towards that ceiling, that is the signal to move to Reseller 2 at $29.99 — a measured trigger rather than a guess about client count.
What the client's own measurement will show them
Clients run PageSpeed Insights, not curl. The Core Web Vitals block at the top is field data from real Chrome users, which means it lags any fix you deploy by weeks. Say so before you optimise anything, or you will spend a fortnight arguing about a number that has not caught up yet.
Every client has their own cPanel, so their Resource Usage graph belongs to them alone. When somebody asks why the site was slow on Tuesday afternoon, there is a chart with an answer on it rather than a shrug.
Private nameservers carry your brand, so the delegation a client looks up shows your business rather than a supplier's.
Account separation is also what makes a departure clean: one cPanel backup out, one restore at the other end, and nothing belonging to anybody else inside it.
Size it from the numbers, then run the same checks on us
Reseller 1 is $14.99 a month plus $0.40 per active user, carrying 100 cPanel accounts on 30 GB of NVMe with 300 GB of bandwidth. Reseller 2 doubles storage and bandwidth at $29.99 for 250 accounts; Reseller 3 takes it to 100 GB and 1.5 TB at $59.99 for 500. Upgrades apply in place, so the tier you open on is not a commitment.
Point the loop at sites we already host before you order anything, compare the renewal figure with the order figure — ours are the same number — and look the company up: HostingFast is a trading name of Vitalcare at Home Ltd, registered in England and Wales.
One practical note on timing. Reseller plans carry a 7-day money-back window rather than the 30 days on shared, business, WordPress and WooCommerce hosting, so bring a real client site over on day one, not day six. Migration is free and normally done inside 24 hours.
Why a monthly loop beats a monitoring subscription
An uptime monitor tells you a site is up. It will not tell you that a client's home page has drifted from 210 ms to 900 ms across five quiet months, and that drift is what agencies actually get blamed for.
Free migration means bringing a client site over to compare costs nothing but the time to file the request, and the site keeps serving visitors throughout the move.
- One curl loop across every client domain you hold
- Entry-process, memory and I/O caps set per package
- A Resource Usage graph inside each client's own panel
- Renewal invoiced at the figure you ordered at
Why HostingFast
Standard on every plan
WHM with per-package caps
Entry processes, memory and I/O set per package, so a plugin stuck in a loop queues inside one client's account.
Reseller 1, in figures
$14.99 a month plus $0.40 per active user: 100 cPanel accounts, 30 GB of NVMe and 300 GB of bandwidth.
A usage graph per client
Each cPanel keeps its own Resource Usage history, which turns "slow on Tuesday" into something you can actually look at.
LiteSpeed in front of every account
Cached pages answer before PHP starts, and x-litespeed-cache in the headers proves it on any client domain.
Nameservers in your own name
Private nameservers carry your brand, and each client account backs up and restores independently of the rest.
Upgrades that move nobody
Reseller 1 to 2 to 3 is an account change, so growing the roster never means migrating it.
Quick Start
From order to online
- 1
Build the domain list before you buy
One file, one domain per line. Every check on this page is that file plus a loop, and it is the artefact the whole arrangement runs on.
- 2
Set package limits on day one
Entry-process and memory caps go on before the first account exists. Raising one later is trivial; lowering one on a live client site is a conversation.
- 3
Re-run the loop monthly and keep the output
A single set of figures is an opinion. Twelve dated sets are evidence you can put in front of a client who believes the site got worse.
Built In
Loaded onto every plan
- WHM on top, with a separate cPanel account for every client
- Resource limits definable per package rather than per server
- Resource Usage history visible inside each client's own panel
- LiteSpeed serving every account, with a cache header you can read
- Private nameservers carrying your brand rather than a supplier's
- Overselling available, with the resource caps still enforced underneath
- NVMe storage under every reseller tier, not only the largest
- Daily backups across every client account, restorable one at a time
- Imunify360 shielding the whole roster rather than one account at a time
- In-place upgrades from Reseller 1 to 2 to 3 with no account migration
Frequently Asked
What people ask us most often
How do I baseline forty client sites without opening forty tabs?
A text file of domains and a shell loop. Run curl with a time_starttransfer format string against each line and you have time to first byte for the whole roster in about thirty seconds; redirect it into a dated file and you have a trend from the second month onward. Request each domain twice and record the second figure, so a cold cache neither flatters nor condemns anybody.
Which resource limit actually stops one client slowing the rest?
The entry-process ceiling, in practice. It caps how many PHP requests a single account can have in flight, so a plugin stuck in a loop queues inside that account instead of consuming the concurrency everybody shares. Memory and I/O caps matter too, but that ceiling is what decides whether a bad afternoon belongs to one client or to forty.
Does overselling hurt performance, or only the accounting?
Only the accounting, provided the resource caps are set. Overselling means the disk you have sold exceeds the disk the plan holds, which works because most sites use a fraction of their allowance. It says nothing about CPU or processes — those follow the per-package limits you configure, and those are what performance actually depends on.
How do I show a client that a migration made their site quicker?
Record time to first byte and largest contentful paint on the old host for a week before the move, then the same two figures for a week afterwards. Lab tools answer the same day; the Core Web Vitals field data in PageSpeed Insights comes from real Chrome users and takes weeks to catch up, so state which one you are quoting. Migration is free, so the before-and-after costs you nothing but attention.
Keep reading
VPS vs Dedicated Servers
When a roster outgrows shared tenancy, and what dedicated hardware buys that a virtual machine does not.
Wiki Hosting
Documentation platforms compared on what they cost to run and to back up, for teams that write things down.
Reseller Hosting (Glossary)
The definition in full, with the WHM-and-cPanel hierarchy spelled out properly.
Reseller Hosting
White-label WHM hosting on NVMe behind LiteSpeed, with per-package resource caps you set yourself.
DirectAdmin Reseller Hosting
The lighter panel at a lower monthly rate, for a roster that never needed cPanel's full surface.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Measure the fleet, not one site.
WHM with per-package caps, LiteSpeed in front of every client account, free migration and a renewal figure identical to the order figure.
View Reseller Hosting plans