Fast WordPress web hosting is mostly physics and discipline: PHP time, MySQL queries, and bytes on the wire. WPHost’s hosting-side claim is narrow and real — PHP 8.4 — not a fabricated 400% chart, and not a built-in CDN we do not operate. WordPress remains PHP + MySQL. Plans: $9 / $30 / $65 / $130. No one-click installer. No auto plugin updates. Deploy history ≠ database backup. No email.
Where latency actually comes from
DNS/TLS (usually small when warm), PHP bootstrap, SQL, then HTML+assets. Hosting strongly influences PHP version and machine health. You influence plugins, theme weight, and images. Edge CDNs help static bytes if you add one yourself.
Site-speed library: WordPress hosting for website speed. Store speed: fast WooCommerce hosting. Blog speed: fast WordPress hosting for blogs.
Payload size before mythology
A 3 MB hero image ruins phone LCP regardless of PHP. Resize before upload. Prefer modern formats when your workflow allows. Lazy-load below-fold. Page builders can be fine or catastrophic — measure.
Starter’s 2 GB fills with unoptimized media; “needing Scale for speed” is often needing thinner JPEGs.
Worked example: agency client microsite
Agency ships a six-page microsite. Fast path: Pro ($30) for staging, lean theme, one cache plugin excluding logged-in users, compressed case-study images, no stacked minifiers the night before launch. Test on staging. Deploy to production. Preview on HTTPS. Then DNS.
They do not buy a higher plan to chase a fake speed badge. PHP 8.4 is already there.
Free URLs are not domains you own
Agencies sometimes demos on free hostnames and call Core Web Vitals “done.” Then production on the client domain loads different absolute asset URLs, cookies, and third-party scripts. Speed work must be re-validated on the real hostname over HTTPS. Own the domain; treat preview as preview. We do not bundle a CDN — if the client wants Cloudflare, configure it on the real domain, not only on a disposable free URL.
Cache without stacking disasters
Pick one page-cache approach. Exclude carts, checkouts, and wp-admin. Object cache is a specialized tool we do not sell as a branded add-on. Auto plugin updates are not a performance feature we offer — a cache plugin updating itself into a misconfiguration is an outage.
What we will not print
- 400% faster banners
- Built-in CDN as our product
- Softaculous as acceleration
- Deploy history as a full backup that “keeps you fast after hacks” (dump MySQL properly)
- PCI SLA for Woo (Woo can run; measure cart pages carefully)
Practical speed checklist
- Confirm PHP 8.4.
- Backup DB+files; update deliberately.
- One cache plugin; verify exclusions.
- Compress images.
- Remove abandoned plugins.
- Optional BYO CDN.
- Measure cold/warm/logged-in separately.
- Use staging on Pro for experiments.
FAQ
Will Business make my site faster than Starter automatically?
Not magically. Same PHP generation. Upgrade for capacity, staging, teams — profile plugins before paying for speed myths.
Do you include a CDN for web performance?
No. Bring Cloudflare or similar if you need one.
Can WooCommerce be fast here?
Often yes for modest catalogs with good caching hygiene. No PCI SLA, no commerce fantasy layer.
Is file deploy history part of performance tooling?
It helps recover bad uploads quickly. It is not a database backup or a cache layer.