Real exampleA real German company’s website, checked with the free quick check on 24 Oct 2026. Name and address removed.
Poor overall: 22 things to improve, with Accessibility scoring lowest. Start with one action, one name. Quick audit: only the code-measured checks ran, so design and copy judgement is still missing. 4 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.
Low-contrast text is hard to read for people with low vision, older visitors and anyone on a phone in sunlight. It’s also the most common accessibility failure.
FixDarken text until it reaches at least 4.5:1 against its background (3:1 for large text and for icons, borders and focus rings).
Accessibility is where visitors struggle most. I'd start with "text and controls are readable".
14 elements fall below WCAG contrast minimums. Low-contrast text is hard to read for people with low vision, older visitors and anyone on a phone in sunlight. It’s also the most common accessibility failure.
FixDarken text until it reaches at least 4.5:1 against its background (3:1 for large text and for icons, borders and focus rings).
WCAG 2.2 SC 1.4.3, 1.4.11
3 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
No main landmark; screen-reader users can't jump to the content. 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 focus stop(s) without a visible indicator, 20 hidden behind other elements, out of 81. Keyboard users need to see where they are. Without a visible focus outline they are navigating blind.
FixNever remove the focus outline without a replacement. Add a clear :focus-visible style (for example a 2 px outline with 3:1 contrast) to every interactive element.
WCAG 2.2 SC 2.4.7, 2.4.11
Navigation order differs on 15 of 15 pages. When navigation moves around between pages, people relying on memory or assistive tech lose their way.
FixKeep navigation in the same place and order on every page, and don’t change context automatically when a field gets focus or input.
WCAG 2.2 SC 3.2.1, 3.2.2
Copy is where visitors struggle most. I'd start with "c5 · plain, readable language".
Harder to read than needed: Amstad 0 (aim ≥ 60); sentences average 29 words. 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
32 hype words in 5944 words (1.1 per 200): innovative, innovativsten, einzigartig, nahtlos, einzigartigen, einzigartige. Facts per section need the judge stage. Words like “best”, “leading” and “innovative” are ignored. Concrete facts are believed.
FixReplace each superlative with a fact: a number, a name, a result or a timeframe.
NN/g: How Users Read on the Web (concise, scannable, objective)
Homepage says "you" 3× and "we" 6×. 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
2 vague button/link label(s). 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
UI is where visitors struggle most. I'd start with "comfortable body text".
Body text: body 15px (desktop), body 13px (mobile), ≈148 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
1 of 21 large headings use loose tracking or leading. Large headings with loose letter spacing and tall line height look unfinished and break apart as words.
FixFor text 32 px and up, use letter-spacing of 0 or slightly negative (around -0.01 to -0.02em) and line height of 1.0–1.2.
Apple: Designing Fluid Interfaces (WWDC 2018)
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)
3 font families, 7 sizes, 100% 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
74% of spacing values sit on a 5 px grid; text aligns to 8 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
SEO is solid with a few rough edges. I'd start with "core web vitals in the green".
Lab data: LCP 2604 ms, CLS 0.00, Total Blocking Time 0 ms. Slow, jumpy pages rank lower and lose visitors before they load.
FixShrink and preload the largest above-the-fold image, defer non-critical JavaScript, and reserve space for images and embeds to stop layout shift.
web.dev: Core Web Vitals thresholds (LCP 2.5 s, INP 200 ms, CLS 0.1)
No structured data found; search engines have to guess what the business is. Structured data tells search engines what your business is and can earn richer search results.
FixAdd JSON-LD for your business type (Organization, LocalBusiness, Product or Article) with name, logo, contact details and links, and validate it in Google’s Rich Results Test.
Google Search Central: Structured data general guidelines
Missing 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
Image delivery can improve: Improve image delivery (Est savings of 708 KiB); Image elements do not have explicit `width` and `height`; Serves images with low resolution. Heavy images slow every page, especially on mobile data.
FixServe images as WebP or AVIF at the size they are shown, set width and height, and add loading="lazy" to images below the fold.
Google Search Central: SEO Starter Guide
UX is where visitors struggle most. I'd start with "one action, one name".
15 page(s) reached under different names; 11 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
3 element(s) change on their own; whether visitors can pause them, and how overlays close, needs the judge stage. Content that moves on its own, or overlays that are hard to close, take control away from visitors. They read more slowly than carousels advance.
FixLet visitors pause or stop anything that changes by itself, make overlays closable with a close button, Escape and a click outside, and keep the Back button working.
Jakob Nielsen, NN/g: 10 Usability Heuristics for User Interface Design
First action 0.3 screens down; 5 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 2.6 s, 1.5 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.