The honest answer to "how long does website maintenance take?" is: it depends on what kind of site you have. A five-page brochure site and a busy online store are very different jobs. Here is how to think about the time, so you can plan for it.
Part of it is automatic
A good share of maintenance runs on its own. Uptime monitoring checks your site around the clock. Backups run on a schedule. Security scans run daily or weekly. A person only steps in when something needs attention, so this part costs very little of anyone's time month to month.
Part of it needs a person
Other work needs a careful human: applying updates and checking that nothing broke, reading the security and speed reports, testing a restore from a backup, and fixing whatever comes up. On a small site this is typically an hour or two a month. On a larger or busier site it grows, because there are more plugins to update and more pages to check.
Your requests are the rest
Most of the time a site owner actually notices is spent on changes: a new opening hour, a fresh product, a banner, a page that needs a new section. These are small individually, but together they are often the largest share of a month.
How long common jobs take
These are typical times for everyday requests. They are planning figures, not promises, because a job on a tidy site takes less time than the same job on one with years of leftovers.
| Request | Typical time |
|---|---|
| Update opening hours, prices or contact details | 15 minutes |
| Add a blog post or a product you send us | 30 minutes |
| Swap images or fix text across several pages | 30 minutes |
| Menu, footer and widget changes | 15 to 30 minutes |
| Adjust colours, spacing or fonts | 30 minutes |
| Publish a new page from an existing template | 1 hour |
| Install and set up a plugin, like a booking form | 1 hour |
| Connect analytics, email or your CRM | 1 to 2 hours |
| Fix a mobile layout or browser bug | 30 minutes to 2 hours |
The routine, by how often it comes round
| How often | What happens | Who does it |
|---|---|---|
| Every day | Uptime, form and backup checks, and a security scan | Automatic, with a person alerted if something fails |
| Every week | Updates applied and checked, security log reviewed, broken links found | A person |
| Every month | A restore test, a full form and checkout test, accounts reviewed, a report written | A person |
| Every quarter | Speed and content review, hosting and PHP version check | A person |
| Every year | Renewals, access review, a longer improvement list | A person, with you |
You can print the whole routine as a list: the website maintenance checklist.
A rough guide to hours a month
- A small brochure or local service site: a couple of hours a month, including a few small changes.
- A busy business site or a site with many pages: around six hours, because there is more to update, check and change.
- An online store or a site that earns most of your revenue: twelve hours or more, because checkout testing, staging and quicker turnaround add time.
What makes it take longer
- Many plugins, and plugins that overlap.
- Custom code that nobody documented.
- No staging copy, so every update needs extra care.
- Slow or limited hosting.
- Requests that arrive in pieces, or without the text and images.
Doing it yourself or handing it over
| Doing it yourself | With a maintenance team | |
|---|---|---|
| Setting up the tools | You research, buy and configure them | Already in place |
| Finding the time | It competes with running the business | It is scheduled for you |
| When something breaks | You diagnose it, often on a deadline | Someone who has seen it before looks first |
| Knowing it was done | You remember, or you do not | A monthly report records it |
A month in the life of a small site
Take a five-page business site on a modest plan. In the first week the updates are applied and checked, and the security and backup reports are read. In the second week you send three small requests: a new price list, a team photo and a changed opening hour. They are done in a short sitting. In the third week nothing happens, and that is fine, because monitoring is watching. In the fourth week a restore is tested and the month's report is written. In total a person spent a couple of hours, and you spent about ten minutes sending the requests.
The life of one request
| Stage | What happens | Where the time goes |
|---|---|---|
| You send it | You describe the change and attach any text or images | Minutes, if the request is complete |
| It is picked up | Someone reads it and asks anything that is unclear | Depends on the reply promise of your plan |
| The work | The change is made, on staging first where your plan includes it | The job time in the table above |
| The check | The result is looked at on desktop and phone | A few minutes |
| Done | You are told, and the time is recorded against your hours | Minutes |
How long a WordPress update takes
The update itself is quick. A plugin update often applies in under a minute. What takes time is everything around it: confirming a recent backup exists, testing on a copy where one is available, checking pages and forms afterwards, and looking again once it is live. For a handful of routine updates that is a modest sitting. For a major version of WordPress or a store with many plugins, allow longer, and expect the first update after a long gap to take much more time than a regular one, because the site has several versions to catch up on.
Using your hours well
- Batch small changes. Five changes sent together are quicker than five sent apart.
- Send everything at once. Text, images, links and where each should go.
- Say what good looks like. A screenshot or an example saves guessing.
- Plan the big jobs. A new page from a template is an hour. A new feature is a project and should be scoped first.
Signs you need more hours
- You run out every month and keep postponing requests.
- Changes are urgent more often than not.
- The site is changing faster than the plan assumed, for example in a sale or a launch.
It is simple to move up a plan, and just as simple to move down when the busy period ends.
Estimating a larger job
Some work is a project, not upkeep: moving to a new host, rebuilding a section, adding a feature. The time depends on a few things you can usually describe in advance.
| Factor | Why it changes the time |
|---|---|
| How much content or data moves | More pages, products or users mean more to check |
| How many plugins and integrations are involved | Each one is another thing that can behave differently |
| Whether the site is well documented | Unknown custom code takes time to understand |
| Whether a staging copy exists | Without one, every step needs extra care |
| How quickly decisions and content arrive | Waiting for answers is often the longest part |
What you can do to keep it short
- Gather the text, images and logins before you start.
- Name one person who can make decisions quickly.
- Say what must be ready by when, and why.
- Test the result promptly, and report problems in one list.
How to spot a quote that underestimates
A quote that is far shorter than the others is not always better. Ask what it assumes: that the content is ready, that nothing conflicts, that the site is tidy. If the answer is yes to all of those, ask what happens when one is wrong.
What is a maintenance window?
A maintenance window is a short, planned period when a change is made and the site may be briefly unavailable or slower. Choose a quiet hour for your visitors, tell people in advance if the site will be down, and keep it as short as the work allows. If you run a Shopify store and need to close it for a short time, see how to put a Shopify store in maintenance mode.
Why a pool of hours beats a task list
Fixed task lists make providers say "that is not included" when something new comes up. A pool of hands-on hours works the other way around: you decide what to spend it on. Our plans include 2, 6 or 12 hands-on hours a month, tracked in 15-minute blocks.
Want a second opinion on what you need?
Our free coverage check shows which parts of maintenance you already have and which are missing, and helps you see which plan size fits.
