Website review, no card needed

baumberge-atelier.de logo

baumberge-atelier.de website review

Visit site (opens in a new tab)Reviewed 20 November 202638 issues · 77 checks

This review found 38 issues worth fixing on baumberge-atelier.de, 12 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

Full-page screenshot of baumberge-atelier.de (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix69
  • Improve image delivery

    13.3 s · 37.9 MB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (jimstatic.com, jimcdn.com and jimdo.com), adding 68.1 MB and 236 ms of main-thread time.

  • jimcdn.com adds 1 ms

    1 ms

    jimcdn.com costs a phone 1 ms of main-thread work and 67.7 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.

  • Mobile performance score: 69

    69/100

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

  • Reduce unused JavaScript

    750 ms · 126 KiB

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

  • Render-blocking requests

    700 ms

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

  • Reduce unused CSS

    300 ms · 35 KiB

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

  • jimstatic.com adds 235 ms

    235 ms

    jimstatic.com costs a phone 235 ms of main-thread work and 373 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.

  • 1,906 HTML elements

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

  • Font display

    250 ms

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 161 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Use efficient cache lifetimes

    1 KiB

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

2 checks passed
  • Main-thread work: 1.0 s

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

  • Server response: 113 ms

    113 ms

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

Core Web Vitals

5 to fix66
  • Largest Contentful Paint: 185.2 s

    185.2 s

    Your largest element takes 185.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BAUMBERGE-ATELIER EINZIGARTIG - HANDGEFERTIGT”.

  • Time to Interactive: 201.9 s

    201.9 s

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

  • 158 images without width and height

    158 images have no width and height attributes, so the layout jumps as each one loads.

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Speed Index: 3.9 s

    3.9 s

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

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

2 checks passed
  • Total Blocking Time: 111 ms

    111 ms

    Scripts block the page for only 111 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

5 to fix18
  • Page weight: 68.1 MB in 253 requests

    68.1 MB

    Your homepage downloads 68.1 MB in 253 requests on a phone: images 67.7 MB (233), scripts 234 KiB (6) and fonts 93 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 40 images over 500 KB

    40 images weigh 38.4 MB together. On a phone connection a single image that size takes seconds.

  • 40 images far larger than shown

    28.3 MB

    40 images are downloaded at several times the size a phone draws them, for example image.jpg at 2,020 px wide, shown at 286 px. Resized copies would save about 28.3 MB.

  • 40 images in older formats

    40 images (38.4 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.

  • 40 images below the first screen load straight away

    40 images further down the page (38.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 19.3 g of CO₂ per visit

    19.31 g

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

Accessibility

6 to fixGoogle 8390
  • 8 buttons without a name

    8 buttons have no accessible name, so screen readers announce just “button”.

  • 42 text elements with low contrast

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 313 links without text

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

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

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

  • Alternative text of images should not be repeated as text (3 elements)

    Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 230 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

4 to fixGoogle 9282
  • Title is long (79 characters)

    Your title is 79 characters, so Google will cut it off around 60: “Baumberge-Atelier unikate Näh- Schmuck und Deko-Arbeiten - baumberge-atelier.de”.

  • 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 short (54 characters)

    Your meta description is only 54 characters: “Unique handmade by JHB Näharbeiten, Schmuck, Deko uvm.”. 70 to 160 characters is enough to sell the click.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 227 internal links, 7 external

    The homepage links to 227 pages on baumberge-atelier.de and 7 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Kissen, zum Kuscheln, zum Lesen etc....”.

  • Canonical URL set

    The canonical URL is https://www.baumberge-atelier.de/.

  • 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://www.baumberge-atelier.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.baumberge-atelier.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 (517 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix65
  • 2 linked pages are broken

    Your homepage links to https://www.baumberge-atelier.de/%C3%BCber-mich/miniaturh%C3%A4user-1-24/carribean-beach and https://www.baumberge-atelier.de/%C3%BCber-mich/miniaturh%C3%A4user-1-24/english-tea-rose-garden, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 12 pages without a meta description

    https://www.baumberge-atelier.de/%C3%BCber-mich/stickbilder-katzen, https://www.baumberge-atelier.de/%C3%BCber-mich/stickbilder-verschiendene, https://www.baumberge-atelier.de/%C3%BCber-mich/miniaturh%C3%A4user-1-24, https://www.baumberge-atelier.de/%C3%BCber-mich/miniaturh%C3%A4user-1-24/mein-atelier, https://www.baumberge-atelier.de/%C3%BCber-mich/miniaturh%C3%A4user-1-24/feen-zimmer and https://www.baumberge-atelier.de/%C3%BCber-mich/miniaturh%C3%A4user-1-24/chocolatier and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages without an H1

    https://www.baumberge-atelier.de/%C3%BCber-mich/stickbilder-verschiendene, https://www.baumberge-atelier.de/%C3%BCber-mich/miniaturh%C3%A4user-1-24, https://www.baumberge-atelier.de/%C3%BCber-mich/miniaturh%C3%A4user-1-24/mein-atelier, https://www.baumberge-atelier.de/%C3%BCber-mich/miniaturh%C3%A4user-1-24/feen-zimmer, https://www.baumberge-atelier.de/%C3%BCber-mich/miniaturh%C3%A4user-1-24/chocolatier and https://www.baumberge-atelier.de/%C3%BCber-mich/miniaturh%C3%A4user-1-24/birthday-party-room and 5 others have 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 84 found) and read each the way a search engine does.

4 checks passed
  • 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 7797
  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    14 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. 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.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 484 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Umami.

Privacy and tracking

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies, 2 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.

  • 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
  • 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 baumberge-atelier.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
Jimdo Creator
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on baumberge-atelier.de, including 14 speed issues, 4 SEO issues and 4 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