Last updated: August 2026 | By CareWP Team
If you have ever booked an hour of WordPress support, you have probably wondered exactly what that hour buys you. Is it enough for a plugin update and a content change, or does it disappear the moment something goes wrong? This guide breaks down what typically fits into an hour of WordPress maintenance, why the work is tracked in 15-minute blocks, and how to make sure your hour goes further.
Quick Answer
An hour of WordPress maintenance usually covers two to four smaller tasks, such as a round of plugin and theme updates, a content change, and a minor fix, tracked in 15-minute blocks. Some of that time goes toward understanding the request before any work starts, so a clear, detailed request leaves more time for the actual fix.
CareWP is a Perth-based WordPress maintenance service that tracks and delivers maintenance work in exactly this way, so this is a question our clients ask often.
Why Maintenance Work Is Billed in 15-Minute Blocks
Most professional WordPress maintenance providers, CareWP included, track time in 15-minute increments rather than billing a flat hour for every request. This matters for two reasons.
First, WordPress work is rarely one uniform task. A single hour might cover a quick text edit, a plugin update, and a small CSS fix, each taking a different amount of time. Fifteen-minute blocks let that hour be split accurately across several small jobs instead of forcing every request into an all-or-nothing hour.
Second, it keeps billing honest in both directions. A five-minute image swap is charged as one 15-minute block, not a full hour, and a task that runs long is tracked in the increments it actually used. You are not paying for time nobody spent, and the engineer is not squeezed into an unrealistic estimate.
What Fits Into a Typical Hour
The table below shows realistic technical and content tasks and roughly how many 15-minute blocks each one takes. Actual timing varies by site complexity, hosting environment and how many plugins are involved.
| Time | Technical tasks | Content tasks |
|---|---|---|
| 15 minutes | Update a handful of plugins, restart a stalled cron job, check an error log for one issue | Swap an image, fix a typo or broken link, update a phone number or opening hours |
| 30 minutes | Core, theme and plugin updates tested on staging, resolve a plugin conflict, clear a caching issue | Update a landing page section, add a short blog post from supplied text, adjust a form’s fields |
| 45 minutes | Investigate and patch a security warning, fix a broken layout after an update, restore from backup after a small error | Format and upload a longer blog post with images, rebuild a simple page section, update several pages with the same change |
| 60 minutes | Full monthly update round with staging tests and a report, diagnose and fix a moderate performance issue, resolve a malware flag on a single file | Publish a full page of new content with SEO basics, restructure a menu across the site, batch-update pricing or product details |
Most one-hour sessions combine two or three of these rather than one long task, which is why a plugin update round plus a content change plus a small fix is a common way to fill an hour.
Why Some of the Hour Goes to Understanding the Issue
The clock does not start only once the fix begins. Time spent understanding what you actually need, reading the request, checking the site, reproducing the issue and confirming the scope, is part of the work and part of the hour.
This is where the request itself makes the biggest difference. A request like “the contact form is broken” takes longer to resolve than one that says “the contact form on /contact/ shows a blank white page after clicking submit, started after yesterday’s plugin update.” The second version removes a round of investigation entirely.
When a request lacks that context, the engineer has to stop and ask for clarification before any fix can begin. Every round of back-and-forth (message sent, reply awaited, clarification given) adds delay on top of the time it takes, and it often pushes a task that should have taken 15 minutes into a much longer one. In the worst case, a fix is attempted on the wrong assumption, has to be undone, and the real issue only gets tackled in a second session.
How to Get the Most Out of Your Maintenance Hour
A little detail up front saves time on both sides. Before sending a request, include:
- The exact page or URL affected, not just “the website.”
- What you expected to happen versus what actually happened.
- When it started, and anything that changed around that time, such as a plugin update or a new form submission.
- Screenshots or screen recordings if the issue is visual.
- Priority, so the engineer knows whether it is urgent or can wait for the next scheduled session.
Bundling small, unrelated requests together in one message (rather than sending them one at a time over several days) also helps an engineer plan the hour efficiently and get more done in the time available.
When an Hour Is Not Enough
Some jobs genuinely need more than an hour, and a good provider will tell you that upfront rather than rushing a partial fix. Full site recovery after a hack, a major redesign, migrating hosts, or building new functionality from scratch are examples of work that gets scoped and quoted separately rather than squeezed into a single maintenance session.
CareWP’s ongoing care plans, from Essential to Enterprise, are designed to absorb the regular 15-minute-to-1-hour work as part of routine coverage, while larger jobs such as malware removal or full site recovery are handled as their own scoped engagement. You can see how the tiers differ on our pricing page.
Frequently Asked Questions
How many WordPress tasks can be done in one hour?
Typically two to four smaller tasks, such as a round of plugin updates, a content change and a minor fix. Exact numbers depend on site complexity and how much investigation each task needs.
Why is WordPress maintenance work billed in 15-minute blocks?
Fifteen-minute blocks let providers split an hour accurately across several small tasks instead of billing a flat hour for every request, so a five-minute fix is not charged as a full hour and a longer task is tracked in the time it actually took.
Does time spent understanding my request count toward the hour?
Yes. Reading the request, checking the site and confirming the scope is part of the work. Clear, detailed requests reduce this time; vague ones that need follow-up questions use more of the hour before any fix begins.
What should I include in a support request to save time?
The exact page or URL, what you expected versus what happened, when the issue started, a screenshot if it is visual, and how urgent it is. This removes a round of back-and-forth before the fix can start.
What WordPress work does not fit into a single hour?
Full site recovery after a hack, major redesigns, host migrations and new custom functionality are usually scoped and quoted as their own project rather than fitted into a routine maintenance hour.
Get Maintenance Time That Is Used Well
An hour of WordPress maintenance goes furthest when the request is clear and the provider tracks time honestly. CareWP pairs every client with a dedicated Perth-local engineer who works in 15-minute blocks, so you only pay for the time your site actually needs.
If you would like to know how much ongoing time your site typically needs, get in touch with CareWP for a straightforward recommendation, or see our WordPress maintenance Perth page for local plans and pricing.
