Work continues after launch

Protect the value.
Keep moving forward.

Keep your website working for your business, with planned updates, tested forms and improvements that make your team’s work easier.

SYSTEMATIC MAINTENANCE01—03
Work continues after launch.
  1. 01
    AssessCondition and risks
  2. 02
    ChangeUpdates and corrections
  3. 03
    TestCritical journeys and operation

Every change ends with a functional check.

Starting point

Keep inquiries and
orders moving.

Important journeys must still work after a change. Backups, testing and follow-up checks belong together. We check forms, navigation and the shop’s purchase journey instead of relying only on an update notification.

Ongoing support

The important work
comes first.

We agree what needs attention now and what can wait. That creates manageable tasks for updates, quality and security, with clear responsibilities and checked results.

Updates & functional tests

We assess the CMS, store software, theme, plugins and runtime versions together. Where needed, changes are prepared in a test environment, with backups and a fallback route.

After an update, navigation, forms, checkout, imports and connected services matter. A successful update click does not replace these follow-up checks.

Performance & quality

Oversized images, unnecessary extensions, databases or hosting can slow a website down. We measure specific bottlenecks and prioritize changes accordingly.

Quality includes mobile usability, text wrapping, internal links and technical SEO as well as response times.

Security & development

We check permissions, known vulnerabilities, signs of malware and available backups. Working recovery needs a clear process.

Form spam, failed orders and new requirements feed into an organized task list. Ongoing maintenance, troubleshooting and new functions are expressly agreed.

Act promptly

An urgent problem
with your website or store?

For malware, failed updates, unavailable pages, form spam or store errors, a structured initial assessment helps. Use urgent support to describe the problem, URL, system and urgency.

Go to urgent website and store support
Web and infrastructure

The foundation
needs maintenance too.

For business-critical web applications, support does not end at the CMS. On request, we also consider servers, operating systems and the underlying web infrastructure.

Dedicated servers, colocation or rack solutions in an Austrian data center, and remote hands for hardware problems, are coordinated with the operating model. Responsibilities, maintenance windows and response targets are specifically agreed.

Hosting & infrastructure in detail

For specialist patch management and server updates:

Explore patch management at wsus.at (complementary website, opens in a new tab)
When maintenance reaches its limits

Support should
stay transparent.

If maintained versions are unavailable or every small change takes disproportionate effort, we assess the operating model. We separate licenses, extensions, hosting, technical maintenance and support for your editors. Included services, additional hours and response targets are expressly agreed.

For unsupported CMS versions, we compare upgrades, simpler ongoing operation on a maintained foundation and a platform change. The aim is a solution whose ongoing effort matches its value.

Compare migration & operating costs
Thoughtful implementation

Understand the existing setup first.

When taking over a website, we assess system versions, extensions, custom changes and available backups. This produces a clear task list. Urgent risks, necessary maintenance and optional improvements are considered separately.

01

Assess the setup before taking over support

02

Clarify backups and fallback options

03

Check forms, navigation and store processes

04

Document changes and open points

Questions & answers

What you should
know before starting.

Do you support websites built by others?

Following a technical assessment. Clear access, valid licenses, available backups and the condition of custom changes are decisive.

Can you improve a slow website?

We start by measuring and isolating the problem. Causes may include content, extensions, databases, hosting or external services. A specific improvement can only be responsibly planned after that assessment.

Will the website then be completely secure?

There is no absolute security guarantee. Regular maintenance, appropriate permissions and a prepared response to problems reduce risks but do not replace ongoing attention.