Publishing stack · Beginner · an afternoon to set up properly
How to start a blog on your domain — Build the Archive That Will Not Slow Down in Two Years
Setting the blog up takes an afternoon; the decisions you make this afternoon are the ones you will be writing redirect rules about in two years.
The short answer
Get the URL structure and the image pipeline right on day one, because those are the two decisions that are expensive to reverse. Post-name permalinks avoid the redirect map that a dated or category-based structure eventually forces on you, and a WebP conversion step keeps every future post cheap without you thinking about it again.
Everything after that is about what happens at scale. A blog with ten posts is fast whatever you do; the same blog at three hundred posts has archive queries, a related-posts plugin running an unindexed lookup on every page view and a search page nothing can cache. This runbook sets the structure up so those problems never start.
By the HostingFast team · Reviewed 24 August 2026
Beginner
Assumed skill
5
Numbered stages
Free
Support, billed at
Proven
Run on the platform we operate
Aimed at someone who will end up with a few hundred posts and would rather not rebuild the site to get there. Publishing on your own domain and your own install means the archive, the URLs and the search authority accrue to you — and so do the performance decisions.
Two things to fix before the first post: the permalink structure, and how images get processed on upload. Both are cheap now and awkward later, which is the entire reason they come first on this page rather than last.
Set the URL once, because the redirects are forever
Post-name permalinks give you clean, stable URLs with no date or category baked in, which means recategorising a post later does not change its address. A dated structure looks tidy for a year and then makes every piece of evergreen content look stale in the search results, and changing it afterwards means a redirect rule for every post you have written.
Decide the category taxonomy now too, and keep it small. Categories are the paths readers and crawlers walk; tags proliferate into hundreds of thin archive pages that dilute your own signal. Four or five real categories will still be right in three years.
What actually gets slow as the archive grows
Three things, in this order. Related-posts plugins that run an unindexed meta query on every single page view. Archive and category pages that fetch full post objects when they only render a title and an excerpt. And the internal search page, which is dynamic by definition and therefore never served from cache.
None of those are visible at twenty posts. Profile a category page with Query Monitor once you are past a hundred and the offender is usually named in the first line of output. Cache the archives, exclude search, and either index what the related-posts plugin queries or replace it with a hand-curated list.
An image pipeline you never think about again
Every post is going to carry images, so the processing has to be automatic. WebP conversion is built into the platform at no extra cost, which takes the largest slice off page weight before any plugin is involved. Add explicit width and height attributes in the theme so the browser reserves space and your layout shift stays at zero.
Then set a size limit for yourself on upload. A 4,000-pixel photograph resized in the browser still transfers at full weight, and no amount of caching downstream recovers those bytes. Resize before upload, let the platform convert the format, and the pipeline costs you nothing per post from then on.
Ship on a cadence the stack can support
Weekly and sustained beats twenty posts in a fortnight and silence afterwards, and it also gives you a reason to look at the numbers regularly. Once a month, check which posts get traffic, which templates are slow on mobile, and whether the archive pages are still being served from cache after your last plugin addition.
The platform half of this is already handled: WordPress and 400+ other applications install in one click, LiteSpeed caching is compiled into the server, backups run daily with restores you run yourself, and staging clones exist for trying a plugin on a copy before it reaches your live archive.
The stack the archive will sit on
WordPress installs in one click alongside 400+ other applications, on NVMe storage with LiteSpeed compiled into the web server. The caching layer most blogging guides tell you to install is already the default here, which is why this runbook spends its time on structure instead.
Order an annual plan and the first year of your domain registration costs you nothing.
- One-click WordPress, plus 400+ other applications
- LiteSpeed caching compiled in, so archives are served from cache
- WebP conversion built into the platform at no extra cost
- Year one of the domain free when you order annually
Why HostingFast
Standard on every plan
URLs you will not redirect
Post-name permalinks and a small category set, decided before the first post rather than after the hundredth.
Named the things that get slow
Related-post queries, archive templates and internal search — in the order they start costing you, with the fix for each.
An image pipeline on autopilot
WebP conversion at the platform plus explicit dimensions in the theme, so page weight and layout shift both stay handled.
Profiling built into the routine
A monthly look at Query Monitor on a category page catches the plugin that quietly added a query per view.
Caching already in the server
LiteSpeed is compiled in rather than added by plugin, so archives are cached before you configure anything.
Rehearsal space for plugins
Staging clones and daily backups mean a promising plugin gets tested on a copy rather than on your live archive.
Quick Start
From order to online
- 1
Install WordPress and fix the permalinks
One click from the installer, then set post-name permalinks before you publish anything. Changing this later means a redirect rule for every existing post.
- 2
Decide four or five categories
A small deliberate taxonomy, and restraint on tags. Hundreds of thin tag archives dilute your own signal and give crawlers busywork.
- 3
Set up the image pipeline
Resize on upload, let the platform's WebP conversion handle the format, and make sure the theme emits width and height so nothing shifts.
- 4
Confirm archives are being cached
Load a category page and read the cache header. Archives are the pages that grow expensive, so they are the ones that must be served from cache.
- 5
Profile once you pass a hundred posts
Query Monitor on a category page and on a single post. Related-posts plugins and unindexed meta lookups show up immediately in that output.
Built In
Loaded onto every plan
- WordPress and 400+ other applications installed in one click
- LiteSpeed caching compiled into the server, not bolted on by plugin
- Built-in WebP image conversion at no extra cost
- NVMe SSD storage on every tier, including the entry plan
- Staging environments for rehearsing a change before it ships
- Daily backups on every plan, with restores you run yourself from the panel
- Year one of your domain free when you order annually
- Per-site PHP version switching from the control panel
- WordPress Toolkit, with updates handled for you
- Human support on duty every hour of every day
Frequently Asked
What people ask us most often
Which permalink structure avoids a redirect map later?
Post name. It contains nothing that changes — no date to make evergreen content look stale, no category to break when you recategorise. A dated or category-based structure works fine until the day you want to change it, at which point you owe a redirect rule for every post ever published and a fortnight of watching the 404 log.
What starts getting slow as the archive grows past a hundred posts?
Related-posts plugins running an unindexed meta query on every view, archive templates fetching full post objects to render an excerpt, and the internal search page, which is uncacheable by nature. Profile a category page with Query Monitor and the offender is usually named in the first line of output.
Does a related-posts plugin really cost a query per page view?
Many of them cost several, and on a large archive those queries are frequently unindexed. Check with Query Monitor on a single post: if a related-posts lookup appears near the top of the duration list, either index what it queries, switch it to a cached or pre-computed mode, or curate the links by hand in the post.
Does a text-heavy blog need a CDN?
Usually not if the audience is near the origin. Our origin is in London, so a UK or Irish readership is already at 5–15 ms and an edge has almost nothing to win. Cached HTML from LiteSpeed does most of the work; measure the round trip from your largest audience region before adding a layer.
Keep reading
How to Register a Domain Name
Check the name, pick the ending and get it registered, with the DNS control you will need afterwards — beginner, roughly 10 minutes.
How to Read Your Website Statistics
Read traffic straight from the server's own logs, with no tag, no script and no consent banner in the way — beginner, roughly 20 minutes.
Addon Domain (Glossary)
How a second site sits inside one account, and what it shares with the first.
Domain Names
Search, register and transfer names — year one free when you order annual hosting.
cPanel Reseller Hosting
The industry-standard panel scaled for resellers, with WHM included.
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.
Put the archive on cached NVMe.
One-click WordPress, LiteSpeed compiled into the server, WebP conversion included, and year one of the domain free on annual plans.
View Domain Names plans