The short answer
A strong website says within a few seconds what you offer, who it's for and what the visitor should do now. It loads on mobile in 2.5 seconds at most (LCP), shows one clear next step per section and backs up trust with real names, figures and cases.
Add to that a CMS your team really uses, clean HTML structure and easily readable contrast. At the end of the article there's a checklist with target values you can tick off on your own site.
Whether it's a new build, a relaunch or ongoing maintenance: we measure every website project against the same principles. It's not about trends. It's about the basis without which a website can't do its actual job: turning visitors into enquiries and customers.
1. Does a visitor understand within seconds what you offer?
A visitor decides very quickly whether to stay. You don't win that time with an original slogan. You win it with an immediately understandable answer to three questions: what do you do? For whom? What should I do now?
In practice that means: the headline names the service, not just a feeling. The subline names the target group or region. And the button is in view without scrolling. Example: "We live quality" says nothing. "Electrical installation for businesses in the Stuttgart area, quote within 48 hours" answers all three questions in one line.
How important this is was shown by the relaunch of Hotel Zuckerfabrik. On the old site, the welcome text could only be reached after the first scroll. There was no incentive to book in view. Today headline, "Book now" and the availability check sit directly in the hero.
2. How fast does a website have to load?
Load time feeds into Google's assessment of page experience via the Core Web Vitals. Google recommends three target values [2]: the largest visible element (Largest Contentful Paint, LCP) appears within 2.5 seconds. The page responds to input in under 200 milliseconds (INP). And the layout hardly shifts while loading (CLS under 0.1).
The most common brakes are large images without modern formats, fonts from external servers, too many tracking and chat scripts and a website builder full of features nobody uses. Each of these brakes can be solved. But it's easiest before they appear: load time belongs in the project as a goal, not as rework afterwards.
3. Why does the mobile version have to come first?
Around 60 % of page views in Germany now come from smartphones [1]. Google uses the mobile version of your content for indexing and ranking [3]. A site designed for desktop and only "adapted" for mobile therefore starts at a disadvantage.
Mobile first means concretely: content, navigation and forms are thought out for the small screen first. Buttons are big enough for a thumb. Phone numbers can be tapped. And nothing important is hidden on the phone that's visible on desktop.
4. How many calls to action can a page take?
Many websites offer five next steps at once: newsletter, download, contact, demo and social media. In the end none of them happens reliably. A strong page has one dominant call to action that comes back at suitable points.
A second, quieter step is fine if it suits an earlier phase. Example: "Request a project" as the main button, plus a text link "What does it cost?" to a pricing article. More than two different offers per page are almost always too many in our project experience. How to build the path behind it is in the article on conversion funnels.
5. Which trust signals really work?
Stars without a source, logos without context and "over 100 happy customers" without evidence are quickly skipped. What works can be verified:
- Real people. Contacts with name, role and photo, no stock images.
- Concrete figures with a frame. Time period, starting point and source belong with them. Example from our work: Batteriecenter Ludwigsburg, +521 % visitors from April to August 2026.
- Cases with before and after instead of vague promises of success.
- Honest limits. A sentence like "We're not the right fit for that" often builds more trust than any seal.
Google puts it similarly: it should be obvious to visitors who created a piece of content, for example through a byline with information about the author's background [4]. That applies to guides just as much as to service pages.
6. Which CMS suits your team?
A website where every text change needs an external request goes stale faster than most people realise. Nobody wants that. But the hurdle is too high. A CMS that matches the real maintenance effort is more important than one with as many features as possible.
The rule of thumb from our project experience: if you change content monthly, you need a CMS with a simple interface and clear permissions. If you change something once or twice a year, a static site without a CMS can be faster, cheaper and lower-maintenance. Ask yourself beforehand: who maintains what, and how often?
7. What do Google and AI search need from your site?
A real HTML hierarchy helps machines understand your page: one H1, below it H2 and H3 as actual headings, not just bold text. Important content is on the page as text, not only in images.
Structured data following Schema.org additionally describes who you are and what you offer. But it's no secret trick for AI answers. Google says explicitly: there are no additional requirements and no special schema markup for AI Overviews and AI Mode [5]. The normal SEO fundamentals apply. What matters is that structured data matches the visible text. More on this in the article on SEO vs. GEO. How crawling, local SEO and measurement work together is shown in our overview SEO & GEO.
8. Why is accessibility good design?
Easily readable contrast, large click areas and forms with clear labels help people with disabilities. But they also help anyone looking at their phone outside in the sun. The WCAG 2.2 guideline names concrete values [6]: normal text needs a contrast ratio of at least 4.5:1. Click targets should be at least 24 × 24 CSS pixels or have enough spacing.
For some websites accessibility has also been mandatory in Germany since June 2025, for example for online shops for consumers. When the law applies is in the article Hiring an agency.
Which mistakes do we see most often in audits?
From our project experience, four patterns come up again and again, across all industries:
- The slogan comes before the service. The headline sounds good but doesn't say what the company does. Anyone arriving via Google is looking for a service, not a motto.
- The hero image is a huge photo without compression. It looks nice on desktop and pushes the mobile LCP value above 2.5 seconds.
- Contact can only be reached via the menu. Anyone convinced at the end of a service page first has to scroll up and search.
- References without context. A logo strip without a word about what was done hardly convinces. One sentence per project and a link to the case are often enough.
None of these mistakes needs a relaunch. Each can be fixed with little effort once it's been spotted. That's exactly what the checklist is for.
The checklist with target values
Take 30 minutes and go through your homepage and one service page with it:
| Principle & check | Target value |
|---|---|
| Clarity 5-second test with a stranger | They name the service, target group and next step |
| Load time PageSpeed Insights (mobile) | LCP ≤ 2.5 s, INP < 200 ms, CLS < 0.1 |
| Mobile Your own smartphone | Enquiry can be sent in under a minute |
| Call to action Count the CTAs per page | One main offer, at most one quiet extra |
| Trust Read through the homepage | Real name, photo and at least one piece of evidence with a source |
| Maintenance Change a text yourself | Without outside help in under 10 minutes |
| Structure Browser extension for headings | Exactly one H1, logical H2/H3 |
| Contrast Contrast checker | Body text at least 4.5:1 |
The more rows are green, the more likely your website works as a digital point of contact, however old or new it is. If four or more rows are red, it's worth looking at the 7 signs you need a relaunch.