steakhaus-kette.example

2 page(s) tell search engines not to index them and 0 return an error. Pages search engines can’t crawl or index simply don’t show up in results.

Fix→Make sure key pages return 200, have no noindex, point their canonical to themselves and are listed in an XML sitemap referenced from robots.txt.

Lab data: LCP 7465 ms, CLS 0.00, Total Blocking Time 1 ms. Slow, jumpy pages rank lower and lose visitors before they load.

Fix→Shrink and preload the largest above-the-fold image, defer non-critical JavaScript, and reserve space for images and embeds to stop layout shift.

1 page(s) without a meta description. The title and description are your ad in search results. Missing or duplicate ones get fewer clicks.

Fix→Write 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.

Missing og:title, og:description, og:image; shared links will look bare. Links shared without a preview image and description get far fewer clicks.

Fix→Add og:title, og:description and a 1200 × 630 px og:image to every key page, and check them with a link preview tool.

Image delivery can improve: Improve image delivery (Est savings of 523 KiB). Heavy images slow every page, especially on mobile data.

Fix→Serve images as WebP or AVIF at the size they are shown, set width and height, and add loading="lazy" to images below the fold.

Body text: body 14px (desktop), body 12px (mobile), ≈89 characters per line (outside comfortable range). Small text, long lines and tight line spacing tire readers quickly, especially on phones.

Fix→Set 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.

5 font families and 7 different sizes: the type has no clear system. Too many font sizes and families make a page feel unplanned and blur the difference between a heading and body text.

Fix→Pick 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.

6 transition(s) over 500 ms, 0 movement(s) with linear easing. Slow or linear animations make an interface feel sluggish; the right timing makes it feel responsive.

Fix→Use 100–200 ms for small interactions and 200–400 ms for panels, ease-out for things entering, and nothing over 500 ms on a click path.

33% of tested controls respond the moment they're pressed. Buttons that react a moment late feel unresponsive, even if the site is fast.

Fix→Show a pressed state immediately (:active), open menus from the element that triggered them, and use CSS transitions so animations can be interrupted.

82% of spacing values sit on a 5 px grid; text aligns to 7 left edges. Random spacing makes a layout feel slightly off even when visitors can’t say why.

Fix→Choose 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.

6 vague button/link label(s); "mehr erfahren" leads to 3 different places. Labels like “Learn more” or “Click here” don’t say what happens, so people hesitate or skip them.

Fix→Write every button and link as a verb plus what the visitor gets: “Book a call”, “See pricing”, “Download the guide”.

Harder to read than needed: Amstad 39 (aim ≥ 60); sentences average 22 words. Long sentences and difficult words lose readers, including experts reading on a phone.

Fix→Aim for sentences under 20 words, prefer everyday words, write in the active voice, and explain any jargon the first time it appears.

8 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.

Fix→Use real <button> and <a href> elements for anything clickable, don’t remove them from the tab order, and add a “Skip to content” link.

0 focus stop(s) without a visible indicator, 58 hidden behind other elements, out of 122. Keyboard users need to see where they are. Without a visible focus outline they are navigating blind.

Fix→Never 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.

With "reduce motion" switched on, 8 of 8 animations still run. Moving content can make some people dizzy or unable to focus, and flashing can trigger seizures.

Fix→Add a pause button to anything that moves for more than five seconds, avoid flashing, and turn off non-essential animation under prefers-reduced-motion.

4 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.

Fix→Use relative units and flexible layouts so the page works at 400% zoom and with larger letter and line spacing, without content being cut off.

Navigation order differs on 15 of 15 pages. When navigation moves around between pages, people relying on memory or assistive tech lose their way.

Fix→Keep navigation in the same place and order on every page, and don’t change context automatically when a field gets focus or input.

1 skipped heading level(s). Screen reader users jump by headings and landmarks. A page without real structure is one long stream.

Fix→Use one <h1>, nest headings in order (h2 under h1, h3 under h2), and wrap the page in <header>, <nav>, <main> and <footer>.

Landing page: LCP 7.5 s, 44.8 MB on mobile. Later funnel steps are measured by the funnel walk. On phones, every extra second of loading costs conversions.

Fix→Get 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.

37 page(s) reached under different names; 8 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.

Fix→Give every destination one label and use it everywhere: menu, buttons, footer and page title. Rename or remove the duplicates the audit found.

First action 0.8 screens down; 4 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.

Fix→Make primary buttons at least 44 px tall, bring the main action into the first screen on mobile, and check that nothing overflows sideways.