Website review, no card needed

braun-bueffel.com logo

braun-bueffel.com website review

Visit site (opens in a new tab)Reviewed 23 October 202630 issues · 77 checks

This review found 30 issues worth fixing on braun-bueffel.com, 11 of them high impact, across 77 checks. The most urgent: improve image delivery. 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.3 sMay 2Oct 171.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.4 s
May 9, 20261.4 s
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.5 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.7 s
Aug 8, 20261.7 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
138 ms102 msMay 2Oct 17134 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026106 ms
May 9, 2026110 ms
May 16, 2026112 ms
May 23, 2026116 ms
May 30, 2026120 ms
Jun 6, 2026123 ms
Jun 13, 2026125 ms
Jun 20, 2026128 ms
Jun 27, 2026130 ms
Jul 4, 2026132 ms
Jul 11, 2026131 ms
Jul 18, 2026128 ms
Jul 25, 2026121 ms
Aug 1, 2026123 ms
Aug 8, 2026122 ms
Aug 15, 2026121 ms
Aug 22, 2026121 ms
Aug 29, 2026115 ms
Sep 5, 2026112 ms
Sep 12, 2026113 ms
Sep 19, 2026114 ms
Sep 26, 2026119 ms
Oct 3, 2026124 ms
Oct 10, 2026128 ms
Oct 17, 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

Full-page screenshot of braun-bueffel.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. braun-bueffel.com at 0.4 s0.4 s
  2. braun-bueffel.com at 0.8 s0.8 s
  3. braun-bueffel.com at 1.2 s1.2 s
  4. braun-bueffel.com at 1.6 s1.6 s
  5. braun-bueffel.com at 2.0 s2.0 s
  6. braun-bueffel.com at 2.4 s2.4 s
  7. braun-bueffel.com at 2.8 s2.8 s
  8. braun-bueffel.com at 3.2 s3.2 s

Speed

11 to fix57
  • Improve image delivery

    3.8 s · 2.4 MB

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

  • Reduce unused JavaScript

    1.2 s · 460 KiB

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

  • 3,412 HTML elements

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

  • Use efficient cache lifetimes

    950 ms · 219 KiB

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

  • Mobile performance score: 57

    57/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Google Tag Manager and Clarity and others), adding 2.9 MB and 702 ms of main-thread time.

  • Render-blocking requests

    950 ms

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

  • Main-thread work: 3.8 s

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

  • Klaviyo adds 223 ms

    223 ms

    Klaviyo costs a phone 223 ms of main-thread work and 661 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.

  • Google Tag Manager adds 164 ms

    164 ms

    Google Tag Manager costs a phone 164 ms of main-thread work and 325 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.

  • Shopify adds 49 ms

    49 ms

    Shopify costs a phone 49 ms of main-thread work and 1.4 MB 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.

  • Minify JavaScript

    150 ms · 49 KiB

    49 KiB could be saved by minifying JavaScript.

  • 10 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    18 KiB

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

1 checks passed
  • Server response: 65 ms

    65 ms

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

Core Web Vitals

7 to fix67
  • 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: 21.0 s

    21.0 s

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

  • Time to Interactive: 28.7 s

    28.7 s

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

  • Speed Index: 9.0 s

    9.0 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

    The first text or image appears after 3.1 s on a phone. Good is under 1.8 s.

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Tap response (INP) got 21% slower for real visitors

    +21%

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

  • Largest content (LCP) got 17% slower for real visitors

    +17%

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

6 checks passed
  • Real-user INP: 138 ms

    138 ms

    Real visitors wait 138 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.5 s

    1.5 s

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

  • Real-user TTFB: 659 ms

    659 ms

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

  • Cumulative Layout Shift: 0.089

    0.089

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

  • Total Blocking Time: 173 ms

    173 ms

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

Images and page weight

1 to fix33
  • Page weight: 6.0 MB in 264 requests

    6.0 MB

    Your homepage downloads 6.0 MB in 264 requests on a phone: images 3.4 MB (27), scripts 1.7 MB (111) and other files 575 KiB (82). Under 2 MB keeps phones on slow connections fast.

  • About 1.7 g of CO₂ per visit

    1.70 g

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

Accessibility

4 to fixGoogle 7781
  • Documents must have <title> element to aid in navigation (1 element)

    Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 48 images in the HTML carry an alt attribute.

  • 8 automated accessibility rules passed

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

SEO

Google 82100
  • 174 internal links, 7 external

    The homepage links to 174 pages on braun-bueffel.com and 7 external pages.

8 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Entdecken Sie exklusive Lederwaren im BRAUN BÜFFEL Shop: Geldbörsen, Etuis, Taschen & Accessoires. Jetzt shoppen und ze…”.

  • One H1 headline

    Your main headline reads: “Braun Büffel”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “BRAUN BÜFFEL - Handgefertigte Lederwaren seit 1887”.

  • Canonical URL set

    The canonical URL is https://braun-bueffel.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Store 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://braun-bueffel.com/sitemap.xml.

AI search readiness

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

  • llms.txt published

    The site publishes https://braun-bueffel.com/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 93 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

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

Best practices

1 to fixGoogle 9692
  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://braun-bueffel.com/cdn/shop/t/53/assets/badges.css?v=35702' because its MIME type (…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix67
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • Only about 86 words

    The homepage has only about 86 words of visible text; thin pages give Google and first-time buyers little to go on.

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

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Zum Schweizer Shop”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 4 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.

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies (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.

  • 57 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity

Company

Founded
1887
Headquarters
Kirn

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on braun-bueffel.com, including 18 speed issues and 5 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