Profiling Notes
WordPress com vs self hosted — The same code, and only one of them lets you profile it
You know both options run WordPress. What nobody has told you is which one lets you find out why a page takes 900 milliseconds and which one leaves you filing a ticket about it.
The short answer
Choose self-hosted if you ever intend to diagnose your own site: WP-CLI, the slow query log, an object-cache drop-in, a profiler and per-site PHP settings are all things you either have shell access to or you do not, and that access is the real difference between the two products.
Both run the identical open-source code. What varies is who holds the keys to the installation and how deep you can go when something is slow. Below: the tools each side gives you, the cache layers you can only reach when you own the stack, and how to measure the same site on both.
By the HostingFast team · Reviewed 24 August 2026
99.9%
Uptime target
24/7
Humans reachable
Free
SSL, all plans
NVMe
Disks under it
The two products share a name and a codebase, which is why the comparison is usually written as a features table. For anyone who has ever had to work out where a request's time actually went, that framing misses the point entirely.
The useful question is diagnostic reach. When a page slows down, can you open a shell, run WP-CLI, read the slow query log, install Query Monitor and see the queries, or are you limited to a dashboard and a support form? That answer determines how long every future problem takes to fix.
Diagnostic reach is the actual difference
On a self-hosted installation you can install Query Monitor and see every query a page ran, with durations and callers attached. You can enable the MySQL slow query log and find the offender by name. You can run WP-CLI over SSH to bulk-check plugins, flush caches or transform data without loading a single admin screen.
On a hosted platform the equivalent operations are either restricted or absent, depending on the tier. That is not a criticism of the product — it is what makes it maintenance-free — but it does mean an unexplained slowdown becomes somebody else's queue rather than your afternoon.
If you never intend to look, this costs you nothing. If you are the person who ends up looking anyway, the ability to open a shell is worth more than any feature on either comparison table.
The cache layers you can only reach when you own the stack
Our WordPress plans run AccelerateWP alongside Redis object caching, with LiteSpeed handling page cache at server level. Those are three distinct layers doing three different jobs, and knowing which one a given request missed is most of the work of making a slow site fast.
Page cache serves anonymous visitors without waking PHP. Object cache stops the same query being answered twice within a single request or across requests. OPcache keeps compiled PHP in memory. A site with all three configured behaves very differently from one relying on a single plugin, and you can only assemble them where you control the stack.
The object-cache drop-in is the one people miss. It is a file in wp-content, it needs Redis behind it, and on a dynamic site it typically does more for real response times than another page-cache plugin ever will.
Measuring the same site on both
Use curl with a write-out format to read the time to first byte, and run it a dozen times rather than once. A single sample tells you almost nothing; a distribution tells you whether the cache is warm, whether the origin is consistent, and whether the slow request was an outlier or the norm.
Then run Lighthouse for the browser side and check the field data in the Chrome User Experience Report for what real visitors experienced. Lab and field disagree more often than people expect, and the disagreement is usually the interesting part.
Sprint WordPress is specified for one site, 10 GB of storage, one core with 2 GB of RAM and 100k monthly visits, with 10 staging copies, WordPress Toolkit Deluxe and WP-CLI over SSH. That is a stack you can profile, which is the whole argument on this page in product form.
What moving actually involves
Installation is one click and updates and backups run for you on managed WordPress, so the difficulty reputation attached to self-hosting mostly belongs to unmanaged servers rather than to this arrangement.
Migration from an existing host is free and run by our engineers: files, database, mailboxes and configuration come across, you review the copy before DNS moves, and the old site keeps serving until the new one is ready.
Order annually and the first year of your domain registration is included, free SSL issues and renews itself, and the rate you order at is the rate you renew at. The commercial side stays boring on purpose so the technical side can be the interesting part.
Why we keep pointing you at the shell
Every performance claim we make is one you can check with WP-CLI, curl and Lighthouse from your own machine. That is the point of selling a stack you can open rather than one you have to trust.
Redis object caching, AccelerateWP and up to 10 staging copies come with the WordPress plans, so the layers you need to test with are already there.
- Query Monitor and the slow query log
- WP-CLI over SSH, not a dashboard
- Three cache layers, separately controlled
- Free migration with no cutover gap
Why HostingFast
Standard on every plan
A shell you can actually use
WP-CLI over SSH, with Git and Composer alongside it, so diagnosis does not have to route through wp-admin.
Redis object caching included
The drop-in that stops repeat queries, which on a dynamic site does more than another page-cache plugin.
AccelerateWP and LiteSpeed
Server-level page caching in front of PHP, so anonymous traffic never reaches the application at all.
Ten staging copies
Clone, test and push live — enough parallel environments to reproduce a bug without touching production.
WordPress Toolkit Deluxe
Cloning, rollbacks and update management included at no added cost on the WordPress plans.
Migration handled by engineers
Files, database, mail and configuration moved free, with the old site serving until the new one is verified.
Prices Side by Side
Our numbers next to the big names
Typical intro and renewal pricing across the market, lined up against ours — including the renewal figure most comparison charts skip.
| Feature | HostingFastMost popular | Typical household-name host | Typical bargain host | Typical loss-leader deal |
|---|---|---|---|---|
| Starting price / mo* | $2.42/mo | $4–$6 | $2–$4 | $1–$3 |
| Renewal price / mo | $2.42/mo | $10–$15 | $8–$12 | $4–$6 |
| Cheapest plan renews at its sign-up price | ||||
| SSL as standard | ||||
| Migration done for you | ||||
| NVMe drives on the cheapest tier | ||||
| Daily backups from the first tier | ||||
| Real humans on support, 24/7 |
*Our number is the lowest-priced plan we sell on an annual term, pulled live from the same catalogue that powers our pricing page — it physically cannot fall out of date. The other three columns show the ranges shared hosts in each bracket typically advertise: introductory offers that mostly demand a one-to-four-year commitment, then jump once it expires. We no longer name rivals or print their prices, because a figure we cannot verify on the day you read it has no business on this page. Line us up against whichever host you are really weighing — and give the renewal row the hardest look.
Quick Start
From order to online
- 1
Sample TTFB properly
Run curl with a timing write-out at least a dozen times against the same URL and look at the spread. One request tells you about one request; the distribution tells you whether the cache is doing its job.
- 2
Find the query, not the symptom
Install Query Monitor, load the slow page as an administrator, and read the query list sorted by duration. Nine times out of ten one query or one autoloaded option is responsible for most of the wait.
- 3
Add the object cache and re-measure
Put the Redis drop-in in place, warm the site, and repeat the same curl sampling. If the median barely moves, the bottleneck was never repeat queries and you have just eliminated a suspect for free.
Built In
Loaded onto every plan
- WP-CLI over SSH, with Git and Composer available at the command line
- Redis object caching alongside AccelerateWP on the WordPress plans
- LiteSpeed page caching built into the server, not added by plugin
- Up to 10 staging copies for reproducing a problem safely
- WordPress Toolkit Deluxe included at no added cost
- Per-site PHP version switching from the control panel
- NVMe SSD storage under every tier, entry plan included
- Free WordPress migration from your old host, run by our engineers
- Free SSL that renews itself before it can lapse
- Core and plugin updates applied for you, with a daily backup behind them
Frequently Asked
What people ask us most often
Can I run WP-CLI or profile queries on WordPress.com?
Not in the way a developer means. Shell access, an arbitrary object-cache drop-in and the MySQL slow query log are things you get when you control the installation. On managed WordPress here, WP-CLI runs over SSH on every plan, which is what makes a slow page a diagnosis rather than a support ticket.
Does Redis object caching actually help a small site?
It helps dynamic requests, not cached ones. A brochure site whose pages are served from the LiteSpeed page cache will barely notice. A membership area, a store or anything where visitors are logged in bypasses page cache entirely, and that is exactly where an object cache stops the same query being answered twice.
How do I measure Time to First Byte properly from the command line?
Use curl with a write-out format that reports the time to first byte, and repeat it a dozen times rather than trusting one sample. Look at the median and the spread. A tight distribution means the cache is working; a wide one usually means some requests are missing it entirely.
What does a 100k monthly visits figure mean in practice?
It is the sizing guide for the Sprint WordPress tier, alongside 10 GB of storage, one core and 2 GB of RAM. Turbo WordPress steps up to 400k and Nitro WordPress to 1M with more cores and memory behind them. Upgrades happen in place from the client area, so outgrowing a tier is a setting rather than a migration.
Keep reading
Let's Encrypt vs Paid SSL
Whether a paid certificate changes anything measurable in the handshake, and where it genuinely does.
Addon Domains vs Separate Accounts
Shared allocation versus separate accounts, judged on contention rather than on tidiness.
How to Speed Up WordPress
The specific changes that move a WordPress site's numbers, in the order worth doing them.
WordPress Hosting
Managed WordPress with LiteSpeed, Redis object caching and up to ten staging copies.
VPS Hosting
KVM virtual servers with full root, DDoS filtering and one flat monthly rate.
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.
Take a stack you can open.
Managed WordPress with WP-CLI, Redis, LiteSpeed and staging copies — plus a free migration to get your existing site onto it.
View WordPress Hosting plans