Web design in Lucerne.

Lucerne puts an internationally composed guest business and a thoroughly local everyday trade in the same city — and the two need almost opposite websites. The figures show the scale. The city of Lucerne counted around 1.48 million hotel overnight stays in 2025, up 5.1 per cent on the previous year; across the canton it was roughly 2.5 million, a third record year in a row. At the same time, around 99 per cent of all companies in the canton of Lucerne are small or medium-sized, and within the service sector healthcare accounts for the largest share of employment.

A hotel, an excursion operator or a restaurant on the Reuss addresses people who do not know the place, often do not speak the language, will not telephone, and are deciding in another time zone. A fiduciary office, a dental practice, a plumbing firm or an electrician in Kriens, Emmen or Horw addresses people who live ten minutes away, speak German, and will simply call if in doubt.

The distinction sounds obvious and gets ignored constantly. We regularly see guest websites whose primary contact route is a telephone number — for somebody in Singapore that is not an offer at all. And the reverse: local trade sites carrying long English translations nobody reads. So the first step is always the same question. Which of the two businesses is this being built for? Anyone serving both does not need a compromise site. They need two clearly separated areas inside one presence.

The decisive difference is the absence of local knowledge. A guest does not know whether your house is a five-minute walk from the station or a bus ride away, and that uncertainty is the most common reason people book through a portal after all. Six things that belong near the top of a Lucerne guest site:

• Location in minutes, not in street names. "Seven minutes on foot from Lucerne station" says more than any address does.
• Price in local currency, clearly marked as CHF. A missing currency label creates mistrust and generates enquiries you have to answer.
• Getting here as its own page. From Zurich airport, by train, by car, by boat — including parking, which is a genuine question in the old town.
• Written contact routes. A form and an email address rather than a phone number as the main route. A guest in another time zone does not call.
• Season and opening hours in plain view. Whatever closes in winter has to be visible before the booking, not after it.
• Images that show the place. The view, the surroundings, the walk to the door — not only interiors.

For everyday local trade almost the opposite applies: a short site, the phone number large, the service area named plainly, availability rather than atmosphere. That lean variant is what most of our SME work looks like: five to eight pages, no gallery, and the enquiry route reachable from every one of them.

A Lucerne guest website is opened on a mobile phone, on a foreign mobile network, far more often than average — and there every unnecessary megabyte costs real bookings. Tourism businesses in particular lean towards image-heavy sites: a large video in the header, galleries of forty shots, high-resolution panoramas. That is right editorially, because images are the product here. It is risky technically, because those same images bring the site to a halt.

The measurable value behind this is the time to the largest visible element, the Largest Contentful Paint — in practice almost always that big header image. What the figure means and which threshold counts as good is explained in our glossary entry on LCP. Our work on it is unspectacular and effective: modern image formats instead of uncompressed files, correctly sized variants per screen width, loading further images only on scroll, and a header that appears first and sharpens to full resolution afterwards.

The second big drag is embedded third-party systems: booking windows, review widgets, chat boxes, map services, visitor statistics. Each one loads its own code. We integrate them so they only start when they are actually needed — and we tell you plainly which of them is not worth its price in load time.

None of this is guesswork. We measure the site before and after the rebuild, so the improvement is evidenced rather than asserted — and so you can see which single element is costing you the most.

We do not build booking engines and we do not build property management systems. What we do is make sure the handover from your website into your existing system does not feel like a break. That boundary is drawn deliberately. Booking systems need payment processing, availability sync across several channels and continuous maintenance. A substitute built for a single business would be expensive and fragile.

What actually decides direct bookings is the moment of the switch. Typical faults we fix again and again: the booking window opens in a new tab with a completely different look. The website language is not carried over, and the English-speaking guest lands on a German form. The currency jumps. The price on the offer page and the price in the booking window do not match. Each of these creates doubt, and doubt sends the guest back to the portal they already trusted.

So we treat that handover as its own work item: language, currency, styling, price display and the route back. How much your provider allows varies. Some systems can be aligned closely to your presence; others barely at all. We tell you which case applies before implementation rather than explaining it afterwards.

If the enquiry route matters more to you than the booking route — for a restaurant, a venue or an excursion operator taking group requests — the same discipline applies to forms. Whether those enquiries are actually being counted is a separate question, covered under conversion tracking.

The range runs from CHF 3,000 to CHF 25,000, and the two items that move the figure are called languages and images. A focused single-language presence for a local service business sits at the lower end. A multilingual guest site with offer pages, photography, a travel page and booking integration sits at the top. The full breakdown is on web design and prices; a first self-assessment comes from the project calculator.

Running costs should be budgeted separately: domain, hosting, any licences for booking or review systems, and annual maintenance. For tourism businesses one further item is easily forgotten — image upkeep. A business that commissions new photography every couple of years looks current. One that does not looks, after five years, like a business that may no longer exist.

Honesty includes what we can evidence. Our references sit in the Zurich region. For Leo Ristorante in Globus we delivered the website, the photo and video material and the search work. For the bar Basilica in Zurich West, a presence including a reservation function. For Nolte Küchen Zurich, the complete digital presence. All of it is documented under our work. We have no Lucerne client project — and we will not invent one to make this page look better.

Launch belongs several weeks before the season the website is meant to work for. After a rebuild it takes time for search engines to take in the new structure fully, and that phase should not fall into your strongest booking period. Starting in May and hoping to go live in July means working against your own calendar.

Then there is the image question, which delays more projects in Central Switzerland than any technical task does. Exterior shots are tied to weather and season. A snow-covered picture cannot be taken in summer, and a terrace picture cannot be produced in January. So we make image planning the first step rather than the last: what exists, what is usable, what has to be created, and when that is realistically possible.

In practice that means, for most Lucerne tourism businesses: start in the quieter period, produce the photography in parallel, launch with lead time. For local service businesses with no seasonal swing, timing barely matters. There the only question is how quickly the site can be finished.

One related point on sequencing. If you are also planning paid campaigns for the coming season, the site should be live and measuring before the budget starts running. Sending paid traffic to a page you cannot yet read data from is the most common way a season's marketing money produces no usable learning.

In four cases we advise against a web project, and we would rather say it in the first conversation than in the third month.

• Your Google Business Profile is neglected. For a local business, a fully maintained profile with current photos, opening hours and answered reviews almost always does more in the short run than a new website. That is local SEO work and it starts at CHF 300 a month — described under local SEO.
• The real problem is the images. If a technically sound site is simply badly photographed, a photo day is the cheaper and more effective investment than a rebuild.
• Your budget is below CHF 3,000. Then we will not build you half a thing. A clean business profile and a simple builder site are the more sensible decision in that position.
• You need regular presence on the premises. Photo days, training at reception, weekly meetings — we cannot deliver that from Zollikon. There are good agencies in Central Switzerland for it.

A fifth case concerns dependence on booking portals. If practically every booking comes through a portal today, a new website alone will not change that. Direct bookings come from a bundle: a visible price advantage, a maintained business profile, reviews, returning guests, and a booking route without a break. The website is one part of that — not the whole answer. Anyone promising you otherwise is selling a hope.