Website review, no card needed

klebemeister.eu logo

klebemeister.eu website review

Visit site (opens in a new tab)Reviewed 8 November 202631 issues · 80 checks

This review found 31 issues worth fixing on klebemeister.eu, 12 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.

  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
2.3 s2.1 sMay 16Oct 312.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.3 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
172 ms138 msMay 16Oct 31168 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026143 ms
May 23, 2026144 ms
May 30, 2026146 ms
Jun 6, 2026146 ms
Jun 13, 2026145 ms
Jun 20, 2026143 ms
Jun 27, 2026142 ms
Jul 4, 2026142 ms
Jul 11, 2026145 ms
Jul 18, 2026148 ms
Jul 25, 2026148 ms
Aug 1, 2026148 ms
Aug 8, 2026151 ms
Aug 15, 2026150 ms
Aug 22, 2026147 ms
Aug 29, 2026152 ms
Sep 5, 2026148 ms
Sep 12, 2026153 ms
Sep 19, 2026156 ms
Sep 26, 2026157 ms
Oct 3, 2026162 ms
Oct 10, 2026161 ms
Oct 17, 2026163 ms
Oct 24, 2026167 ms
Oct 31, 2026168 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 klebemeister.eu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. klebemeister.eu at 0.4 s0.4 s
  2. klebemeister.eu at 0.8 s0.8 s
  3. klebemeister.eu at 1.1 s1.1 s
  4. klebemeister.eu at 1.5 s1.5 s
  5. klebemeister.eu at 1.9 s1.9 s
  6. klebemeister.eu at 2.3 s2.3 s
  7. klebemeister.eu at 2.6 s2.6 s
  8. klebemeister.eu at 3.0 s3.0 s

Speed

8 to fix66
  • Reduce unused JavaScript

    1.5 s · 432 KiB

    About 432 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Use efficient cache lifetimes

    1.3 s · 379 KiB

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

  • 10,652 HTML elements

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

  • Improve image delivery

    450 ms · 960 KiB

    11 images could be 960 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Mobile performance score: 66

    66/100

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

  • Render-blocking requests

    550 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.

  • Main-thread work: 3.3 s

    A phone's processor spends 3.3 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 4 long tasks on the main thread

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Omniconvert and Cookiebot and others), adding 935 KiB and 446 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 221 KiB

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

  • Legacy JavaScript

    150 ms · 28 KiB

    Polyfills for old browsers add 28 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify JavaScript

    150 ms · 4 KiB

    4 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    17 KiB

    17 KiB JavaScript is shipped twice across bundles.

  • 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 checks passed
  • Server response: 30 ms

    30 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 12.6 s

    12.6 s

    Your largest element takes 12.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 13.7 s

    13.7 s

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

  • Speed Index: 6.1 s

    6.1 s

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

    The first text or image appears after 2.1 s on a phone. Good is under 1.8 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) 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 143 ms to 168 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -1%

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

6 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 167 ms

    167 ms

    Real visitors wait 167 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 TTFB: 527 ms

    527 ms

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

  • Total Blocking Time: 163 ms

    163 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix57
  • 4 images far larger than shown

    845 KiB

    4 images are downloaded at several times the size a phone draws them, for example 30-16516161.jpg at 2,639 px wide, shown at 72 px. Resized copies would save about 845 KiB.

  • Page weight: 3.4 MB in 151 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 151 requests on a phone: images 1.5 MB (37), scripts 863 KiB (62) and other files 703 KiB (32). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    klebemeister_banner_2026_84a04302-3e34-4b94-b56f-0ed61964e01 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).

  • 8 images below the first screen load straight away

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

  • About 1.0 g of CO₂ per visit

    0.95 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

9 to fixGoogle 8191
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 12 text elements with low contrast

    12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 9 images without alt text

    9 images have no alt text, which hurts accessibility and image search.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 links without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Table header text should not be empty (1 element)

    Table header text should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.

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

    Elements with visible text labels do not have matching accessible names. (1 element).

  • <td> elements in a large <table> do not have table headers.

    <td> elements in a large <table> do not have table headers. (1 element).

1 checks passed
  • 56 automated accessibility rules passed

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

SEO

1 to fixGoogle 9293
  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “klebemeister.eu - Online Shop für Maler - Abdeckbänder, Maskertape uvm”.

  • 364 internal links, 5 external

    The homepage links to 364 pages on klebemeister.eu and 5 external pages.

7 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “klebemeister.eu I Großhandel & Online Shop I für Maler und Lackierer I Abdeckbänder, Masker Tape, Soft Tape der Marke k…”.

  • One H1 headline

    Your main headline reads: “klebemeister.eu”.

  • Canonical URL set

    The canonical URL is https://klebemeister.eu/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://klebemeister.eu/sitemap.xml.

AI search readiness

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://klebemeister.eu/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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 “Invalid left-hand side in assignment”.

2 checks passed
  • Tap targets are thumb-sized

    36 of 42 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 1,369 words of copy

    The homepage carries about 1,369 words of visible text.

5 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “[email protected]”.

  • 5 short forms

    5 short forms (2 fields at most) are right on the homepage.

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

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

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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.

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 cookies (measured from a US location before any click).

  • 31 other companies contacted

    Loading the homepage contacts 31 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 klebemeister.eu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Essential Announcer · Omniconvert Explore · Frequently Bought · Also Bought · Klaviyo Email Marketing Sms · Essential Announcement Bar · loox.io · activehosted.com · trustpilot.com · hextom.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Bootstrap
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on klebemeister.eu, including 15 speed issues, 1 SEO issue 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

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