How long does a Karlsruhe project actually take?

Three days for a business site, seven for a store, ten for a custom application. That holds because the process is fixed rather than improvised and because your content exists on day one. What stretches a build is almost never the code — it is waiting for copy, logos and photographs, so those are requested before the clock starts.

What payment methods can my Karlsruhe checkout accept?

For Germany: Stripe, SEPA Direct Debit, Klarna, giropay, and PayPal — which carries unusually high share here. The right combination depends on your average basket and your customers, and picking wrong is expensive — the payment method a buyer expects but cannot find is one of the most common reasons a checkout is abandoned at the final step.

Can you fix my existing site rather than rebuild it?

Often, yes, and it is usually the cheaper answer. Speed problems, a broken mobile layout, a form that silently fails or missing structured data are all fixable on the site you already have. I will tell you which of the two you need after looking, and a rebuild only gets recommended when the fix would cost more than starting again.

What hours will you be available to us in Karlsruhe?

My working day lands at 06:00–15:00 in your time, which is roughly 6 hours inside a normal Karlsruhe working day. In practice you can raise something in the morning and have it answered the same morning, and a scheduled call is easy to place at a civilised hour for both of us.

Will the site actually rank in Karlsruhe search results?

The build handles what is technically controllable: crawlable HTML, correct headings, structured data, fast pages, a clean sitemap and Search Console set up on day one. Ranking also depends on your competitors, your domain's age and the links pointing at you, which no developer controls. Anyone guaranteeing a position is guessing or lying.

Do you provide ongoing maintenance after launch?

Thirty days of snag fixes are included after launch at no extra cost — anything that does not work as specified gets fixed. Beyond that there are monthly plans for updates, backups, monitoring and small changes. They are optional and cancellable; a site handed over properly does not require a retainer to keep running.

Do you build on WordPress or something custom?

Whichever the project justifies. WordPress when you need to edit content constantly and want a familiar admin. A static build when speed and security matter more than a plugin ecosystem. Custom PHP and MySQL when the logic is genuinely yours. The choice is explained in the quote with its trade-offs, not presented as a foregone conclusion.

Germany · Germany

Website speed and performance optimisation in Karlsruhe

A Lighthouse score on a developer laptop with fibre broadband is not a measurement of your site — it is a measurement of the laptop. The work here is judged on field data from real visitors on real phones, which is also the data Google actually uses. For Karlsruhe businesses, quoted in EUR from $80, typically live in 4 days.

What website speed and performance optimisation includes for a Karlsruhe business

Fixed scope, agreed in writing before development starts. From $80, typically live in 4 days.

Field-data baseline from Chrome UX Report where your traffic supports it, plus throttled lab testing where it does not
Largest Contentful Paint work: the actual LCP element identified, then preloaded, resized and served in a modern format
Interaction to Next Paint work, which usually means shipping less JavaScript rather than reordering it
Cumulative Layout Shift eliminated: dimensions on media, reserved space for embeds, metric-matched font fallbacks
Render path fixed — critical CSS, deferred non-essential script, and third-party tags audited for what they cost
Image pipeline: AVIF and WebP with correct srcset, and lazy loading applied below the fold only
Caching and compression configured at the server, including long-lived immutable assets
A before-and-after report with the numbers and the method, so you can reproduce it rather than trust it

The terms for a German client

Starting price	From $80, quoted and invoiced in EUR
Typical timeline	4 days once content is supplied
Tax position	VAT at 19%, reverse-charged on imported services
Data protection	the EU GDPR and the BDSG, enforced by notably active state authorities — resolved by a DPA with EU Standard Contractual Clauses and a documented transfer impact assessment
Payment rails available	Stripe, SEPA Direct Debit, Klarna, giropay, and PayPal — which carries unusually high share here
My day in Karlsruhe time	06:00–15:00 — about 6 hours of overlap

Why this matters for Germany specifically

German law requires a compliant Impressum and Widerrufsbelehrung, and getting them wrong invites an Abmahnung — a formal cease-and-desist with costs attached. On German builds these are structural requirements, not footer decoration.

Accessibility on a Karlsruhe build, and why it is not optional

Keyboard navigation, real contrast ratios, form labels that are actually associated with their inputs, and alt text that describes rather than repeats. None of it is expensive when built in from the start and all of it is expensive to retrofit, which is the entire argument for doing it in the first pass.

The commercial case is simpler than the legal one: a site that a screen reader can navigate is a site that a search engine can parse, because both are reading the same semantic structure. Accessibility work and technical SEO overlap far more than either discipline usually admits, and in Karlsruhe the same build serves both.

Hospitality and venues in Karlsruhe

Restaurants, cafés, hotels and venues are judged on four things a visitor looks for immediately: today's opening hours, the menu or rate as a readable page, real photographs of the actual room, and how to book. Everything else on a hospitality site is decoration arranged around those four.

The PDF menu deserves its own warning. It is invisible to search engines, unreadable on a phone without pinch-zoom, and it is the most common reason a Karlsruhe venue never appears for searches naming the dishes it serves. Menus belong in HTML.

The contact form that silently fails

The most expensive bug on a small business website makes no noise at all. A form posts, shows a thank-you message, and the email never arrives — usually because the host's mail function is unauthenticated and the receiving server drops it without a bounce. The business concludes demand fell.

The fix is authenticated SMTP with SPF, DKIM and DMARC configured on the sending domain, plus a database write so a submission survives even when delivery fails. If you are unsure whether your Karlsruhe site has this problem, submit your own form from a phone on mobile data and see what actually arrives.

What I am not claiming about Karlsruhe

I have no office, postal address or phone number in Karlsruhe
I cannot meet you in person, and if that is a requirement you should hire locally
I am not claiming existing clients in Karlsruhe specifically — my live work is listed on the work page and you can check it
Nothing on this page is a guarantee of search rankings, which no developer can honestly offer