Performance profile · Copywriters & Content Studios
Web hosting for copywriters — Nothing on your site is heavier than the words
You publish text and nothing else, so a four-second paint on a phone has exactly one explanation — and it is not the length of your copy.
The short answer
A page of text should paint almost immediately, so when it does not the cause is nearly always the font stack: two or three custom faces, loaded render-blocking, with no fallback while they download. Set `font-display: swap`, cut to one or two weights, and re-run a throttled Lighthouse pass — LCP usually drops by more than any hosting change would give you.
The server side is straightforward: your pages are identical for every visitor, so LiteSpeed serves stored HTML without waking PHP, on NVMe, from a London origin 5 to 15 ms away from a UK reader. That part comes with the entry plan; the rest of the fix lives in your theme.
By the HostingFast team · Reviewed 24 August 2026
Free
Migration from your old host
24/7
Answers from humans
Daily
Backups, self-service
$0
Setup fees
A copywriter's own website is the sample every client reads without being asked to, which makes its speed a professional claim rather than a technical detail. A slow page of prose is an argument against the person who wrote it.
The diagnosis takes one Lighthouse run: Chrome DevTools, Mobile, throttling on Slow 4G, three passes, median. The report will list render-blocking resources and name your LCP element. On a text site the blockers are fonts and the LCP element is usually a heading that could not render until a font arrived.
The second thing worth timing is the enquiry form, because a form that fails quietly costs you a project rather than a metric. Both tests take an afternoon, and neither of them requires you to believe anything a host says.
Fonts are the only heavy thing on a text page
Three custom faces at four weights each is twelve files, and if they load render-blocking the browser holds your words back until they arrive. Look at the render-blocking list in the Lighthouse report, then at the network waterfall: fonts sitting in front of first paint is the pattern. Fix it with `font-display: swap`, self-host what you can, and cut the weights you never actually use.
Watch Cumulative Layout Shift while you do it, because a swap that changes metrics mid-paint makes the text jump. Set a sensible fallback stack with similar proportions, re-run the same three passes, and compare medians rather than best runs. This is one of the few optimisations where the win is both visible and measurable in a single session.
Publish the samples as pages, and time one
A sample locked in a PDF is a download, a wait and a pinch-to-zoom, and none of that is measurable in the metrics a client will read. Published as a page, the same sample paints in a second, gets indexed, and can be timed: five runs of `curl -s -o /dev/null -w '%{time_starttransfer}'` gives you a median TTFB, and Google's good threshold is 800 ms.
A cached page here should be far inside that, because a sample is the same bytes for every reader and LiteSpeed hands over stored HTML without touching PHP. If your median is poor on a text page, the cache is not doing its job — check that you are running exactly one caching plugin, not two competing for the same HTML.
The enquiry form is the only path that cannot be cached
Submissions run the full stack every time: PHP, database, mail. Test it end to end with a real address rather than trusting the on-screen confirmation, and read the headers of what arrives — SPF passing, DKIM signing, DMARC aligned. Those records are configured for you here and outbound mail leaves through MailChannels.
While you are in there, put the scoping questions in the form itself: word count, revisions included, deadline, who signs off. It is the same principle as caching — answer the predictable question once, in advance, instead of paying for it on every request.
Keep a dated baseline, because decay is invisible
Sites get slower the way rooms get untidy: one plugin, one embed, one analytics tag at a time. A throttled Lighthouse run saved with today's date turns the site feels slower now from a feeling into a comparison, and it costs three minutes a quarter.
Save the TTFB median in the same file. When you next change host, theme or PHP version, you will have something to measure against, and you will be able to say which change was responsible instead of guessing between three of them.
A fast floor under a site you keep light
Text sites do not need power; they need a platform that gets out of the way. Cached pages come off a LiteSpeed engine in the server, storage is NVMe on every tier, and the origin is in London, 5 to 15 ms from a UK reader.
The rest of a HostingFast account is there so you can check the claim: SSH access, per-site PHP switching, real logs, and a resource graph that shows CPU and memory against your limits rather than a green tick.
- Cached pages served before PHP starts, on every tier
- NVMe storage on the entry plan, not just the top one
- SPF, DKIM and DMARC configured, MailChannels on outbound mail
- Free migration, so the before-and-after test costs nothing
Why HostingFast
Standard on every plan
A server that is never the excuse
Prose caches perfectly, so LiteSpeed on NVMe means a slow page of text is always something you can fix in the theme.
Evidence for your own claims
SSH, real logs and per-site PHP switching, so the writer who sells clarity can produce numbers rather than adjectives.
Enquiries that reach you
SPF, DKIM and DMARC configured with MailChannels on outbound mail, so a project enquiry never dies in a spam folder.
One-click installs, no build chain
Softaculous puts WordPress and 240+ other applications on the account in a click, so publishing starts the same evening.
Free migration, free comparison
Our engineers move the site at no charge, which makes measuring your old host against this one a ten-minute job.
No setup fee, flat renewal
Nothing to pay to join and no year-two step, so the cost of your own site stays a line you can forget about.
Quick Start
From order to online
- 1
Run one throttled pass and read the blockers
Lighthouse, Mobile, Slow 4G, three runs. Note LCP, CLS and every render-blocking resource. On a text site that list is mostly fonts.
- 2
Cut the font stack, then re-measure
Two weights, font-display: swap, a fallback with similar metrics. Re-run the identical three passes and compare the medians.
- 3
Send yourself an enquiry
Submit the form with a real address, read the headers, confirm SPF, DKIM and DMARC all check out on two different mail providers.
Built In
Loaded onto every plan
- LiteSpeed cache in the server, so prose is served prebuilt
- NVMe storage on every tier for the uncached paths
- Per-site PHP version switching from the control panel
- Daily backups with restores you run yourself
- SPF, DKIM and DMARC configured for your sending domain
- Mailboxes on your own domain with IMAP, POP, SMTP and webmail
- Softaculous installs WordPress and 240+ applications in one click
- Built-in WebP conversion for the occasional screenshot
- Free migration by our engineers, normally inside a day
- No setup fee, and a renewal at the rate you ordered at
Frequently Asked
What people ask us most often
My site is nothing but text. Why is LCP over three seconds?
Look at the render-blocking list in a throttled Lighthouse run. On a text-only site it is nearly always web fonts: several faces at several weights, loaded before anything paints. Set font-display: swap, cut to the weights you actually use, and re-run the same three passes. That single change usually moves LCP more than any plan upgrade would.
Should portfolio samples be PDFs or web pages?
Pages, and the performance argument is the strongest one. A PDF is a download, a wait and a pinch-to-zoom on a phone, and none of it is measurable in the metrics a prospective client sees. A sample published as a page paints in about a second, gets indexed, and can be timed with curl to prove it.
How do I make sure the fallback font does not make text jump?
Watch Cumulative Layout Shift in the same Lighthouse run. Pick a fallback with similar metrics to your web font, and adjust size-adjust or letter-spacing until the swap is undramatic. It is a ten-minute job and it stops you trading one bad metric for another, which is the usual mistake here.
Do I need caching on a site this small?
It comes with the platform, so the question is really whether you have added a second one. LiteSpeed is a cache engine in the server; a plugin is its control surface. Two caching plugins do not cache twice, they conflict, and on a small site the symptom is usually a page that will not update when you edit it.
Keep reading
Community Groups — Hosting Guide
A volunteer-run site with the same discipline: keep it light, and hand it over documented.
Letting Agents — Hosting Guide
A property site where the weight is photography rather than fonts, but the method is identical.
How to Test Your Website Speed
The step-by-step version of the timing method used throughout this page.
Ecommerce Hosting — Built for Copywriters
Store-grade hosting if the writing business ever starts selling products directly.
Domain Names
Register or move the name your samples live on, with the first year free on annual plans.
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.
Fix the fonts first.
One throttled Lighthouse run names the blocking assets — and the cache underneath is already doing its part.
View Ecommerce Hosting — Built for Copywriters plans