Juno
How it worksExample reportPricing
Start free audit
© Juno
Deutsch
ImprintPrivacyTermsWithdrawal
IndustryBakery chainRehab centresRestaurant chainElectrical contractorOnline shopFood producerMetal engineeringElectronics maker

Real exampleA real German company’s website, checked with the free quick check on 24 Oct 2026. Name and address removed.

Homepage · 24 Oct 2026

feinkost-hersteller.example

Poor overall: 20 things to improve, with Conversion scoring lowest. Start with one action, one name. Quick audit: only the code-measured checks ran, so design and copy judgement is still missing. 5 checks need a person to confirm.

critical
1
major
8
minor
11
Checked53%quick audit
52of 100Poor2 high-impact fixes you can make in minutes

Scores by audit

If you only do three things

  1. One action, one name

    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.

  2. Controls announce what they are

    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.

  3. Forms can be completed by everyone

    Forms are where accessibility problems cost you leads and sales directly.

    Fix→Give every field a visible label, mark required fields in text, link error messages to their field, and use the right autocomplete attributes.

Accessibility

Poor 49/100

Accessibility is where visitors struggle most. I'd start with "controls announce what they are".

  • critical

    Controls announce what they are

    16 controls without a usable accessible name or valid ARIA (button-name, 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.

    For your developer
    • .owl-carousel-book-page > .owl-nav > .owl-next[type="button"][role="presentation"] · Element does not have inner text that is visible to screen readers
    • .owl-products-carousel > .owl-nav > .owl-prev[type="button"][role="presentation"] · Element does not have inner text that is visible to screen readers
    • .owl-products-carousel > .owl-nav > .owl-next[type="button"][role="presentation"] · Element does not have inner text that is visible to screen readers
    • .active.owl-item:nth-child(1) > .item > .item-silde.position-relative > .wn-image-wrap > .wn-item-image.text-center > .aspect-ratio--custom.aspect-ratio > .d-b…

    WCAG 2.2 SC 4.1.2, 2.5.3

  • major

    Forms can be completed by everyone

    1 form field has no persistent label; the placeholder disappears as soon as people type. Forms are where accessibility problems cost you leads and sales directly.

    Fix→Give every field a visible label, mark required fields in text, link error messages to their field, and use the right autocomplete attributes.

    For your developer
    • div.col-12 > form.standard-form > div.form-group > div.form-input > input.form-control · No persistent label (placeholder-only): "E-Mail Adresse*"
    • div.col-12 > form.standard-form > div.form-group > div.form-input > input.form-control · Personal-data field without autocomplete: "E-Mail Adresse*"

    WCAG 2.2 SC 3.3.1, 3.3.2

  • major

    Survives zoom and custom text spacing

    Content scrolls sideways when zoomed (200% zoom); people who zoom in must scroll in two directions to read. 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.

    For your developer
    • page width at 320 px viewport: 320 px (target 320)

    WCAG 2.2 SC 1.4.4, 1.4.10

  • major

    Focus is always visible

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

    For your developer
    • div.item > div.row > div.col-12:nth-of-type(2) > div.col-padding:nth-of-type(2) > a.wn-button · No visible focus change: "Jetzt Rabattcode herunterladen!"
    • div.item > div.row > div.col-12:nth-of-type(2) > div.col-padding:nth-of-type(2) > a.wn-button · No visible focus change: "Jetzt Cashback sichern!"
    • div.item > div.row > div.col-12:nth-of-type(2) > div.col-padding:nth-of-type(2) > a.wn-button · No visible focus change: "Hier zum Cashback & Gewinnspiel"
    • div.rcpBookPage-wrap > div.rcpBookPage-content:nth-of-type(2) > div.owl-carousel > div.owl-nav:nth-of-type(2) > button.owl-next:nth-of-type(2) · No visible foc…

    WCAG 2.2 SC 2.4.7, 2.4.11

  • minor

    Predictable across pages

    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.

    For your developer
    • Navigation differs from the homepage

    WCAG 2.2 SC 3.2.1, 3.2.2

  • minor

    Structure is real, not just visual

    2 h1 headings. 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>.

    For your developer
    • h1 count: 2 (target 1)

    WCAG 2.2 SC 1.3.1, 1.3.2

Copy

Poor 54/100

Copy is where visitors struggle most. I'd start with "c6 · buttons and links say what happens".

  • major

    C6 · Buttons and links say what happens

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

    For your developer
    • div.wn-rcpList-outer > div.col-12:nth-of-type(2) > div.col-12:nth-of-type(1) > div.wn-textbox > a.text-color-green · "Mehr erfahren" → https://www.[brand]…
    • div.parallax-container > div.container:nth-of-type(1) > div.row > div.col > a.wn-button · "Weiterlesen" → https://feinkost-hersteller.example/rezepte/special/alles_ueb…
    • div.parallax-container > div.container:nth-of-type(1) > div.row > div.col > a.wn-button · "Weiterlesen" → https://feinkost-hersteller.example/rezepte/special/unsere_vi…
    • div.row > div.col-12:nth-of-type(1) > div.wn-image-wrap > div.wn-image-content > a · "Mehr erfahren" → https://feinkost-hersteller.example/nachhaltigkeit_bei_hengstenb…

    WCAG 2.2 SC 2.4.4

  • minor

    C3 · About the reader, not the company

    Homepage says "you" 10× and "we" 16×. 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.

    For your developer
    • reader words: 10
    • company words: 16

    Government Digital Service: GOV.UK content design: writing for the web

  • minor

    C5 · Plain, readable language

    Harder to read than needed: Amstad 48 (aim ≥ 60). 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.

    For your developer
    • Amstad (Flesch, German): 48.21
    • average sentence length: 18.86 words (target 20)

    plainlanguage.gov: Federal Plain Language Guidelines

SEO

Needs work 65/100

SEO needs some love. I'd start with "core web vitals in the green".

  • major

    Core Web Vitals in the green

    Lab data: LCP 16247 ms, CLS 0.03, Total Blocking Time 11 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.

    For your developer
    • LCP (lab, mobile): 16246.74 ms (target 2500)
    • CLS: 0.03 (target 0.1)
    • Total Blocking Time (lab, stands in for INP): 11 ms (target 200)

    web.dev: Core Web Vitals thresholds (LCP 2.5 s, INP 200 ms, CLS 0.1)

  • minor

    Unique, descriptive titles and descriptions

    1 page(s) without a meta description; 5 description(s) outside 70–170 characters; 7 title(s) outside 15–65 characters. 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.

    For your developer
    • Title 9 characters: "Aktuelles"
    • Title 7 characters: "Kontakt"
    • Title 12 characters: "Werksverkauf"
    • No meta description

    Google Search Central: Influencing title links in search results

  • minor

    Images are light and described

    Image delivery can improve: Improve image delivery (Est savings of 5,661 KiB); Image elements do not have explicit `width` and `height`; Serves images with low resolution. 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.

    For your developer
    • Improve image delivery (Est savings of 5,661 KiB)
    • Image elements do not have explicit `width` and `height`
    • Serves images with low resolution

    Google Search Central: SEO Starter Guide

UI

Needs work 67/100

UI needs some love. I'd start with "a deliberate type scale".

  • minor

    A deliberate type scale

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

    For your developer
    • font families (excl. icons): 4
    • distinct font sizes: 7 (target 8)
    • sizes on a modular scale: 100 %
    • Families: NiveauGroteskRegular, NiveauGroteskBold, NiveauGroteskMedium, Shelby

    Adam Wathan & Steve Schoger: Refactoring UI — hierarchy, spacing systems, limited palettes

  • minor

    Interactions feel direct

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

    For your developer
    • div.container > div.wn-navbar-navigation:nth-of-type(2) > ul.list-inline:nth-of-type(2) > li.list-inline-item:nth-of-type(1) > div.dropdown · "Produkte": no ch…
    • div.container > div.wn-navbar-navigation:nth-of-type(2) > ul.list-inline:nth-of-type(2) > li.list-inline-item:nth-of-type(2) > div.dropdown · "Rezepte": no cha…
    • div.container > div.wn-navbar-navigation:nth-of-type(2) > ul.list-inline:nth-of-type(2) > li.list-inline-item:nth-of-type(3) > div.dropdown · "Nachhaltigkeit":…
    • div.container > div.wn-navbar-navigation:nth-of-type(2) > ul.list-inline:nth-of-type(2) > li.list-inline-item:nth-of-type(4) > div.dropdown · "Über uns": no ch…

    Apple: Designing Fluid Interfaces (WWDC 2018)

  • minor

    Spacing on a system

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

    For your developer
    • spacing on 4 px grid: 48 % (target 80)
    • distinct left text edges: 10 (target 4)

    Adam Wathan & Steve Schoger: Refactoring UI — hierarchy, spacing systems, limited palettes

Conversion

Not checked yet 23% measured

Conversion is where visitors struggle most. I'd start with "fast on a phone".

  • major

    Fast on a phone

    Landing page: LCP 16.2 s, 16.0 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.

    For your developer
    • LCP (mobile, lab): 16246.74 ms (target 2500)
    • page weight: 16 MB (target 2)

    web.dev: Core Web Vitals thresholds (LCP 2.5 s, INP 200 ms, CLS 0.1)

  • minor

    Conversions can be measured

    No analytics found, so conversions cannot be measured or improved. Without measurement you can’t tell which changes help, so improvements become guesswork.

    Fix→Install privacy-friendly analytics and track your key actions (button clicks, form submissions, bookings) as conversion events.

    For your developer
    • analytics hosts: 0

    Corey Haines (marketingskills): cro, signup, popups and offers skills

  • minor

    Forms ask only what they need

    newsletter form asks for 1 field; 1 field(s) without the right keyboard type. Every extra form field lowers completion, and wrong field types make phones show the wrong keyboard.

    Fix→Ask only for what you need now (five fields or fewer for a lead form), mark optional fields, and use type="email"/"tel" with autocomplete.

    For your developer
    • div.row > div.col-12:nth-of-type(2) > div.row > div.col-12 > form.standard-form · E-Mail Adresse*
    • div.col-12 > form.standard-form > div.form-group > div.form-input > input.form-control · type="text" for "E-Mail Adresse*"

    Baymard Institute: Checkout usability research (guest checkout, form field count)

UX

Not checked yet 29% measured

UX is where visitors struggle most. I'd start with "one action, one name".

  • major

    One action, one name

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

    For your developer
    • "aktuelles" ×64, "suchbegriff" ×1, "produkte" ×1, "rezepte" ×1, "nachhaltigkeit" ×1, "über uns" ×1, "karriere" ×1
    • "kontakt" ×32, "suchbegriff" ×1, "produkte" ×1, "rezepte" ×1, "nachhaltigkeit" ×1, "über uns" ×1, "karriere" ×1, "wo finde ich den produktionscode" ×1, "hier k…
    • "werksverkauf" ×32, "suchbegriff" ×1, "produkte" ×1, "rezepte" ×1, "nachhaltigkeit" ×1, "über uns" ×1, "karriere" ×1
    • "produkte" ×35, "alle produkte" ×34, "newsletter" ×16, "unsere produkte" ×2, "mehr erfahren" ×1, "suchbegriff" ×1, "rezepte" ×1, "nachhaltigkeit" ×1, "über uns…

    Jakob Nielsen, NN/g: 10 Usability Heuristics for User Interface Design

  • major

    Mobile is a first-class experience

    First action 3.1 screens down. 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.

    For your developer
    • div.col-padding > div.imageText-wrap > div.imageText-content:nth-of-type(2) > div.pt-15:nth-of-type(2) > a.wn-button · First prominent action "Jetzt Rabattcode…

    NN/g: Mobile UX guidelines (touch targets, content priority)

Your 30-minute plan

0 of 9 done

Small fixes with a big pay-off. Tick them off as you go.

That's it from me. Make a few changes, run me again, and I'll tell you what moved.

Run your own audit