Performance Glossary
A CMS Builds Every Page. Caching Decides the Cost
You need to explain why a database-driven site can be slower than a folder of HTML, and what has to be true for it not to be.
The short answer
A CMS wraps your content in an editing interface and assembles each page from a database when it is requested, which is what makes editing painless and what makes an uncached page slower than a static file.
The whole trade rests on caching. Store the assembled result and serve it repeatedly, and the convenience costs nothing on most requests; skip that step and every visitor pays the full render.
By the HostingFast team · Reviewed 12 August 2026
0
Terms, measured not asserted
100+
Entries wired together
Real
Runnable commands
Free
Free to read, always
Content and presentation are kept apart. Editors work in an interface, templates decide what the output looks like, and the two can change independently. WordPress dominates the field, while Joomla and Drupal hold on wherever the content model needs an unusual shape.
The choice is really about who edits and how structured the content is. Custom content types, permission models and translation workflows separate these platforms far more sharply than any comparison table on their own websites does.
What happens on an uncached request
The web server hands the request to PHP, PHP boots the application and its extensions, the application resolves the route, runs its queries, renders templates and returns HTML. On a static file none of that happens: the server reads bytes off disk and sends them.
That is the honest comparison, and it is why cache hit ratio is the number that decides whether a CMS site feels quick. Nothing about the platform makes it slow; the work it performs on a miss is what makes it slow.
Which requests can never be cached
Anything personalised: a logged-in view, a basket, a form submission, a search results page, an admin screen. These paths always run the full application, so they are where a CMS site's real performance profile lives and where object caching pays for itself.
Count them before you tune anything. If ninety-five per cent of your traffic is anonymous article reads, page caching solves your problem. If half of it is logged-in members, page caching barely touches your worst path and you should be looking at queries instead.
Where the platforms genuinely differ
On rendering cost, less than the marketing suggests. On workflow, considerably: Joomla's granular editor permissions, Drupal's structured content types and approval chains, WordPress's enormous plugin ecosystem. All three run on our plans, and all three are PHP applications with a database behind them.
Choose on the content model and the people editing, then treat the performance work as identical regardless of which you picked. The caching layers, the query profiling and the PHP version dropdown behave the same way for all of them.
Reading your hit ratio
The cache is either answering or it is not, and the response headers say which. Request a page twice and look for the cache status header on the second one — a miss on a page that should be cacheable usually means a cookie, a query string, or a rule excluding more than you intended.
Track the ratio over a week rather than judging it from one request. A ratio that drops sharply after a deploy is the clearest signal that something in the new release is setting a cookie on every visitor, which quietly turns your entire site into the uncached path.
Platform choices, without the platform loyalty
Where three tools do broadly the same job, these entries say what actually separates them and what is identical no matter which you pick.
WordPress, Joomla and Drupal all install in one click here, on LiteSpeed with NVMe storage and per-site PHP version control.
- Render cost described step by step
- Uncacheable paths counted first
- Differences located in workflow
- Hit ratio read from headers
Why HostingFast
Standard on every plan
The request path, step by step
What happens between the server and the HTML on a cache miss, so the cost has a shape rather than a reputation.
Traffic mix before tuning
Counting anonymous against personalised requests, because the two are fixed by completely different work.
Differences where they are real
Workflow, permissions and content modelling, rather than a rendering-speed contest nobody wins.
Hit ratio as the headline number
How to read cache status from response headers and what a sudden drop after a deploy usually means.
Same tuning, any platform
The caching layers and profiling steps that apply identically whichever of the three you chose.
Linked to the layer beneath
Where the answer turns out to be a query or a runtime version, the entry points you at it.
Quick Start
From order to online
- 1
Split your traffic by cacheability
Count anonymous requests against logged-in and personalised ones. That ratio decides which caching layer is worth your afternoon.
- 2
Read the cache header twice
Request a page, then request it again and look at the cache status. A second-request miss is a rule problem, not a hardware one.
- 3
Profile one uncacheable path
Take the heaviest personalised page and attribute its time to plugins and queries on staging before changing anything.
Built In
Loaded onto every plan
- Softaculous installers for WordPress and 400+ further applications
- LiteSpeed compiled into the server, not a caching plugin bolted on afterwards
- PHP version selectable per site, switched from the control panel in seconds
- NVMe on every tier — the entry plan runs the same drives as the top one
- Staging you can clone, break and throw away before anything reaches live
- Daily backups with a self-service restore you run yourself from the panel
- cPanel, so every script and tutorial you already have still applies
- Free SSL on every plan, reissued automatically well before it can expire
- A human on support at any hour, including for the awkward questions
- Free migration by our own engineers, normally inside 24 hours
Frequently Asked
What people ask us most often
Is a CMS slower than a static site, honestly?
On a cache miss, yes, and by a wide margin — the application has to build what a static server merely reads. On a cache hit the difference disappears, because the visitor is receiving a stored response. So the real question is what proportion of your requests miss, not which architecture you picked.
Which CMS handles a team of editors best?
Joomla for granular per-editor permissions out of the box, Drupal for structured content with approval chains, WordPress for everything else plus the largest ecosystem by a distance. All three install in one click here, and the hosting-side tuning is identical for each.
How many sites can share a single account?
From the Turbo tier upwards you can run several, each with its own domain, mailboxes and certificate inside one account. If the extra sites belong to clients rather than to you, reseller hosting is the better shape: it keeps each account properly walled off from the others.
What does support actually cover at three in the morning?
A human reply at any hour, with a scope that includes the practical jobs: DNS records, mailbox setup, a restore, a WordPress site that has stopped answering. Send a hard technical question in before you buy — the reply you get is a fair preview of the standard afterwards.
Keep reading
Database
The queryable half of a site, and why a restore is never files alone.
WordPress
The PHP application under four in ten websites, and what decides its speed.
Best CMS Hosting for Content Teams
Which CMS hosts hold up when four editors publish at once, with the checks shown.
Web Hosting
cPanel hosting on NVMe with LiteSpeed, free SSL and a migration included.
Secure Hosting
Imunify360, isolated accounts and hardened defaults, without a speed penalty.
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.
Assemble it once, serve it many times.
LiteSpeed page caching, Redis for the paths it cannot touch, and one-click installs for WordPress, Joomla and Drupal.
View Web Hosting plans