Website review, no card needed

lederei-waldsee.de logo

lederei-waldsee.de website review

Visit site (opens in a new tab)Reviewed 13 November 202637 issues · 79 checks

This review found 37 issues worth fixing on lederei-waldsee.de, 9 of them high impact, across 79 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.1 s786 msMay 23Nov 7881 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026871 ms
May 30, 2026962 ms
Jun 6, 2026998 ms
Jun 13, 2026980 ms
Jun 20, 2026981 ms
Jun 27, 2026910 ms
Jul 4, 2026920 ms
Jul 11, 20261.0 s
Jul 18, 20261.0 s
Jul 25, 2026989 ms
Aug 1, 2026936 ms
Aug 8, 2026879 ms
Aug 15, 2026821 ms
Aug 22, 2026911 ms
Aug 29, 2026931 ms
Sep 5, 2026934 ms
Sep 12, 20261.0 s
Sep 19, 2026939 ms
Sep 26, 2026938 ms
Oct 3, 2026853 ms
Oct 10, 2026841 ms
Oct 17, 2026826 ms
Oct 24, 2026820 ms
Oct 31, 2026895 ms
Nov 7, 2026881 ms
Real-visitor tap response (INP)75th percentile, phones
109 ms77 msMay 23Nov 788 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202681 ms
May 30, 202691 ms
Jun 6, 202691 ms
Jun 13, 202686 ms
Jun 20, 202687 ms
Jun 27, 202687 ms
Jul 4, 202691 ms
Jul 11, 2026100 ms
Jul 18, 2026105 ms
Jul 25, 202695 ms
Aug 1, 202696 ms
Aug 8, 202690 ms
Aug 15, 202687 ms
Aug 22, 202693 ms
Aug 29, 202692 ms
Sep 5, 202687 ms
Sep 12, 202694 ms
Sep 19, 202694 ms
Sep 26, 202693 ms
Oct 3, 202688 ms
Oct 10, 202688 ms
Oct 17, 202686 ms
Oct 24, 202687 ms
Oct 31, 202689 ms
Nov 7, 202688 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of lederei-waldsee.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lederei-waldsee.de at 1.7 s1.7 s
  2. lederei-waldsee.de at 3.4 s3.4 s
  3. lederei-waldsee.de at 5.0 s5.0 s
  4. lederei-waldsee.de at 6.7 s6.7 s
  5. lederei-waldsee.de at 8.4 s8.4 s
  6. lederei-waldsee.de at 10.1 s10.1 s
  7. lederei-waldsee.de at 11.8 s11.8 s
  8. lederei-waldsee.de at 13.4 s13.4 s

Speed

7 to fix64
  • Render-blocking requests

    1.3 s

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    928 KiB

    10 images could be 928 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Font display

    500 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 500 ms).

  • Reduce unused JavaScript

    310 ms · 77 KiB

    About 77 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 310 ms faster on a phone.

  • Reduce unused CSS

    310 ms · 47 KiB

    About 47 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.

  • 2,431 HTML elements

    The page has 2,431 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Legacy JavaScript

    7 KiB

    Polyfills for old browsers add 7 KiB JavaScript that modern phones do not need.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • 1 third-party service on the page

    1 third-party service load with your homepage (FontAwesome CDN), adding 10 KiB and 2 ms of main-thread time.

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 320 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

    Your server sent the HTML in 1 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Cumulative Layout Shift: 0.69

    0.69

    The layout shifts by 0.69 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 5.7 s

    5.7 s

    Visually, the page fills in at 5.7 s (Speed Index). Good is under 3.4 s.

  • Largest Contentful Paint: 3.1 s

    3.1 s

    Your largest element takes 3.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “In unserer Lederei verschmelzen traditionelles Handwerk mit…”. Most of its time is element render delay (2.5 s).

  • First Contentful Paint: 2.0 s

    2.0 s

    The first text or image appears after 2.0 s on a phone. Good is under 1.8 s.

  • Tap response (INP) held steady for real visitors

    +3%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 81 ms to 88 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -3%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 0.9 s

    0.9 s

    Real visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 87 ms

    87 ms

    Real visitors wait 87 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.7 s

    0.7 s

    Real visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 504 ms

    504 ms

    Real visitors wait 504 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Time to Interactive: 3.1 s

    3.1 s

    The page is fully interactive after 3.1 s.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix53
  • Page weight: 11.2 MB in 96 requests

    11.2 MB

    Your homepage downloads 11.2 MB in 96 requests on a phone: images 10.9 MB (87), scripts 121 KiB (1) and fonts 72 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 22 images in older formats

    22 images (1.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 8 images below the first screen load straight away

    8 images further down the page (338 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.2 g of CO₂ per visit

    3.17 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.17 g of CO₂e: 380.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9693
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • All page content should be contained by landmarks (5 elements)

    All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 2 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8568
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (27 characters)

    Your title is only 27 characters: “Lederei Waldsee Online-Shop”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 4 links crawlers can't follow

    4 links have no real href, so search engines can't follow them.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 75 internal links, 4 external

    The homepage links to 75 pages on lederei-waldsee.de and 4 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://lederei-waldsee.de/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://lederei-waldsee.de/sitemap_index.xml.

AI search readiness

2 to fix75
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • Some text only appears after JavaScript runs

    43%

    The HTML your server sends has 206 of the 479 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

    There is no https://lederei-waldsee.de/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

1 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Other pages

4 to fix75
  • 1 linked page hidden from search

    https://lederei-waldsee.de/note is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://lederei-waldsee.de/schuhe-clogs and https://lederei-waldsee.de/schuhe-clogs/lammfell-boots all use the title “Lammfell Boots , Lammfellstiefel , Echt Lammfell , Lammfellschuhe | L…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages without a meta description

    https://lederei-waldsee.de/note, https://lederei-waldsee.de/schuhe-clogs, https://lederei-waldsee.de/guertel, https://lederei-waldsee.de/wohnaccessoires, https://lederei-waldsee.de/lederwaren and https://lederei-waldsee.de/fasnet and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://lederei-waldsee.de/schuhe-clogs, https://lederei-waldsee.de/guertel, https://lederei-waldsee.de/wohnaccessoires, https://lederei-waldsee.de/lederwaren, https://lederei-waldsee.de/fasnet and https://lederei-waldsee.de/tierfelle and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 40 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://use.fontawesome.com/releases/v5.1.0/css/all.css' from origin 'https://lederei-wald…”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    134 of 139 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix44
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 479 words of copy

    The homepage carries about 479 words of visible text.

2 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 1 other company contacted

    Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at lederei-waldsee.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2021.

Stack

Hosting
Neue Medien Muennich GmbH

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on lederei-waldsee.de, including 11 speed issues, 5 SEO issues and 6 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25