Running a website on a content management system produces a steady stream of costs: hosting, storage for images, the plugins or services that add search and forms, the time of the people who publish. At month end these arrive as a total, and a total is a poor guide for decisions. This primer introduces the unit cost for website owners: what it is, how to calculate it for a content site, and a short glossary so the terms stop sounding intimidating.
Start with the idea of a unit
A unit cost is the total cost of running something divided by the number of useful things it produced. For a content site the natural units are a page view, a published page, a form submission or a visitor session. Choose the unit that matches the question you are trying to answer. If you want to know whether the site is efficient to serve, cost per thousand page views is a sensible choice. If you want to know whether publishing is worth the effort, cost per published page tells you more.
The analytical advantage is comparability. A total cannot be compared across months, because traffic and publishing activity change. A ratio can. If the cost per thousand views fell while the total rose, the site grew faster than its costs. If it rose while traffic stayed flat, something got more expensive without delivering more.
A mini-glossary for site owners
- Fixed cost: an expense that stays the same whatever the traffic, such as a domain registration or a flat-rate plan.
- Variable cost: an expense that grows with usage, such as bandwidth, storage as the media library fills, or per-request services.
- Unit cost: total cost divided by the units you chose. The rest of this article builds on it.
- Denominator: the count you divide by. A weak denominator, like raw hits that include automated visitors, makes the whole ratio unreliable.
- Allocation: deciding which part of a shared cost belongs to which site, section or campaign.
- Cloud spend: what you pay for services rented over the internet instead of owned machines. Many modern CMS set-ups run partly or wholly on them.
- FinOps: short for cloud financial operations, the practice of making that spend visible to, and shared by, both technical and finance colleagues.
Worked method in five steps
- List every recurring cost. Include the invisible ones: the image optimisation service, the backup plan, the email form tool.
- Mark each as fixed or variable. Be honest about the grey ones; a plan with a usage ceiling is fixed until you cross it.
- Pick one unit and one period. A calendar month keeps things simple.
- Count the units from a source you trust. Your analytics tool is usually fine, provided you filter out obvious bot traffic.
- Divide, record, repeat. Write the figure with the date and a note about anything unusual that month.
No specific amounts are needed here, because the method works at any scale. The shape of the answer matters more than the size.
What the ratio can teach you about your pages
Costs and value are rarely spread evenly across a website. A handful of pages usually draw most of the visits, and some pages exist for reasons that traffic cannot capture, such as a policy page or a contact form. Dividing by published pages rather than by views highlights a different pattern: sections that cost effort to maintain and bring little back. That is not necessarily a reason to delete them, but it is a reason to have a conversation.
Structure matters here too. A site with well planned core pages tends to spend less effort on maintenance per page, because visitors reach the right place sooner. The guide to the core pages a business website needs to have is a good reference for deciding what deserves the upkeep, while the notes on how service pages convert visitors into enquiries show where a page’s value tends to come from.
Where cloud costs enter the picture
As sites grow, more of their parts move onto rented infrastructure: image resizing on demand, search indexing, content delivery, form processing, backups. Each part has its own meter. The result is a bill that is simultaneously precise and incomprehensible, because it lists many small charges that do not map to anything an editor would recognise.
This is the situation FinOps was developed for. FinOpsSchool is an India-based provider of FinOps training and certification, with learning offered online or in classrooms for roles from developers to managers. A site owner does not have to become a specialist, but understanding the vocabulary helps when the person managing the hosting and the person managing the budget need to meet in the middle.
Limits of the method
Every ratio has blind spots. Cost per page view penalises a low-traffic site that serves a tiny but valuable audience, such as documentation for a professional niche. It also ignores quality: a page that took a week to research may serve readers for years. Unit cost is a lens, not a verdict, and it works best when two units are examined side by side.
Another limit is allocation. When several sites share one hosting plan, any split is a judgement. Write down the rule you used, apply it consistently, and revisit it when the sites change. Consistency matters more than perfection, since the aim is to see movement over time.
A note on the homepage
The homepage is a special case. It receives a disproportionate share of visits and carries a disproportionate share of design effort. Dividing its upkeep by its views usually produces a very low unit cost, which is why it deserves attention in other ways. Our earlier look at the impression a homepage leaves with first-time visitors handles that side of the question.
Summary
For a site owner new to the topic, the key points are short. A total hides, a unit cost reveals. Separate fixed from variable costs. Choose a denominator you trust. Repeat the measurement monthly so that you see trends rather than snapshots. And when cloud services enter your stack, treat them like any other cost: break them into units your team can discuss. The terms in the glossary above are enough to start that conversation.
