Website review, no card needed

kaeltebringer.fr logo

kaeltebringer.fr website review

Visit site (opens in a new tab)Reviewed 6 November 202636 issues · 84 checks

This review found 36 issues worth fixing on kaeltebringer.fr, 10 of them high impact, across 84 checks. The most urgent: aRIA attributes must conform to valid values (1 element). 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
3.0 s2.9 sJun 27Jul 253.0 s
Show as table
DateReal-visitor load time (LCP)
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20262.9 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
210 ms190 msJun 27Jul 25208 ms
Show as table
DateReal-visitor tap response (INP)
Jun 27, 2026194 ms
Jul 4, 2026192 ms
Jul 11, 2026194 ms
Jul 18, 2026195 ms
Jul 25, 2026208 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 kaeltebringer.fr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kaeltebringer.fr at 0.4 s0.4 s
  2. kaeltebringer.fr at 0.8 s0.8 s
  3. kaeltebringer.fr at 1.2 s1.2 s
  4. kaeltebringer.fr at 1.6 s1.6 s
  5. kaeltebringer.fr at 1.9 s1.9 s
  6. kaeltebringer.fr at 2.3 s2.3 s
  7. kaeltebringer.fr at 2.7 s2.7 s
  8. kaeltebringer.fr at 3.1 s3.1 s

Speed

9 to fix58
  • Reduce unused JavaScript

    900 ms · 122 KiB

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

  • Mobile performance score: 58

    58/100

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

  • Use efficient cache lifetimes

    550 ms · 105 KiB

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

  • Render-blocking requests

    450 ms

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

  • Legacy JavaScript

    350 ms · 52 KiB

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

  • admetrics.events adds 291 ms

    291 ms

    admetrics.events costs a phone 291 ms of main-thread work and 84 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.

  • Main-thread work: 2.5 s

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

  • 1,544 HTML elements

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

  • Shopify adds 21 ms

    21 ms

    Shopify costs a phone 21 ms of main-thread work and 306 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (admetrics.events, adcell.com and crypto.com and others), adding 826 KiB and 476 ms of main-thread time.

  • 6 long tasks on the main thread

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

  • Improve image delivery

    167 KiB

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

  • Duplicated JavaScript

    100 ms · 29 KiB

    29 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 100 ms faster on a phone.

  • Font display

    50 ms

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

  • Reduce unused CSS

    23 KiB

    About 23 KiB of CSS is downloaded but never applied on this page.

  • 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: 18 ms

    18 ms

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

Core Web Vitals

6 to fix56
  • Largest Contentful Paint: 12.4 s

    12.4 s

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

  • Time to Interactive: 12.5 s

    12.5 s

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

  • Speed Index: 5.6 s

    5.6 s

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

  • Total Blocking Time: 391 ms

    391 ms

    Scripts block taps and scrolling for 391 ms in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 2.3 s

    2.3 s

    The first text or image appears after 2.3 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) held steady for real visitors

    +4%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix81
  • Page weight: 2.2 MB in 189 requests

    2.2 MB

    Your homepage downloads 2.2 MB in 189 requests on a phone: scripts 811 KiB (54), other files 787 KiB (92) and images 408 KiB (20). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    home-banner.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).

  • About 0.6 g of CO₂ per visit

    0.63 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

9 to fixGoogle 7688
  • 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.

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

  • 1 image without alt text

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

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

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

  • Zoom is disabled

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

  • 5 links without text

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

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • Canonical points to another host

    Your canonical URL points to kaeltebringer.de, not kaeltebringer.fr, so Google may credit that host instead.

  • No social preview image

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

  • 115 internal links, 11 external

    The homepage links to 115 pages on kaeltebringer.fr and 11 external pages.

6 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Kältebringer.de ist Ihr Onlineshop für Marken-Klimaanlagen in Deutschland ❄️ Split Klimaanlagen, Klimageräte & Zubehör …”.

  • One H1 headline

    Your main headline reads: “Split-Klimaanlagen kaufen — direkt vom deutschen Anbieter”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Kältebringer.de | Klimaanlagen & Klimageräte zum besten Preis”.

  • Structured data in place

    Structured data found: OnlineStore and WebSite.

  • 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.kaeltebringer.de/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://kaeltebringer.fr/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.

3 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: 6 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 1 page without a meta description

    https://kaeltebringer.fr/collections/black-month has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

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

  • Titles are unique

    Every page we checked has its own title.

  • 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 4 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 3 broken images

    3 images failed to load on a phone, for example https://kaeltebringer.fr/.

  • 15 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load script”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix69
  • 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.

  • Local business without LocalBusiness data

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

  • No opening hours

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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

5 checks passed
  • 9 short forms

    9 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, 1 customer or partner logo, a star rating and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 13 trackers load before any consent

    13

    Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Google Analytics and Google Tag Manager and 8 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 34 cookies set on arrival

    34

    Opening the homepage sets 34 cookies, 3 of them by other companies (measured from a US location before any click).

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

  • 70 other companies contacted

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

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 kaeltebringer.fr, 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 18 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Sitemap Noindex Pro Seo · Nospy · Adcell Tracking Remarketing · Klaviyo Email Marketing Sms · Triplewhale · Judge Me Reviews · Hulk Form Builder · Gdpr Cookie Consent · Product Ads By Criteo · Localizing · Veeper Stop Coupon Leaks · Back In Stock · hulkapps.com · perfectapps.io · trustpilot.com · archive-digger.com · trustedshops.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
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on kaeltebringer.fr, including 15 speed issues, 2 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