Website review, no card needed

leg-wohnen.de logo

leg-wohnen.de website review

Visit site (opens in a new tab)Reviewed 27 October 202625 issues · 78 checks

This review found 25 issues worth fixing on leg-wohnen.de, 7 of them high impact, across 78 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.7 s1.6 sMay 9Oct 241.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.7 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
100 ms93 msMay 9Oct 2495 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202695 ms
May 16, 202696 ms
May 23, 202696 ms
May 30, 202696 ms
Jun 6, 202696 ms
Jun 13, 202697 ms
Jun 20, 202698 ms
Jun 27, 202698 ms
Jul 4, 202698 ms
Jul 11, 202697 ms
Jul 18, 202697 ms
Jul 25, 202697 ms
Aug 1, 202697 ms
Aug 8, 202698 ms
Aug 15, 202699 ms
Aug 22, 202698 ms
Aug 29, 202698 ms
Sep 5, 202699 ms
Sep 12, 202699 ms
Sep 19, 202699 ms
Sep 26, 202697 ms
Oct 3, 202696 ms
Oct 10, 202695 ms
Oct 17, 202694 ms
Oct 24, 202695 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 leg-wohnen.de (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. leg-wohnen.de at 0.4 s0.4 s
  2. leg-wohnen.de at 0.9 s0.9 s
  3. leg-wohnen.de at 1.3 s1.3 s
  4. leg-wohnen.de at 1.8 s1.8 s
  5. leg-wohnen.de at 2.2 s2.2 s
  6. leg-wohnen.de at 2.7 s2.7 s
  7. leg-wohnen.de at 3.1 s3.1 s
  8. leg-wohnen.de at 3.6 s3.6 s

Speed

4 to fix94
  • Render-blocking requests

    1.0 s

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

  • Improve image delivery

    1.3 MB

    7 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    530 ms · 79 KiB

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

  • Usercentrics CMP adds 294 ms

    294 ms

    Usercentrics CMP costs a phone 294 ms of main-thread work and 233 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 1 third-party service on the page

    1 third-party service load with your homepage (Usercentrics CMP), adding 233 KiB and 294 ms of main-thread time.

  • 4 long tasks on the main thread

    4 long tasks block the main thread while loading, the longest for 166 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    165 KiB

    2 files are served with short cache lifetimes, so returning visitors download them again (165 KiB).

  • Reduce unused JavaScript

    165 KiB

    About 165 KiB of JavaScript is downloaded but never used on this page.

  • Font display

    150 ms

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

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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.

3 checks passed
  • Mobile performance score: 94

    94/100

    Your mobile performance score is 94 (desktop: 90). That is in Google's “good” band (90 and up).

  • Main-thread work: 1.6 s

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

  • Server response: 8 ms

    8 ms

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

Core Web Vitals

3 to fix100
  • Time to Interactive: 8.3 s

    8.3 s

    The page becomes fully interactive after 8.3 s. Good is under 3.8 s.

  • Speed Index: 4.6 s

    4.6 s

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

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -1%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 95 ms to 95 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-10-24, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

10 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: 1.2 s

    1.2 s

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

  • Real-user INP: 88 ms

    88 ms

    Real visitors wait 88 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: 1.0 s

    1.0 s

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

  • Real-user TTFB: 457 ms

    457 ms

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

  • Total Blocking Time: 199 ms

    199 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 1.7 s

    1.7 s

    Your largest element renders in 1.7 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Als großer deutscher Vermieter bieten wir rund einer halben…”.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 7.8 MB in 47 requests

    7.8 MB

    Your homepage downloads 7.8 MB in 47 requests on a phone: media 5.3 MB (2), images 1.8 MB (19) and scripts 351 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (108 KiB) is 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.

  • 1 image below the first screen load straight away

    1 image further down the page (58 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.2 g of CO₂ per visit

    2.21 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.21 g of CO₂e: 265.8 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

3 to fixGoogle 8895
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • 3 links without text

    3 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

4 to fixGoogle 8584
  • Title is long (90 characters)

    Your title is 90 characters, so Google will cut it off around 60: “Wohnungen, Stellplätze und Gewerbeflächen an über 200 Standorten in NRW und darüber hinaus”.

  • No structured data

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 108 internal links, 25 external

    The homepage links to 108 pages on leg-wohnen.de and 25 external pages.

5 checks passed
  • Meta description: 114 characters

    Your meta description is 114 characters: “Sie suchen eine neue Mietwohnung? Durchsuchen Sie unser gesamtes Wohnungsangebot und finden Sie Ihr neues Zuhause!”.

  • One H1 headline

    Your main headline reads: “Aktuelle Mieterinfos und neue Projekte”.

  • Canonical URL set

    The canonical URL is https://www.leg-wohnen.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://leg-wohnen.de/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://www.leg-wohnen.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.

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (761 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 2 linked pages hidden from search

    https://www.leg-wohnen.de/immobilien/mietwohnungen and https://www.leg-wohnen.de/immobilien/stellplaetze-garagen are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 10 pages without a meta description

    https://www.leg-wohnen.de/immobilien/mietwohnungen, https://www.leg-wohnen.de/immobilien/favoriten, https://www.leg-wohnen.de/mieterservice/kontakt, https://www.leg-wohnen.de/mieterservice/meine-leg, https://www.leg-wohnen.de/eigentumswohnungen-wilhelmshaven and https://www.leg-wohnen.de/neubau/bonn-westside and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://www.leg-wohnen.de/mieterservice, https://www.leg-wohnen.de/immobilien/mietwohnungen, https://www.leg-wohnen.de/immobilien/stellplaetze-garagen, https://www.leg-wohnen.de/immobilien/gewerbeimmobilien, https://www.leg-wohnen.de/mieterservice/kontakt and https://www.leg-wohnen.de/neubau and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://www.leg-wohnen.de/neubau/bremen-tabakquartier and https://www.leg-wohnen.de/neubau/essen-literatur-quartier took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8887
  • 5 small tap targets

    5 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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 analytics detected

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • 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 630 words of copy

    The homepage carries about 630 words of visible text.

2 checks passed
  • 1 short form

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

  • Social proof on the page

    Social proof on the homepage: 2 testimonial or review blocks and 1 trust badge.

Privacy and tracking

  • 5 other companies contacted

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

2 checks passed
  • Consent tool: Usercentrics

    A consent management tool (Usercentrics) loads with the page.

  • 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 leg-wohnen.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
TYPO3 CMS
Framework
jQuery
Hosting
Hetzner

Company

Founded
1970
Headquarters
Düsseldorf

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on leg-wohnen.de, including 7 speed issues, 4 SEO issues and 4 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