Website review, no card needed
kleemannlifts.com website review
Visit site (opens in a new tab)Reviewed 3 November 202637 issues · 80 checks
This review found 37 issues worth fixing on kleemannlifts.com, 13 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.7 s |
| Oct 10, 2026 | 3.9 s |
| Oct 17, 2026 | 4.0 s |
| Oct 24, 2026 | 4.0 s |
| Oct 31, 2026 | 4.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 98 ms |
| May 23, 2026 | 99 ms |
| May 30, 2026 | 98 ms |
| Jun 6, 2026 | 100 ms |
| Jun 13, 2026 | 100 ms |
| Jun 20, 2026 | 97 ms |
| Jun 27, 2026 | 96 ms |
| Jul 4, 2026 | 98 ms |
| Jul 11, 2026 | 101 ms |
| Jul 18, 2026 | 101 ms |
| Jul 25, 2026 | 107 ms |
| Aug 1, 2026 | 104 ms |
| Aug 8, 2026 | 99 ms |
| Aug 15, 2026 | 101 ms |
| Aug 22, 2026 | 95 ms |
| Aug 29, 2026 | 94 ms |
| Sep 5, 2026 | 96 ms |
| Sep 12, 2026 | 97 ms |
| Sep 19, 2026 | 96 ms |
| Sep 26, 2026 | 101 ms |
| Oct 3, 2026 | 100 ms |
| Oct 10, 2026 | 105 ms |
| Oct 17, 2026 | 109 ms |
| Oct 24, 2026 | 113 ms |
| Oct 31, 2026 | 117 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
How it loaded on a phone
0.5 s
1.1 s
1.6 s
2.1 s
2.7 s
3.2 s
3.7 s
4.3 s
Speed
Reduce unused JavaScript
1.1 s · 618 KiBAbout 618 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.3 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Cookiebot and JSDelivr CDN and others), adding 1.1 MB and 857 ms of main-thread time.
Use efficient cache lifetimes
750 ms · 182 KiB36 files are served with short cache lifetimes, so returning visitors download them again (182 KiB).
Google Tag Manager adds 673 ms
673 msGoogle Tag Manager costs a phone 673 ms of main-thread work and 904 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.
Font display
450 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).
Reduce unused CSS
300 ms · 66 KiBAbout 66 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
1,869 HTML elements
The page has 1,869 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 175 ms. During a long task the page ignores taps.
Document request latency
64 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Improve image delivery
35 KiB1 image could be 35 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 745 ms of it running JavaScript. That is comfortably low.
Server response: 112 ms
112 msYour server sent the HTML in 112 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 5.3 s
5.3 sReal visitors wait 5.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.2 s
4.2 sReal visitors see the first content after 4.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.3 s
3.3 sReal visitors wait 3.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 9.3 s
9.3 sYour largest element takes 9.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “KLEEMANN Live”.
Time to Interactive: 13.0 s
13.0 sThe page becomes fully interactive after 13.0 s. Good is under 3.8 s.
Speed Index: 6.8 s
6.8 sVisually, the page fills in at 6.8 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) got 47% slower for real visitors
+47%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.8 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 427 ms
427 msScripts block taps and scrolling for 427 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 98 ms to 117 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 121 ms
121 msReal visitors wait 121 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 15.7 MB in 54 requests
15.7 MBYour homepage downloads 15.7 MB in 54 requests on a phone: media 13.3 MB (2), scripts 1.3 MB (17) and fonts 561 KiB (4). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
2.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
1 image far larger than shown
40 KiB1 image is downloaded at several times the size a phone draws it, for example 2.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 40 KiB.
2 images in older formats
2 images (149 KiB) 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 4.4 g of CO₂ per visit
4.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.45 g of CO₂e: 534.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
Unlabelled dropdowns
1 dropdown has no label.
32 text elements with low contrast
32 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (25 elements)
All page content should be contained by landmarks: 25 elements on the page fail this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 36 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 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
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (231 characters)
Your meta description is 231 characters; Google truncates after about 160, so the end of your pitch is cut.
No robots.txt
There is no robots.txt at kleemannlifts.com/robots.txt, the first file search crawlers ask for.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
130 internal links, 6 external
The homepage links to 130 pages on kleemannlifts.com and 6 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Welcome to KLEEMANN”.
Title: 61 characters
Your title is a healthy 61 characters: “Elevators, Cabins, Custom Solutions, Modernization | KLEEMANN”.
Canonical URL set
The canonical URL is https://kleemannlifts.com/.
XML sitemap found
Your XML sitemap is reachable at https://kleemannlifts.com/sitemap.xml.
AI search readiness
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://kleemannlifts.com/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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,900 words), so crawlers that don't run JavaScript still read it.
Other pages
8 pages share a title
/, https://kleemannlifts.com/el, https://kleemannlifts.com/de, https://kleemannlifts.com/fr, https://kleemannlifts.com/ru and https://kleemannlifts.com/tr and 2 others all use the title “Elevators, Cabins, Custom Solutions, Modernization | KLEEMANN”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://kleemannlifts.com/company/contacts has no meta description, so Google writes the search snippet from whatever text it finds.
5 pages share a meta description
https://kleemannlifts.com/de, https://kleemannlifts.com/fr, https://kleemannlifts.com/ru, https://kleemannlifts.com/tr and https://kleemannlifts.com/ro use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 77 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
8 small tap targets
8 of 32 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”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
A 10-field form
Your longest form asks for 10 fields (4 required). Every extra field lowers completion.
About 2,119 words of copy
The homepage carries about 2,119 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Ask for a Quote”.
5 calls to action
The homepage has 5 calls to action, for example “Apply Now”, “Contact” and “Ask for a Quote”.
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks and 1 customer or partner logo.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 kleemannlifts.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Drupal
- Analytics
- Google Tag Manager
- Hosting
- Hetzner
Company
- Founded
- 1983
- Headquarters
- Kilkis Municipality
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 kleemannlifts.com, including 19 speed issues, 3 SEO issues and 1 conversion gap. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.