Programmable

Website review, no card needed

wilka.de logo

wilka.de website review

Visit site (opens in a new tab)Reviewed 18 October 202622 issues · 67 checks

This review found 22 issues worth fixing on wilka.de, 7 of them high impact, across 67 checks. The most urgent: use efficient cache lifetimes. 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

Site score

85B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
880 ms716 msApr 25Oct 10841 ms
Show as table
DateReal-visitor load time (LCP)
Apr 25, 2026810 ms
May 2, 2026788 ms
May 9, 2026780 ms
May 16, 2026799 ms
May 23, 2026735 ms
May 30, 2026743 ms
Jun 6, 2026798 ms
Jun 13, 2026808 ms
Jun 20, 2026850 ms
Jun 27, 2026861 ms
Jul 4, 2026839 ms
Jul 11, 2026808 ms
Jul 18, 2026784 ms
Jul 25, 2026775 ms
Aug 1, 2026747 ms
Aug 8, 2026794 ms
Aug 15, 2026808 ms
Aug 22, 2026858 ms
Aug 29, 2026858 ms
Sep 5, 2026801 ms
Sep 12, 2026786 ms
Sep 19, 2026796 ms
Sep 26, 2026810 ms
Oct 3, 2026844 ms
Oct 10, 2026841 ms
Real-visitor tap response (INP)75th percentile, phones
149 ms123 msApr 25Oct 10134 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026131 ms
May 2, 2026131 ms
May 9, 2026137 ms
May 16, 2026138 ms
May 23, 2026137 ms
May 30, 2026137 ms
Jun 6, 2026145 ms
Jun 13, 2026144 ms
Jun 20, 2026146 ms
Jun 27, 2026144 ms
Jul 4, 2026146 ms
Jul 11, 2026146 ms
Jul 18, 2026146 ms
Jul 25, 2026146 ms
Aug 1, 2026131 ms
Aug 8, 2026135 ms
Aug 15, 2026128 ms
Aug 22, 2026138 ms
Aug 29, 2026133 ms
Sep 5, 2026126 ms
Sep 12, 2026135 ms
Sep 19, 2026132 ms
Sep 26, 2026134 ms
Oct 3, 2026138 ms
Oct 10, 2026134 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

www.wilka.de (opens in a new tab)
Full-page screenshot of wilka.de (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wilka.de at 0.7 s0.7 s
  2. wilka.de at 1.4 s1.4 s
  3. wilka.de at 2.1 s2.1 s
  4. wilka.de at 2.8 s2.8 s
  5. wilka.de at 3.5 s3.5 s
  6. wilka.de at 4.2 s4.2 s
  7. wilka.de at 4.9 s4.9 s
  8. wilka.de at 5.6 s5.6 s

Speed

3 to fix70

  • Use efficient cache lifetimes

    6.6 s · 2.8 MB

    46 files are served with short cache lifetimes, so returning visitors download them again (2.8 MB).

  • Improve image delivery

    2.0 s · 1.7 MB

    12 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.

  • Mobile performance score: 70

    70/100

    Your mobile performance score is 70 (desktop: 54). Pages that score under 90 lose visitors before the first paint.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 50 ms. During a long task the page ignores taps.

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (ccm19.de and move-elevator.de), adding 1 KiB and 0 ms of main-thread time.

2 checks passed

  • Main-thread work: 1.1 s

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

  • Server response: 104 ms

    104 ms

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

Core Web Vitals

3 to fix100

  • Largest Contentful Paint: 8.2 s

    8.2 s

    Your largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “WILKA macht die Welt einfach sicher.”.

  • Speed Index: 6.3 s

    6.3 s

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

  • Time to Interactive: 8.2 s

    8.2 s

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

  • Tap response (INP) held steady for real visitors

    +4%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

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

    1.6 s

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

  • Real-user INP: 111 ms

    111 ms

    Real visitors wait 111 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: 372 ms

    372 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 0.9 s

    0.9 s

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

  • 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

2 to fix75

  • Page weight: 2.8 MB in 49 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 49 requests on a phone: images 2.7 MB (24), scripts 96 KiB (9) and fonts 55 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 7 images in older formats

    7 images (1.6 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.

  • About 0.8 g of CO₂ per visit

    0.81 g

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

2 checks passed

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

1 to fixGoogle 9799

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed

  • Every image has alt text

    All 38 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

4 to fixGoogle 9286

  • No structured data

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

  • 5 H1 headlines

    There are 5 <h1> headlines (“Wir machen die Welt einfach sicher”, “Die Ersatzhelden - Das neue Langlochprogramm” and “WILKA in der Praxis”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 7 links with vague text

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

  • 300 internal links, 36 external

    The homepage links to 300 pages on wilka.de and 36 external pages.

5 checks passed

  • Meta description: 156 characters

    Your meta description is 156 characters: “Als ein führender Hersteller von Schließtechnik entwickelt und produziert WILKA Türschlösser, Zylinder, Schließanlagen …”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “WILKA Schließtechnik: WILKA Schließtechnik GmbH, Velbert”.

  • Canonical URL set

    The canonical URL is https://www.wilka.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://www.wilka.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.wilka.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 (1,140 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83

  • 7 linked pages hidden from search

    https://www.wilka.de/loesungen, https://www.wilka.de/loesungen/anwendungsbereiche, https://www.wilka.de/loesungen/objektloesungen, https://www.wilka.de/loesungen/objektloesungen/ein-und-mehrfamilienhaeuser, https://www.wilka.de/loesungen/objektloesungen/bildung-und-erziehung and https://www.wilka.de/loesungen/objektloesungen/hotels-und-ferienhaeuser and 1 other are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 8 pages without a meta description

    https://www.wilka.de/haendlersuche, https://www.wilka.de/loesungen/anwendungsbereiche, https://www.wilka.de/loesungen/objektloesungen, https://www.wilka.de/loesungen/objektloesungen/ein-und-mehrfamilienhaeuser, https://www.wilka.de/loesungen/objektloesungen/bildung-und-erziehung and https://www.wilka.de/loesungen/objektloesungen/hotels-und-ferienhaeuser and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.wilka.de/haendlersuche has 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 91 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 10087

  • 8 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58

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

    The homepage carries about 727 words of visible text.

3 checks passed

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 35 testimonial or review blocks and 1 customer or partner logo.

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

  • 2 other companies contacted

    Loading the homepage contacts 2 hosts 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 wilka.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

Company

Employees
241
Founded
1865
Headquarters
Velbert

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on wilka.de, including 6 speed issues, 4 SEO issues and 3 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