guss-und-antrieb.example

1 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 4291 ms, CLS 0.00, Total Blocking Time 17 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.

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

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.

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

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

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

Fix→Darken text until it reaches at least 4.5:1 against its background (3:1 for large text and for icons, borders and focus rings).

1 control without a usable accessible name or valid ARIA (link-name). Screen readers announce controls by their name. A button without one is announced as just “button”.

Fix→Give icon-only buttons and links an aria-label, connect form fields to their <label>, and make sure the accessible name contains the visible text.

49 focus stop(s) without a visible indicator, 10 hidden behind other elements, out of 64. 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.

1 interactive element is 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.

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); 1 list/table structure errors. 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>.

Body text: ≈168 characters per line, weight 100 (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.

7 of 7 large headings use loose tracking or leading. Large headings with loose letter spacing and tall line height look unfinished and break apart as words.

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

17% 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.

3 font families, 8 sizes, 88% 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.

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.

65% of spacing values sit on a 4 px grid; text aligns to 10 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 animation(s) on layout properties; CLS 0.00. Animating layout properties makes pages stutter and content jump, especially on cheaper phones.

Fix→Animate only transform and opacity, reserve space for images and embeds, and keep layout shift (CLS) under 0.1.

Harder to read than needed: Amstad -14 (aim ≥ 60); sentences average 34 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.

Homepage says "you" 9× and "we" 13×. Visitors care about their problem, not your company. Copy full of “we” reads like it’s about you.

Fix→Rewrite key sections from the visitor’s side: lead with “you” and what they get, then say what you do.

1 vague button/link label(s). 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”.

24 page(s) reached under different names; 16 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 3.3 screens down; 3 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.

the navigation marks the current page on 15 of 15 pages. Without a “you are here” cue, visitors who arrive from search or a shared link can’t tell where they are or how to get back.

Fix→Mark the current page in the menu (and add aria-current="page"), link the logo to the homepage on every page, and add breadcrumbs on pages three or more levels deep.

Landing page: LCP 4.3 s, 7.9 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.