Speed brief · Personal trainer sites
Web hosting for personal trainers — A funnel is three pages with three different problems
The landing page has a video on it, the application page has a form on it, and the client portal is logged in — measuring them as one site tells you nothing useful.
The short answer
Measure a coaching funnel step by step, because each step fails differently. The landing page is a video and paint problem. The application form is a responsiveness and mail problem. The client portal is logged in, which means it can never be cached and is a CPU problem.
All three run here on NVMe behind a LiteSpeed cache, with the cache doing all the work on step one and none of it on step three. Sprint is $2.42 a month; Nitro at $7.08 brings two cores, 4 GB of RAM and PHP X-Ray for tracing what a portal page is doing.
By the HostingFast team · Reviewed 24 August 2026
NVMe
Storage class on every plan
Free
First-year domain on annual orders
99.9%
Uptime target, monitored
Flat
Renewal, matching your order
Who you train, what a package costs, proof it works, and a way to apply. That is the public site. Behind it, most trainers now run something else entirely: a logged-in area with programmes, check-ins and payment.
Those two halves have almost nothing in common technically. The public half is cacheable, spiky and cheap. The private half is uncacheable, steady and the part that consumes resource. Treating them as one site is why plans get chosen badly.
The sections below take the funnel a step at a time, then deal with the launch week — which is when all three parts get tested at once, usually on the same evening.
Measure each step of the funnel separately
Run Lighthouse on the landing page, the application page and a logged-in portal page as three separate tests, Mobile with Slow 4G throttling, three runs each. Write down largest contentful paint and interaction to next paint for all three. They will not resemble one another.
The landing page should be quick because it is cached. The application page will be slower to respond because of form scripts. The portal page will be the slowest of the three, and that is expected — it is rendered from scratch on every request because it is personal to the person logged in.
Video on a landing page: preload and poster
If your landing page opens with a sales video, the poster frame is almost certainly your largest contentful paint element. Give it display-size dimensions and let WebP conversion handle the rest, and never lazy-load it — deferring the hero is the classic own goal.
Set preload to none or metadata so the video file is fetched only when someone presses play. Left on auto it competes with your own page for bandwidth on exactly the connection where you can least afford it, and most visitors never watch it anyway.
The client portal is logged in, so it is never cached
Every page a client sees after logging in is generated individually: PHP runs, the database is queried, the session is written. No page cache can help, by design. What helps is object caching, which holds query results in memory — Redis object caching is available on the managed WordPress plans for exactly this.
Beyond that it is resource. Sprint gives one core and 2 GB of RAM, which is fine for a handful of clients. Once the portal is the business rather than a side feature, two cores and 4 GB on Nitro at $7.08 plus PHP X-Ray on CloudLinux Pro is the honest answer.
Sizing for a launch week
A cohort launch produces a short, sharp burst on the landing page followed by a wave of applications and then a wave of logins. Only the first of those is cached, which is why launches feel fine for an hour and then start to drag.
Test the sequence in advance. Warm the landing page, submit a genuine application and follow the confirmation email into an inbox, then log in and time a portal page. Managed WordPress plans state monthly visit allowances too — 100k on Sprint WordPress at $4.19, 400k on Turbo WordPress at $5.59, 1M on Nitro WordPress at $9.09 — which is a useful figure to hold a launch against.

Cached where it can be, resourced where it cannot
The public funnel is answered from the LiteSpeed cache on NVMe without PHP starting. The logged-in portal gets the account's CPU and memory, with Redis object caching on the managed WordPress plans to keep each render cheap.
Free SSL, free migration and a first-year domain come with the plan, and the renewal figure is the figure you ordered at — useful when you are pricing a cohort a quarter ahead.
- LiteSpeed page caching for the public funnel
- Redis object caching on the managed WordPress plans
- Stated monthly visit allowances on the WordPress tiers
- Flat renewals, quoted the same in year two
Why HostingFast
Standard on every plan
Landing pages served from cache
A launch burst on a public page is answered from server memory, without PHP starting at all.
Portals given real resource
Two cores and 4 GB of RAM on Nitro for the pages that are personal to every client.
Query results held in memory
Redis object caching on the managed WordPress plans keeps an uncacheable portal page quick.
Visit allowances you can plan with
100k, 400k and 1M monthly visits across the managed WordPress tiers, stated rather than implied.
Applications that reach you
MailChannels carries outbound mail with SPF, DKIM and DMARC configured on your domain.
A price you can quote against
Flat renewals mean the cost you build into a cohort price does not move underneath you.
Quick Start
From order to online
- 1
Test all three steps
Lighthouse on the landing page, the application page and a logged-in portal page, separately, Mobile and Slow 4G, three runs each.
- 2
Move the funnel across
Free engineer-handled migration for the existing site, or a one-click WordPress install and a first-year domain on an annual order.
- 3
Rehearse a launch
Warm the landing page, submit a real application, follow the email to an inbox, then log in and time a portal page.
Built In
Loaded onto every plan
- Each funnel step measured separately rather than as one site
- Poster frame given display dimensions and never lazy-loaded
- Video preload set to none or metadata rather than auto
- Redis object caching available on the managed WordPress plans
- Stated monthly visit allowances: 100k, 400k and 1M by tier
- MailChannels on outbound mail, with SPF, DKIM and DMARC set
- NVMe SSD storage behind a server-level LiteSpeed cache
- Free SSL on every plan, renewed automatically before it can expire
- A renewal price identical to the price you signed up at
- Human support on duty every hour of every day
Frequently Asked
What people ask us most often
Why is my client portal slower than my landing page?
Because it cannot be cached, and that is by design rather than a fault. A landing page is identical for every visitor, so the LiteSpeed cache answers it from server memory. A portal page is personal to whoever is logged in, so it has to be rendered from scratch every time — PHP runs, the database is queried, the session is written. Object caching and CPU are what help there, not page caching.
What should I do with the sales video on my landing page?
Two things. Treat the poster frame as a hero image — display-size dimensions, WebP conversion, never lazy-loaded, because it is almost certainly your largest contentful paint element. And set preload to none or metadata so the video itself is only fetched when somebody presses play. Left on auto it competes with the page for the same bandwidth.
How many monthly visits do the managed WordPress plans allow?
They are stated per tier: 100k a month on Sprint WordPress at $4.19, 400k on Turbo WordPress at $5.59 and 1M on Nitro WordPress at $9.09, with the top tier carrying three cores and 6 GB of RAM. Those are useful figures to hold a cohort launch against, because a launch is exactly the moment a vague allowance becomes an urgent question.
Which part of the funnel should I test before a launch?
All three, in sequence, on the day before rather than the day of. Warm the landing page so the first visitor gets a cached response. Submit a genuine application and follow the confirmation email into an inbox — that is the step that fails silently. Then log in and time a portal page, because the login wave arrives after the application wave and lands entirely on uncached pages.
Keep reading
Landscapers — Hosting Guide
Seasonal trade sites where the enquiry wave arrives in a few concentrated weeks.
Car Dealerships — Hosting Guide
High-value enquiry sites where a slow form costs more than a slow homepage.
Best VPS for a Personal VPN
Running a private network endpoint on a small server, sized and costed honestly.
VPS Hosting — Built for Personal Trainers
Dedicated CPU and memory for a portal that has outgrown a shared allocation.
PHP Hosting
PHP versions, extensions and per-site switching from the control panel.
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 funnel, step by step.
Cached public pages on NVMe from $2.42 a month, Redis object caching for the portal, free SSL and migration included.
View VPS Hosting — Built for Personal Trainers plans