Website support and maintenance
Keeping what already runs: a technical audit, speed, a move without losing traffic, maintenance and the rescue of a project whose developer disappeared.
05 services
Subsections
- 01 Audit A person reads your code and tells you what it will cost.
- 02 Performance Measured, then fixed — front end, server and everything between.
- 03 Migration Off the platform you outgrew, without losing the traffic.
- 04 Maintenance Reserved hours, watched uptime, one person who knows your project.
- 05 Rescue The developer vanished. Access, code and control come back to you.
In short
Support is work with what is already running: an audit, speed, a move off a platform you have outgrown, ongoing maintenance and the rescue of a project whose developer disappeared. We look after the sites we build ourselves: reserved hours every month, monitoring, updates and backups checked by restoring them. With other people’s projects we work honestly: we read the code and write a report, return access and domains to you, deal with the urgent, and then say plainly what is worth keeping and what is cheaper to rebuild — we do not rework someone else’s code. The price is counted in hours; maintenance is a number of hours reserved per month.
What we build
Services in detail
| Service | What’s included | Who it’s for |
|---|---|---|
| Technical Audit |
|
|
| Performance |
|
|
| Migration |
|
|
| Maintenance |
|
|
| Rescue & Takeover |
|
|
Where to start: from the situation to the service
Find your situation — the right column shows which service solves it.
| Situation | What we do | Service |
|---|---|---|
| You are about to invest in a site or buy a business | we check the code, risks and real cost of ownership | Technical audit |
| You are told “everything is fine”, but something is wrong | an independent look and a written report | Technical audit |
| The site is slow, rankings and orders drop | we measure, find the cause and fix it in order of importance | Performance |
| You pay monthly for a builder and hit its ceiling | a move to your own code with traffic preserved | Migration |
| The site earns money, and there is no developer on staff | reserved hours, monitoring, updates and backups | Maintenance |
| The developer stopped replying, you have no access | we return access, stop the damage and give an honest verdict | Rescue |
Technical audit: what we check
A person reads the code and measures the site on real devices. A scanner is only a helper: it does not know what your business loses money on.
Code and architecture
- How the project is built and how hard it is to change
- Outdated dependencies and versions that are no longer supported
- Duplicated and dead code
Security
- Forms, sign-in and file uploads
- Passwords, keys and access rights
- Known vulnerabilities in dependencies
Speed
- Core Web Vitals on real phones and computers
- Server response and database queries
- Images, fonts, scripts and third-party tags
Search and AI
- Indexing, canonical addresses, redirects and the sitemap
- Headings, metadata and structured data
- Whether AI assistants can read and quote the content
Accessibility
- Contrast, keyboard, focus and screen readers
- WCAG and the legal requirements where they apply, such as the European Accessibility Act
Infrastructure and ownership
- Who owns the domain, hosting and code
- Backups and whether they can actually be restored
- Certificates, mail and DNS
What is in the audit report
Not a hundred pages of warnings, but a document you can make decisions with.
-
01
A summary for the owner
One page in plain language: what state the site is in and what it costs you.
-
02
Ranked by money
Findings are ranked by what costs you money first, not by what is easiest to list.
-
03
A fix and an estimate
For each finding: why it matters, how to fix it and roughly how much work it takes.
-
04
Quick wins
What gives the most effect for the least work — to start with.
-
05
An honest verdict
Whether it is worth improving what exists or cheaper to build anew.
-
06
The report is yours
It stays with you, whoever does the work afterwards.
Site speed: the numbers that matter
Google measures speed on real visitors’ devices. These are the thresholds of the green zone.
- LCP — up to 2.5 s
- How fast the main content of the page appears.
- INP — up to 200 ms
- How fast the page responds to taps and clicks.
- CLS — up to 0.1
- How much the page jumps while loading.
- TTFB — up to 0.8 s
- How fast the server starts to answer. Not part of Core Web Vitals, but everything else depends on it.
How we speed a site up
Sites we built we speed up ourselves. On other sites we measure, set up everything that does not require changing the code, and write out the code changes for your team — or plan them into a move.
-
Measurement
Data from real visitors and checks on ordinary phones — not only on a powerful laptop.
-
Diagnosis
What exactly is slow: the server, the database, images, scripts or third-party tags.
-
Delivery
Caching, compression and modern image formats — often a noticeable gain without touching the code.
-
Fixes by priority
First what slows down the pages that bring money, then everything else.
-
Before and after
The same measurements after the work — the result in numbers, not in words.
-
Monitoring
So the speed does not quietly slide back with new content and tags.
How we move a site without losing traffic
A move is not copying pages. The point is that search engines and customers do not notice it — except that the site became faster.
-
A snapshot of what exists
All addresses, rankings, traffic and incoming links — so we know what must be preserved.
-
A redirect map
Every old address gets its new one: 301 redirects mapped one by one.
-
Data out of the platform
Content, media, orders and customers are exported — including what the platform made hard to take.
-
A new site on clean code
Built on a test domain closed from indexing; titles, descriptions and texts that already work are kept.
-
A switch with a rollback
Planned without downtime; if something goes wrong, we go back to the old version in minutes.
-
Watching after the move
Errors, indexing and rankings in Google Search Console — in the first weeks after the switch.
Maintenance: how it works
For sites we built or moved to our own code. The first month after handover is a free warranty; after that, maintenance by agreement.
-
01
Hours every month
Reserved for changes, content and small features. Unused hours are discussed, not wasted.
-
02
Monitoring
Uptime, errors, certificates and forms are watched — we learn about a problem before your customers do.
-
03
Updates
Security patches, dependencies and the server environment are updated and tested.
-
04
Backups that work
Backups are checked by restoring them, not just by a schedule.
-
05
Quarterly check-up
Speed and search health are checked every quarter, not once a year.
-
06
One person in the loop
Someone who already knows your project — reachable without a briefing.
The developer disappeared: what we do
First control and safety, then decisions. We do not rework someone else’s code, but we return the project to you and say honestly what to do with it.
-
Access back in your name
Domain, hosting, repository, mail and analytics are recovered and registered to you.
-
Stopping the damage
We renew the domain and certificate, close access for former contractors, make a backup and switch off what is dangerous.
-
Reading the project
The code and infrastructure are read and described — the black box gets a map.
-
An honest verdict
What is worth keeping, what should be rebuilt and what it will cost.
-
The next step
Either the documentation goes to your team or a new contractor, or we build a new site and move everything valuable.
-
Never again
Handover documentation and access kept with you — so you are never in this position again.
Site owner’s checklist: how to protect yourself in advance
Most rescues could have been avoided. Check these points today — it takes an evening.
-
01
The domain is in your name
Not on the contractor and not on a former employee’s personal account.
-
02
The hosting is yours
The account and the payments are with the company.
-
03
The code is with you
A repository you have access to, or at least a fresh copy of the source files.
-
04
Copies outside the hosting
Backups stored somewhere else — and restored at least once.
-
05
Two administrators
Access does not depend on one person.
-
06
A description of the project
Where it all lives and how it is connected — a document any developer can pick up.
Common mistakes after launch
-
Waiting until it breaks
An expired certificate or a broken form costs orders every hour nobody notices.
-
Backups nobody restored
A backup that has never been restored is a hope, not a backup.
-
Putting updates off
Old versions collect known vulnerabilities, and each delay makes the update harder.
-
An audit by a scanner only
A list of hundreds of warnings without priorities does not say what to fix first.
-
A move without redirects
Search engines lose the old pages, and the site starts from zero.
-
Everything on one person
When the only person with access disappears, so does control over the site.
Questions about support
How much does website support cost?
The price is counted in hours. Maintenance is a number of hours reserved per month; an audit, a speed-up or a move is estimated for the task and fixed before the start. The estimate is free.
Do you take on sites you did not build?
For an audit, a move and a rescue — yes. We do not rework someone else’s code on an ongoing basis: it is usually faster to build anew than to dig through outdated, tangled code. Ongoing maintenance is for sites we built or moved to our own code.
Will we keep our rankings after a move?
That is the whole point of a careful move: addresses are mapped one to one with redirects, working texts and metadata are kept, and indexing is watched in the first weeks.
Can you speed up a site on WordPress or a builder?
Partly: we measure and set up delivery — caching, compression, images. Beyond that the platform sets a ceiling, and the real gain comes with a move to your own code.
Do unused maintenance hours burn?
No. Hours are either used or discussed — for example, moved to a feature you have long wanted.
How is the warranty different from maintenance?
A month of fixing anything that turns out broken — free: that is not support, that is finishing the job. Ongoing work is a separate agreement.
Can we take the audit report to another contractor?
Yes. The report is yours and is written so any developer can work from it.
The site is down right now. What do we do?
Write through the form or the contacts and describe what you see. If it is our site, we fix it; if not, we start with access and stopping the damage.
Do you check accessibility?
Yes, as part of the audit: contrast, keyboard, focus and screen readers — against WCAG and the legal requirements where they apply.
Do you sign an NDA?
NDA on request before the launch. Under an NDA the project is not shown anywhere at all. In any case we pass no materials or information about your project to third parties and never reuse them in similar projects for others.
Online form
Discuss
support
Describe what is happening with the site and what worries you — we will suggest where to start: an audit, speed, a move or maintenance. The consultation is free.