Maintenance and performance after launch
Websites and applications depend on changing hosting, libraries, APIs and content. Maintenance should define checks, ownership and included costs.
Backups need restoration checks
Define scope, frequency and retention. Files and database must correspond. An untested backup does not show how quickly you can recover.
Updates and monitoring
Check versions, compatibility and key functions after updates. Monitoring detects outages, but someone must receive alerts and have an agreed response window.
Measure speed in context
Large images, third-party scripts, server behaviour and queries can delay loading. Use repeatable tests and field data where available. A lab score does not represent every visitor.
Content and evolution
Update inaccurate services, contact details and pages. Measure forms and conversions. Separate maintenance from new functionality and document support limits.