Real exampleA real German company’s website, checked with the free quick check on 24 Oct 2026. Name and address removed.
Needs work overall: 18 things to improve, with UI scoring lowest. Start with one action, one name. Quick audit: only the code-measured checks ran, so design and copy judgement is still missing. 6 checks need a person to confirm.
When one destination has several names, or one name leads to different places, visitors stop trusting the navigation and second-guess every click.
FixGive every destination one label and use it everywhere: menu, buttons, footer and page title. Rename or remove the duplicates the audit found.
Small text, long lines and tight line spacing tire readers quickly, especially on phones.
FixSet body text to at least 16 px, line length to 45–75 characters (max-width around 65ch) and line height to 1.4–1.6.
Labels like “Learn more” or “Click here” don’t say what happens, so people hesitate or skip them.
FixWrite every button and link as a verb plus what the visitor gets: “Book a call”, “See pricing”, “Download the guide”.
UI is where visitors struggle most. I'd start with "comfortable body text".
Body text: body 14px (mobile), ≈82 characters per line (outside comfortable range). Small text, long lines and tight line spacing tire readers quickly, especially on phones.
FixSet body text to at least 16 px, line length to 45–75 characters (max-width around 65ch) and line height to 1.4–1.6.
Matthew Butterick: Practical Typography — line length, point size, line spacing
141 buttons in 11 distinct styles. When buttons come in many styles, visitors can’t tell which action matters most or even what’s clickable.
FixReduce buttons to three styles (primary, secondary, text) and use each one for the same kind of action everywhere.
Jakob Nielsen, NN/g: 10 Usability Heuristics for User Interface Design
0% of tested controls respond the moment they're pressed. Buttons that react a moment late feel unresponsive, even if the site is fast.
FixShow a pressed state immediately (:active), open menus from the element that triggered them, and use CSS transitions so animations can be interrupted.
Apple: Designing Fluid Interfaces (WWDC 2018)
2 font families, 10 sizes, 90% on a consistent scale. Too many font sizes and families make a page feel unplanned and blur the difference between a heading and body text.
FixPick two families at most and a scale of six to eight sizes (for example 14, 16, 20, 25, 31, 39 px), then map every text style onto it.
Adam Wathan & Steve Schoger: Refactoring UI — hierarchy, spacing systems, limited palettes
91% of spacing values sit on a 4 px grid; text aligns to 22 left edges. Random spacing makes a layout feel slightly off even when visitors can’t say why.
FixChoose a spacing base (4 or 8 px), define a short set of steps (8, 16, 24, 32, 48, 64), and replace one-off values with the nearest step.
Adam Wathan & Steve Schoger: Refactoring UI — hierarchy, spacing systems, limited palettes
0 animation(s) on layout properties; CLS 0.39. Animating layout properties makes pages stutter and content jump, especially on cheaper phones.
FixAnimate only transform and opacity, reserve space for images and embeds, and keep layout shift (CLS) under 0.1.
Apple: Designing Fluid Interfaces (WWDC 2018)
Copy is where visitors struggle most. I'd start with "c6 · buttons and links say what happens".
4 vague button/link label(s); "hier" leads to 2 different places. Labels like “Learn more” or “Click here” don’t say what happens, so people hesitate or skip them.
FixWrite every button and link as a verb plus what the visitor gets: “Book a call”, “See pricing”, “Download the guide”.
WCAG 2.2 SC 2.4.4
Homepage says "you" 21× and "we" 30×. Visitors care about their problem, not your company. Copy full of “we” reads like it’s about you.
FixRewrite key sections from the visitor’s side: lead with “you” and what they get, then say what you do.
Government Digital Service: GOV.UK content design: writing for the web
Harder to read than needed: Amstad 54 (aim ≥ 60). Long sentences and difficult words lose readers, including experts reading on a phone.
FixAim for sentences under 20 words, prefer everyday words, write in the active voice, and explain any jargon the first time it appears.
plainlanguage.gov: Federal Plain Language Guidelines
Accessibility needs some love. I'd start with "everything works with a keyboard".
40 interactive elements are not reachable with the keyboard. People who can’t use a mouse rely on the keyboard. Anything they can’t reach is something they can’t use.
FixUse real <button> and <a href> elements for anything clickable, don’t remove them from the tab order, and add a “Skip to content” link.
WCAG 2.2 SC 2.1.1, 2.1.2
24 text element(s) get cut off when people increase letter, word or line spacing. Many people zoom or enlarge text. If the layout breaks, content and buttons disappear for them.
FixUse relative units and flexible layouts so the page works at 400% zoom and with larger letter and line spacing, without content being cut off.
WCAG 2.2 SC 1.4.4, 1.4.10
1 skipped heading level(s). Screen reader users jump by headings and landmarks. A page without real structure is one long stream.
FixUse one <h1>, nest headings in order (h2 under h1, h3 under h2), and wrap the page in <header>, <nav>, <main> and <footer>.
WCAG 2.2 SC 1.3.1, 1.3.2
1 personal-data field(s) without autocomplete. Error handling needs the judge stage. Forms are where accessibility problems cost you leads and sales directly.
FixGive every field a visible label, mark required fields in text, link error messages to their field, and use the right autocomplete attributes.
WCAG 2.2 SC 3.3.1, 3.3.2
SEO is solid with a few rough edges. I'd start with "unique, descriptive titles and descriptions".
1 description(s) outside 70–170 characters; 1 title(s) outside 15–65 characters. The title and description are your ad in search results. Missing or duplicate ones get fewer clicks.
FixWrite a unique title per page (main topic first, brand last, under about 60 characters) and a 120–160 character description that makes people want to click.
Google Search Central: Influencing title links in search results
Missing og:title, og:description, og:image; shared links will look bare. Links shared without a preview image and description get far fewer clicks.
FixAdd og:title, og:description and a 1200 × 630 px og:image to every key page, and check them with a link preview tool.
Google Search Central: SEO Starter Guide
UX is where visitors struggle most. I'd start with "one action, one name".
96 page(s) reached under different names; 39 label(s) leading to different pages. When one destination has several names, or one name leads to different places, visitors stop trusting the navigation and second-guess every click.
FixGive every destination one label and use it everywhere: menu, buttons, footer and page title. Rename or remove the duplicates the audit found.
Jakob Nielsen, NN/g: 10 Usability Heuristics for User Interface Design
First action 0.2 screens down; 20 key button(s) under 44px tall. Most visits are on phones. Small tap targets and actions pushed far down make the mobile site feel second-class.
FixMake primary buttons at least 44 px tall, bring the main action into the first screen on mobile, and check that nothing overflows sideways.
NN/g: Mobile UX guidelines (touch targets, content priority)
Conversion needs some love. I'd start with "fast on a phone".
Landing page: LCP unknown, 29.3 MB on mobile. Later funnel steps are measured by the funnel walk. On phones, every extra second of loading costs conversions.
FixGet mobile LCP under 2.5 s and pages under 2 MB: compress images, cut unused scripts and fonts, and lazy-load what’s below the fold.
web.dev: Core Web Vitals thresholds (LCP 2.5 s, INP 200 ms, CLS 0.1)
Small fixes with a big pay-off. Tick them off as you go.