Most website maintenance contracts are line items — fix what breaks, patch what's exposed. The operating-layer version treats the site as the surface where revenue happens. Different work, different price.
Most website maintenance contracts are line items — fix what breaks, patch what's exposed. The operating-layer version treats the site as the surface where revenue happens. Different work, different price.
Website maintenance is one of those line items that gets quoted at £150/month and forgotten about. The contract reads "monthly updates, security patches, backup management" — vague enough that nobody can complain when nothing visible happens and concrete enough that a finance team approves it without thinking.
That's maintenance-as-line-item. It exists. It's not the same as maintenance-as-operating-layer, and the two have completely different cost shapes and outcomes.
Website maintenance covers everything that keeps a site running between major redesigns: security patches, plugin/theme updates, uptime monitoring, backup verification, performance tuning, broken-link fixes, content updates, and SEO hygiene.
Two flavours:
For most ecommerce sites the line-item version is dangerously cheap — it covers the visible failure modes (downtime, hacks, broken checkout) and misses the silent ones (page speed degrading by 8% per quarter, schema markup drifting, image weights creeping up, conversion rate quietly declining).
| Task | Frequency | What it doesn't catch |
|---|---|---|
| Plugin / theme updates | Monthly | Compatibility regressions, deprecation warnings. |
| Security patches | As-needed | Custom-code vulnerabilities, third-party script risks. |
| Backup verification | Weekly | Whether the backup actually restores (most don't test). |
| Uptime monitoring | Continuous | Slow-but-up. Core Web Vitals degradation. |
| Broken link fixes | Quarterly | Stale internal redirects, orphan pages. |
| Basic content updates | Per-request | SEO impact, structured-data alignment. |
None of these are wrong. They're table-stakes. The problem is when they're the only thing happening to the site, and the team assumes that means the site is in good shape.
Composite of 30 DTC sites on line-item-only maintenance. Each metric drifts slowly; none triggers an alarm.
Largest Contentful Paint (LCP) creeps up as images get added, third-party scripts accumulate, and JavaScript bundles bloat. Without an active maintenance layer that audits and optimises, LCP typically drifts up 8–15% per year. Eventually you cross Google's 2.5s threshold and the page experience signal flips from "Good" to "Needs improvement" — and you lose ranking.
Forms break, payment integrations update, browsers ship updates that affect specific UI behaviour. Without conversion-rate monitoring tied to maintenance, you find out about a broken checkout by reading support tickets. Operating-layer maintenance includes a weekly auto-test of the checkout flow on top browsers.
Schema markup drifts when product templates get updated. Internal link counts shift when categories are reorganised. Sitemaps get out of sync with reality. Without monthly SEO hygiene, you lose 3–8% of organic traffic per year to slow drift that nobody triggered on purpose.
Stale "About" page from 2021. Old team photos. Outdated stats. None of these break anything. All of them quietly reduce trust. Operating-layer maintenance includes a quarterly content sweep.
Shopify pushes new APIs every quarter. WordPress security patches need testing before deployment. Custom React/Next.js builds have their own dependency-update cadence. Each platform has work that's invisible until it's not.
| Tier | Monthly cost (UK) | Hours included | Coverage |
|---|---|---|---|
| Bare-minimum (line item) | £100–£250 | 2–4h | Patches, backups, uptime. |
| Active | £400–£900 | 5–10h | + basic performance, content updates. |
| Operating-layer (small site) | £1,500–£3,000 | 15–25h | + CRO, SEO hygiene, weekly checkout tests. |
| Operating-layer (mid) | £3,000–£8,000 | 30–60h | + structured A/B testing, schema work, integration debugging. |
The £150/month "maintenance" quote is real. It's also doing roughly £150 of work. The difference between that and a £3,000 retainer isn't "they're charging more for the same thing" — they're doing different work.
Most small ecommerce businesses don't need full operating-layer maintenance. They need active maintenance — somewhere in the £400–£900 range — plus an annual or semi-annual deep audit that catches the drift. Operating-layer makes sense once revenue exceeds roughly £3M and the site is doing enough volume that 4% conversion-rate decline costs more than the retainer.
Google's Core Web Vitals documentation is the right starting reference for what should be monitored regardless of tier.
Plugin updates, security patches, uptime monitoring, backup verification, occasional broken-link fixes, and minor content updates. Anywhere from £100–£400/month depending on platform complexity and response-time SLA.
Continuous monitoring (uptime, security alerts) runs 24/7. Active maintenance work runs monthly. Performance audits run quarterly. Full site audits run annually. Stretching any of those longer is where drift creeps in.
Shopify handles the hosting, security, and core platform. You don't need maintenance for those. You DO need active work on theme customisations, app updates, third-party integration drift, and the bespoke logic in your store. £500–£1,500/mo is typical for a mid-sized Shopify store.
No. Hosting keeps the server running. Maintenance keeps the site running. Most modern setups (Vercel, Netlify, Shopify, Webflow) include hosting; maintenance is a separate workload focused on the code, content, and integrations.
Yes if you have a developer with platform-specific experience + 5–10 hours/week to allocate. Most small ecommerce businesses don't have either, which is why retainers exist. Hybrid (in-house content updates, outside dev for code-level work) is common.
Qwrki runs the website as part of the operating layer — same team that maintains the site also runs the analytics that measures it, the SEO that drives traffic to it, and the lifecycle that monetises the visitors. There's no separate "maintenance" line item because keeping the site healthy is part of keeping the operation healthy. Book a call — we'll audit your current setup against the drift chart above.
Site speed fixes ranked by effort against payoff: images, scripts, apps, fonts and hosting. Why speed moves conversion and where to start this week.
Shopify vs WooCommerce, compared on what actually differs: who carries the operational burden, the real cost shape, flexibility, and when each one honestly wins.
A website migration SEO checklist: redirect mapping, pre-launch benchmarks, launch-day verification and the monitoring window that catches problems early.
Website maintenance is one of those line items that gets quoted at £150/month and forgotten about. The contract reads "monthly updates, security patches, backup management" — vague enough that nobody can complain when nothing visible happens and concrete enough that a finance team approves it without thinking.
That's maintenance-as-line-item. It exists. It's not the same as maintenance-as-operating-layer, and the two have completely different cost shapes and outcomes.
Website maintenance covers everything that keeps a site running between major redesigns: security patches, plugin/theme updates, uptime monitoring, backup verification, performance tuning, broken-link fixes, content updates, and SEO hygiene.
Two flavours:
For most ecommerce sites the line-item version is dangerously cheap — it covers the visible failure modes (downtime, hacks, broken checkout) and misses the silent ones (page speed degrading by 8% per quarter, schema markup drifting, image weights creeping up, conversion rate quietly declining).
| Task | Frequency | What it doesn't catch |
|---|---|---|
| Plugin / theme updates | Monthly | Compatibility regressions, deprecation warnings. |
| Security patches | As-needed | Custom-code vulnerabilities, third-party script risks. |
| Backup verification | Weekly | Whether the backup actually restores (most don't test). |
| Uptime monitoring | Continuous | Slow-but-up. Core Web Vitals degradation. |
| Broken link fixes | Quarterly | Stale internal redirects, orphan pages. |
| Basic content updates | Per-request | SEO impact, structured-data alignment. |
None of these are wrong. They're table-stakes. The problem is when they're the only thing happening to the site, and the team assumes that means the site is in good shape.
Composite of 30 DTC sites on line-item-only maintenance. Each metric drifts slowly; none triggers an alarm.
Largest Contentful Paint (LCP) creeps up as images get added, third-party scripts accumulate, and JavaScript bundles bloat. Without an active maintenance layer that audits and optimises, LCP typically drifts up 8–15% per year. Eventually you cross Google's 2.5s threshold and the page experience signal flips from "Good" to "Needs improvement" — and you lose ranking.
Forms break, payment integrations update, browsers ship updates that affect specific UI behaviour. Without conversion-rate monitoring tied to maintenance, you find out about a broken checkout by reading support tickets. Operating-layer maintenance includes a weekly auto-test of the checkout flow on top browsers.
Schema markup drifts when product templates get updated. Internal link counts shift when categories are reorganised. Sitemaps get out of sync with reality. Without monthly SEO hygiene, you lose 3–8% of organic traffic per year to slow drift that nobody triggered on purpose.
Stale "About" page from 2021. Old team photos. Outdated stats. None of these break anything. All of them quietly reduce trust. Operating-layer maintenance includes a quarterly content sweep.
Shopify pushes new APIs every quarter. WordPress security patches need testing before deployment. Custom React/Next.js builds have their own dependency-update cadence. Each platform has work that's invisible until it's not.
| Tier | Monthly cost (UK) | Hours included | Coverage |
|---|---|---|---|
| Bare-minimum (line item) | £100–£250 | 2–4h | Patches, backups, uptime. |
| Active | £400–£900 | 5–10h | + basic performance, content updates. |
| Operating-layer (small site) | £1,500–£3,000 | 15–25h | + CRO, SEO hygiene, weekly checkout tests. |
| Operating-layer (mid) | £3,000–£8,000 | 30–60h | + structured A/B testing, schema work, integration debugging. |
The £150/month "maintenance" quote is real. It's also doing roughly £150 of work. The difference between that and a £3,000 retainer isn't "they're charging more for the same thing" — they're doing different work.
Most small ecommerce businesses don't need full operating-layer maintenance. They need active maintenance — somewhere in the £400–£900 range — plus an annual or semi-annual deep audit that catches the drift. Operating-layer makes sense once revenue exceeds roughly £3M and the site is doing enough volume that 4% conversion-rate decline costs more than the retainer.
Google's Core Web Vitals documentation is the right starting reference for what should be monitored regardless of tier.
Plugin updates, security patches, uptime monitoring, backup verification, occasional broken-link fixes, and minor content updates. Anywhere from £100–£400/month depending on platform complexity and response-time SLA.
Continuous monitoring (uptime, security alerts) runs 24/7. Active maintenance work runs monthly. Performance audits run quarterly. Full site audits run annually. Stretching any of those longer is where drift creeps in.
Shopify handles the hosting, security, and core platform. You don't need maintenance for those. You DO need active work on theme customisations, app updates, third-party integration drift, and the bespoke logic in your store. £500–£1,500/mo is typical for a mid-sized Shopify store.
No. Hosting keeps the server running. Maintenance keeps the site running. Most modern setups (Vercel, Netlify, Shopify, Webflow) include hosting; maintenance is a separate workload focused on the code, content, and integrations.
Yes if you have a developer with platform-specific experience + 5–10 hours/week to allocate. Most small ecommerce businesses don't have either, which is why retainers exist. Hybrid (in-house content updates, outside dev for code-level work) is common.
Qwrki runs the website as part of the operating layer — same team that maintains the site also runs the analytics that measures it, the SEO that drives traffic to it, and the lifecycle that monetises the visitors. There's no separate "maintenance" line item because keeping the site healthy is part of keeping the operation healthy. Book a call — we'll audit your current setup against the drift chart above.
Site speed fixes ranked by effort against payoff: images, scripts, apps, fonts and hosting. Why speed moves conversion and where to start this week.
Shopify vs WooCommerce, compared on what actually differs: who carries the operational burden, the real cost shape, flexibility, and when each one honestly wins.
A website migration SEO checklist: redirect mapping, pre-launch benchmarks, launch-day verification and the monitoring window that catches problems early.
