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

industrie-elektronik.example

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.

critical
2
major
5
minor
15
Checked53%quick audit
54of 100Poor3 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. Comfortable body text

    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.

  3. Text and controls are readable

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

Accessibility

Poor 44/100

Accessibility is where visitors struggle most. I'd start with "text and controls are readable".

  • critical

    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.

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

    For your developer
    • .cell.small-6 > p:nth-child(2) · #797979 on #ffffff is 4.35:1, needs 4.5:1 (try #747474)
    • .cell.small-6 > p:nth-child(3) > strong · "Mit der Erfahrung aus traditionellen Mä…": #797979 on #ffffff is 4.35:1, needs 4.5:1 (try #747474)
    • .cell.small-6 > p:nth-child(4) · #797979 on #ffffff is 4.35:1, needs 4.5:1 (try #747474)

    WCAG 2.2 SC 1.4.3, 1.4.11

  • critical

    Everything works with a keyboard

    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.

    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.

    For your developer
    • focus stops: 81
    • unreachable controls: 3 (target 0)
    • backward jumps: 0 (target 1)
    • #slick-slide-control01 · Not reachable with Tab: "2"

    WCAG 2.2 SC 2.1.1, 2.1.2

  • major

    Structure is real, not just visual

    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.

    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: 1 (target 1)

    WCAG 2.2 SC 1.3.1, 1.3.2

  • major

    Focus is always visible

    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.

    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
    • #slick-slide-control00 · No visible focus change: "1"
    • div.cell:nth-of-type(3) > div.article > div.teaser-wrapper > div.media-wrapper:nth-of-type(1) > a · Focus hidden behind #cmpwrapper: ""
    • div.article > div.teaser-wrapper > div.media-wrapper:nth-of-type(1) > div.text-wrapper > a · Focus hidden behind #cmpwrapper: "QUALITÄTSSICHERUNG IN DER ELEKTR…
    • div.cell:nth-of-type(3) > div.article > div.teaser-wrapper > div.link-wrapper:nth-of-type(2) > a.btn · Focus hidden behind #cmpwrapper: "WEITERLESEN"

    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

Copy

Poor 46/100

Copy is where visitors struggle most. I'd start with "c5 · plain, readable language".

  • major

    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.

    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): 0.4
    • average sentence length: 29.24 words (target 20)

    plainlanguage.gov: Federal Plain Language Guidelines

  • minor

    C2 · Specific beats superlative

    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.

    Fix→Replace each superlative with a fact: a number, a name, a result or a timeframe.

    For your developer
    • hype words per 200 words: 1.08 (target 1)
    • div.article > div.teaser-wrapper > div.media-wrapper:nth-of-type(1) > div.text-wrapper > p · Vom 10. bis 13. November zeigt [brand] auf der electronica in München…
    • div.s-image-text-over:nth-of-type(10) > div.left-wrapper:nth-of-type(2) > div.text-wrapper:nth-of-type(2) > a.inner-link > p · [brand] bietet Ihnen individuelle A…
    • div.s-text-headline:nth-of-type(14) > div.grid-container:nth-of-type(2) > div.grid-x > div.cell > p:nth-of-type(4) · Ihre Maschinen sind einzigartig. Ihre HMI-…

    NN/g: How Users Read on the Web (concise, scannable, objective)

  • minor

    C3 · About the reader, not the company

    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.

    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: 3
    • company words: 6

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

  • minor

    C6 · Buttons and links say what happens

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

    For your developer
    • div.cell:nth-of-type(1) > div.article > div.teaser-wrapper > div.link-wrapper:nth-of-type(2) > a.btn · "WEITERLESEN" → https://industrie-elektronik.example/news/[brand]-auf…
    • div.grid-container:nth-of-type(3) > div.grid-x > div.inner-wrapper > p:nth-of-type(2) > a · "...MEHR" → https://industrie-elektronik.example/branchen/automation-robotics/

    WCAG 2.2 SC 2.4.4

UI

Poor 50/100

UI is where visitors struggle most. I'd start with "comfortable body text".

  • major

    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.

    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.

    For your developer
    • div.s-text-headline:nth-of-type(4) > div.grid-container:nth-of-type(2) > div.grid-x > div.cell > p:nth-of-type(1) · ✗ body 15px (desktop) · ✗ body 13px (mobile…

    Matthew Butterick: Practical Typography — line length, point size, line spacing

  • minor

    Size-aware tracking and leading

    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.

    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.

    For your developer
    • div.content > div.grid-x > div.cell:nth-of-type(1) > div.newsletter-wrapper > span.title · 40px, letter-spacing normal, line-height 56px: "GET IN TOUCH"

    Apple: Designing Fluid Interfaces (WWDC 2018)

  • 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
    • #slick-slide-control00 · "1": no change until release
    • #slick-slide-control01 · "2": no change until release
    • #slick-slide-control02 · "3": no change until release
    • #slick-slide-control03 · "4": no change until release

    Apple: Designing Fluid Interfaces (WWDC 2018)

  • minor

    A deliberate type scale

    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.

    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): 3
    • distinct font sizes: 7 (target 8)
    • sizes on a modular scale: 100 %
    • Families: Univers LT W01_45 Light, Univers LT W01_75 Black, Univers LT W01_65 Bold

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

  • minor

    Spacing on a system

    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.

    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 5 px grid: 74 % (target 80)
    • distinct left text edges: 8 (target 4)

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

SEO

Good 72/100

SEO is solid with a few rough edges. I'd start with "core web vitals in the green".

  • minor

    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.

    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): 2604.46 ms (target 2500)
    • CLS: 0 (target 0.1)
    • Total Blocking Time (lab, stands in for INP): 0 ms (target 200)

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

  • minor

    Structured data for what the business is

    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.

    For your developer
    • JSON-LD blocks: 0

    Google Search Central: Structured data general guidelines

  • minor

    Looks right when shared

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

    For your developer
    • No og:image

    Google Search Central: SEO Starter Guide

  • minor

    Images are light and described

    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.

    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 708 KiB)
    • Image elements do not have explicit `width` and `height`
    • Serves images with low resolution

    Google Search Central: SEO Starter Guide

UX

Not checked yet 38% measured

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

  • major

    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.

    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
    • "automation robotics" ×48, "branchen" ×2, "produkte" ×2, "plattformen" ×2, "unternehmen" ×2, "media" ×1, "aktuelles" ×1, "downloads" ×1, "business" ×1, "materi…
    • "energy smart infrastructure" ×48, "branchen" ×2, "produkte" ×2, "plattformen" ×2, "unternehmen" ×2, "media" ×1, "aktuelles" ×1, "downloads" ×1, "business" ×1,…
    • "medtech" ×48, "branchen" ×2, "produkte" ×2, "plattformen" ×2, "unternehmen" ×2, "media" ×1, "aktuelles" ×1, "downloads" ×1, "business" ×1, "material complianc…
    • "mobility agriculture" ×48, "branchen" ×2, "produkte" ×2, "plattformen" ×2, "unternehmen" ×2, "media" ×1, "aktuelles" ×1, "downloads" ×1, "business" ×1, "mater…

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

  • minor

    Visitors stay in control

    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.

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

    For your developer
    • #slick-slide01 · 6 changes in 6 s without input
    • #slick-slide00 · 3 changes in 6 s without input
    • div.s-emotion:nth-of-type(3) > div.emotion-slider:nth-of-type(2) > div.slick-list > div.slick-track · 3 changes in 6 s without input

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

  • minor

    Mobile is a first-class experience

    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.

    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
    • #slick-slide-control00 · First prominent action "1" at 0.3 screens down, 20×20px
    • #slick-slide-control00 · 20px tall: "1"
    • #slick-slide-control01 · 20px tall: "2"
    • #slick-slide-control02 · 20px tall: "3"

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

Conversion

Not checked yet 11% measured

Conversion needs some love. I'd start with "fast on a phone".

  • minor

    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.

    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): 2604.46 ms (target 2500)
    • page weight: 1.52 MB (target 2)

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

Your 30-minute plan

0 of 13 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