Payload brief · Therapy Practice Sites
Web hosting for therapists — Six pages of text should not take four seconds
Your site is small, your host is fine, and the page still feels slow — because the weight is in two fonts, a theme framework and a script you forgot you installed.
The short answer
On a small text-led practice site the server is almost never the problem, and moving host will almost never fix it. Six pages of prose cached by LiteSpeed on NVMe return their first byte in a fraction of Google's 800 ms good boundary. What makes such a site feel slow is payload it did not need: two or three web fonts, a page-builder framework loading its whole stylesheet on every page, and one or two third-party scripts nobody has audited since launch.
The measurement that finds all three is total transfer on a cold, throttled load — a single number, taken once, that tells you whether you have a hosting question or a page question. HostingFast gives the hosting half NVMe storage behind LiteSpeed caching from a couple of dollars a month, with free SSL, free migration, mailboxes on your domain and a human on support at any hour.
By the HostingFast team · Reviewed 24 August 2026
24/7
Cover, any hour
1-click
WordPress install
Free
Cost of a certificate
Daily
Restore point schedule
This is the most misdiagnosed performance problem there is. The site is small, so slowness feels like it must be the hosting — and the industry is happy to sell a bigger plan for a problem a bigger plan does not touch.
The visitor makes it worse in a specific way. Choosing a therapist is a slow, private decision made over several visits to the same site, mostly on a phone, often late at night. Returning visits should be the fastest ones you serve, and they are not if every page re-downloads a font set and a builder stylesheet.
So the method here is subtractive rather than additive. Nothing to install, nothing to configure: find what the page is loading that it does not need, remove it, and measure the difference.
Get one number before touching anything
Load your busiest page in Chrome DevTools with the cache disabled and the network throttled to a slow mobile profile, then read the total transferred at the bottom of the network panel. That single figure decides which conversation you are having. A text-led page carrying well over a megabyte is a payload problem, whatever your host is.
Alongside it, take the server number separately so it stops being a suspect: `curl -s -o /dev/null -w '%{time_starttransfer}' https://yourdomain.example`, five runs, median kept. If a cached page comes back in the low hundreds of milliseconds, hosting has done its job and the remaining seconds are all in the page.
Fonts first, because fonts are invisible
Sort the network panel by size and look at what is above the images. On practice sites the answer is frequently two font families in four weights, most of them never used. Every one is a separate fetch, and a font loading with a blocking display strategy means the text is present but unpainted while the browser waits.
Cut to one family and the weights you actually set, and let text render immediately in a fallback while the web font arrives. That change costs nothing, is invisible to a visitor beyond the page appearing sooner, and it usually moves the measurement more than any image work on a site with few images.
The enquiry route is the only page that runs code
Everything else on the site is cacheable prose. The contact form is not: submitting it is a POST, it bypasses the cache, it boots PHP, and on many form plugins it waits for the mail server to accept the message before it will return a confirmation. That is the one request where the stack is genuinely exercised.
Time it as a visitor would — submit a real test with DevTools open and read the POST timing, not the page load. Then test delivery separately, because a form that shows a thank-you page and silently fails to deliver is the worst outcome on a site like this. Outbound mail here goes via MailChannels, and mailboxes on your own domain come with every plan.
What not to spend the afternoon on
Do not chase a lab score of 100. Lab numbers move with the test server and the moment, and the report that actually grades you is the field one: LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1, read at the 75th percentile of real visits. A consistently green field record beats a fragile perfect number every time.
Do not install a second caching plugin on top of server-level caching, and do not buy a CDN to solve a font problem. On a six-page site the honest list of high-value work is short: fewer fonts, a lighter theme, no unused scripts, and one properly sized image per page. Everything past that is effort with nothing at the end of it.
What we do, and what we will tell you not to buy
The platform side is already handled: NVMe storage on every tier, LiteSpeed caching inside the web server, automatic WebP conversion, free SSL that renews itself and daily backups you can restore from the panel.
The page side is yours, and on a small practice site it is where nearly all the available improvement lives. We would rather point at a font stack than sell a plan that will not change the number.
- Server-level caching, not a plugin you configure
- NVMe storage under the entry tier too
- Free SSL issuing and renewing itself
- Daily restore points on every plan
Why HostingFast
Standard on every plan
A first byte that is not the problem
Cached prose off LiteSpeed and NVMe returns fast enough that hosting stops being a plausible suspect, which is genuinely useful information.
Nothing to configure to get caching
The cache lives in the web server. There is no plugin to tune, and no second caching plugin fighting the first one for control of the same headers.
Mail that is tested, not hoped for
Mailboxes on your own domain with MailChannels handling outbound delivery, so a quiet enquiry form can be diagnosed rather than guessed at.
A clone to strip things on
Staging lets you remove a font, a script or a builder plugin and compare the number before the change reaches a client mid-decision.
Certificates that stay valid
Free SSL on every plan, renewed automatically. A browser warning on a first visit to a therapy site costs more than a slow page ever will.
Support that will say no
Humans at any hour who will tell you when the problem is a font rather than a plan, because the alternative is you paying us for nothing.
Quick Start
From order to online
- 1
Take total transfer on a cold throttled load
One number from the network panel, cache disabled, slow mobile profile. It tells you immediately whether this is a payload problem or a hosting one.
- 2
Sort by size and remove, in order
Fonts, then unused scripts, then oversized images. One removal, one retest, one note. Subtraction is the whole strategy on a site this size.
- 3
Time the enquiry POST on its own
The only request that runs code. Measure the submission, then separately confirm the mail actually arrived at an address you control.
Built In
Loaded onto every plan
- Total transfer recorded on a cold, throttled load of the busiest page
- Median TTFB taken separately, so the server stops being a suspect
- Font families reduced to one, with only the weights actually used
- Web fonts set to render text immediately rather than blocking on the fetch
- Unused third-party scripts identified in the network panel and removed
- Page-builder stylesheet checked for loading on pages that do not use it
- Enquiry POST timed with DevTools rather than inferred from page load
- Form delivery verified to a real mailbox, not just the thank-you screen
- No second caching plugin layered over the server-level cache
- Field vitals watched instead of chasing a perfect lab score
Frequently Asked
What people ask us most often
My site is only six pages. Why would hosting not be the cause?
Because six pages of cached prose is close to the cheapest thing a web server can do. Take the server number on its own with curl: if a cached page returns its first byte in the low hundreds of milliseconds against Google's 800 ms good boundary, the host has already finished its part. The remaining seconds are being spent downloading and rendering things the page asked for.
How much of the load is usually fonts?
On text-led practice sites, more than people expect — frequently several hundred kilobytes across two families and four weights, most of which the design never uses. They also delay painting when they load with a blocking display strategy. Reducing to one family and letting text appear in a fallback first is usually the single largest improvement available, and it costs nothing.
Is a caching plugin worth adding on top of your caching?
Generally no, and it can make things worse. LiteSpeed caching runs inside the web server here, so a plugin trying to manage the same headers from PHP is a second opinion the browser did not ask for. If you want a plugin, use the one built for this cache rather than a general-purpose one, and confirm on the response headers that only one thing is deciding cache policy.
The site feels slower on my laptop than the reports suggest. Why?
Check whether you are logged in. Logged-in requests skip the page cache by design, so as the site's editor you are experiencing the uncached version of every page while your visitors get the cached one. It is a useful signal about your plugin stack, but it is not what a client browsing at eleven at night is seeing.
Keep reading
Martial Arts Schools — Hosting Guide
Programme pages, an uncacheable booking POST, and the measurements that separate them.
Car Detailers — Hosting Guide
Where a detailing site's weight sits, and which parts a visitor actually waits on.
How to Test Your Website Speed
The full method — tools, thresholds, and the order to apply them in.
Web Hosting — Built for Therapists & Counsellors
The plans themselves: NVMe, server-level LiteSpeed, free SSL and free migration.
WordPress Hosting
Managed WordPress with Redis object caching for the routes that skip the page cache.
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.
Subtract, then measure again.
Server-level LiteSpeed and NVMe on every tier, free SSL that renews itself, and support that will tell you when a plan is not the answer.
View Web Hosting — Built for Therapists & Counsellors plans