Your website always online, secure and fast, with the MyTarh team watching over it 24/7
A website’s work does not end at delivery. That is when a new period begins, in which the site has to stay up, secure and fast. Website maintenance means someone regularly takes care of this: updating the CMS core, plugins and frameworks, backing up the site and keeping restores possible, monitoring uptime and speed, and acting on problems before your customers notice them.
Most site owners do not think about maintenance until something goes wrong: a blank white page instead of the site, a “Not secure” warning in the browser, a plugin that broke the contact form after an update, or a hacked site with no clean backup. None of these is sudden; each is the result of months without updates, backups or monitoring. Regular maintenance keeps the work small and manageable and stops it turning into a crisis. Updating a few plugins regularly is a small, routine task; updating a site that has not been touched for a year in one go can bring incompatibilities, errors and rewriting part of the site.
At MyTarh, maintenance starts with an initial audit: we review the current state of the site and fix existing technical and security issues before the contract begins. Then monitoring, automatic backups and alerts are set up, and ongoing work continues under a monthly contract. We offer three packages — Basic, Pro and Complete — which differ in update and backup frequency, the level of security monitoring and response speed; the table further down this page compares them. In all three, the work done on your site is reported to you regularly, so you know exactly what was done for the monthly fee and what state your site is in.
These six are the common consequences of leaving a website unattended. None happens overnight; they build up slowly until the day they show themselves:
When a security patch is released for the CMS core or a plugin, the details of the vulnerability become public too. From that moment, a site that has not been updated is a known target, and automated attack tools look for exactly these old versions. These tools do not distinguish between small and large sites; any site running a vulnerable version is a target.
Some plugins and themes are no longer updated by their developers. An old version gets no security patches and stops being compatible with newer versions of PHP or the site core; it has to be identified in time and replaced with a suitable alternative. The same applies to nulled (cracked) plugins and themes, which get no official updates and have no trustworthy source.
A site that has not been updated for months can no longer be updated with one click. Jumping several versions at once raises the risk of incompatibility and breakage, and work that could have been part of the monthly routine becomes a separate project. The longer the gap between updates, the harder it is to find which update caused the problem.
A backup is only worth something if it is complete, current and stored separately from the main server. A backup left on the same hosting is lost if that hosting fails or is hacked, and a backup whose restore has never been tested may turn out incomplete on the day you need it. Backups must include both the files and the database; one without the other does not bring the site back.
The database grows heavier over time, unoptimized images pile up and extra plugins increase server load. The slowdown arrives gradually and visitors usually notice it before the site owner does. It harms the user experience and also affects technical metrics such as Core Web Vitals, which Google takes into account when evaluating pages.
Without monitoring, a site can be down for hours, an SSL certificate can expire and the browser can show a “Not secure” warning, or the contact form can silently stop working so messages never reach you — without anyone knowing. In that case the first news usually comes from a customer who could not place an order or contact you; in other words, after the damage is done.
Updating the CMS, plugins and frameworks for security and performance
Automatic backups to a separate server, from weekly to real-time depending on the package
Regular scans for malware, intrusion attempts and vulnerabilities (from the Pro package)
Continuous speed monitoring and prompt fixes when the site slows down
Instant SMS and Telegram alerts when there is downtime or a problem
A full report on your site's health, security and performance
A full review of the site's current state and existing issues
Resolving existing technical and security problems before support begins
Setting up monitoring, automatic backups and alerts
Regular updates, bug fixing and ticket responses
A clear monthly report of all activity
Pick the package that fits your business
For small websites
For business websites
For high-traffic websites
The packages differ in how often maintenance tasks are done and how quickly a problem is dealt with:
| Criterion | Basic | Pro | Complete |
|---|---|---|---|
| Monthly fee | $149/month | $349/month | $690/month |
| Updates | Monthly | Weekly | Immediate |
| Backups | Weekly | Daily | Real-time |
| Monitoring and security | Uptime monitoring; no security monitoring | Security monitoring and free SSL | Security WAF and free CDN |
| Response time | No urgent response | 4-hour response | 2-hour response with a guaranteed SLA |
| Reporting and communication | Monthly report and 3 support tickets per month | Weekly report and unlimited tickets | Real-time reporting and a dedicated account manager |
| Best for | A small brochure site that rarely changes | A business site that receives orders or requests every day | A high-traffic site where every hour of downtime has a cost |
The table matches the published packages, and the details of the Complete package SLA commitments are written into the contract. Recovery of a hacked site is free for Pro and Complete package clients. See the current figures in the package section of this page.
The monthly fee is set by the package, and choosing a package depends above all on how often your site changes and how much your business depends on it being available. A small brochure site that gets new content once or twice a month is covered by the monthly updates and weekly backups of the Basic package ($149/month). But when new orders, sign-ups or forms come in every day, a weekly backup means risking several days of data; here the daily backups and 4-hour response of the Pro package ($349/month) make more sense. The Complete package ($690/month), with real-time backups, WAF, CDN and a 2-hour response, is built for a high-traffic site whose downtime directly hurts sales and reputation. So the right question is not “which package is cheapest”, but what you would lose if your site went down or lost its data tomorrow, and how quickly it needs to be back.
The second factor is the current state of the site. The initial audit shows what has fallen behind: an old core, abandoned plugins, malware, insecure settings or no backups. These are fixed before maintenance starts; and if the site was built by another team, the cost of fixing them is calculated separately from the monthly contract, because it is one-off work, not ongoing. The audit output is a list of issues showing which are urgent and which can be handled in the normal maintenance routine. That is why a site that has been updated regularly enters maintenance cheaper and faster than one that has been left unattended for years.
Setup time also depends on this audit. For a healthy site, the work moves almost directly to setting up monitoring, automatic backups and alerts; for a site with accumulated issues, the fixing stage takes longer. Keep one point in mind before choosing: maintenance is for keeping your current site healthy. If you want new features, a redesign or a new section, that is a development project and is estimated separately. Keeping the two apart keeps the monthly fee predictable and stops maintenance work being sacrificed to development work.
This list is the contract’s scope of work. The frequency and level of each item depend on the chosen package and are shown in the table above.
CMS, plugin and theme updates, regular backups, security monitoring, speed optimization, small bug fixes and a monthly report are all included in support.
If your site is hacked, we restore it from a clean backup right away and fix the security issue. This is free for clients on the Pro and Complete packages.
Yes. We first run an initial audit to review the state of the site. If it has specific problems, fixing them is priced separately.
Through the ticketing system, WhatsApp and Telegram. In the Complete package, you also get a direct phone number.
Backups are stored on separate servers in different locations, so if something goes wrong with the main server, we can restore your site quickly.
We have three fixed packages: Basic at $149, Pro at $349 and Complete at $690 per month. They differ in how often updates and backups run, the level of security monitoring and response time. If the site has technical or security issues before we start, fixing them is priced separately from the monthly fee.
If your site rarely changes, you do not need heavy support; but keeping plugins up to date and having a clean backup is necessary for any website. The Basic package is built for exactly this: monthly updates, weekly backups, uptime monitoring and a monthly report. Dealing with a hacked site that has no backup is a much bigger job than regular maintenance.
Not necessarily. Response time is how long it takes for a specialist to review your request and start working on it. Resolution time depends on the problem; a simple error may be fixed right away, but cleaning and restoring an infected site takes longer.
An SLA, or service level agreement, is a document that puts support commitments, such as response time and how downtime is handled, in writing. In the Complete package, these commitments are written into the contract so both sides know what to expect in each situation. We go through the details with you before signing.
It depends on how much it would matter to lose the last few days of data if your site broke today. For a brochure site whose content rarely changes, weekly backups are usually enough. But a store or a site that receives orders, sign-ups or user messages every day needs daily or real-time backups.
Auto-updates are only part of the job. Sometimes a new plugin version conflicts with the theme or another plugin and breaks part of the site, while auto-updates neither take a backup beforehand nor check the site afterwards. In support, updates are done together with a backup and a check of the site, so you can roll back to a working version if something goes wrong.
Access to the website admin panel and the hosting or server is needed for updates, backups and security checks; for domain and DNS work, access to the domain panel helps. If you have backups or documentation from the previous team, share them at the start so the initial audit is more accurate.
The free bug-fixing period that comes with a website design project only covers issues in the delivered work. Monthly support is ongoing maintenance: updates, backups, security and speed monitoring, downtime alerts and regular reports. It is best to decide on a support package before the bug-fixing period ends so the site is not left unattended.