Website review, no card needed
bartmannberlin.de website review
Visit site (opens in a new tab)Reviewed 17 November 202640 issues · 87 checks
This review found 40 issues worth fixing on bartmannberlin.de, 12 of them high impact, across 87 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
70C- #96,180 of 114,775 reviewed websitesbeats 14%
- #59,651 of 66,300 online storesbeats 8%
- #55,453 of 60,657 Shopify storesbeats 7%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.8 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 3.1 s |
| Oct 31, 2026 | 2.9 s |
| Nov 7, 2026 | 2.9 s |
| Nov 14, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 143 ms |
| Jun 6, 2026 | 150 ms |
| Jun 13, 2026 | 144 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 151 ms |
| Jul 4, 2026 | 153 ms |
| Jul 11, 2026 | 177 ms |
| Jul 18, 2026 | 169 ms |
| Jul 25, 2026 | 175 ms |
| Aug 1, 2026 | 180 ms |
| Aug 8, 2026 | 184 ms |
| Aug 15, 2026 | 185 ms |
| Aug 22, 2026 | 184 ms |
| Aug 29, 2026 | 179 ms |
| Sep 5, 2026 | 174 ms |
| Sep 19, 2026 | 195 ms |
| Sep 26, 2026 | 213 ms |
| Oct 3, 2026 | 221 ms |
| Oct 10, 2026 | 221 ms |
| Oct 17, 2026 | 206 ms |
| Oct 24, 2026 | 213 ms |
| Oct 31, 2026 | 208 ms |
| Nov 7, 2026 | 211 ms |
| Nov 14, 2026 | 211 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.2 s
2.7 s
3.3 s
3.8 s
4.4 s
Speed
Reduce unused JavaScript
2.4 s · 600 KiBAbout 600 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Render-blocking requests
1.3 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 47
47/100Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.8 s
A phone's processor spends 5.8 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (hsappstatic.net, Facebook and Shopify and others), adding 1.5 MB and 1.6 s of main-thread time.
Use efficient cache lifetimes
200 ms · 381 KiB16 files are served with short cache lifetimes, so returning visitors download them again (381 KiB).
Reduce unused CSS
330 ms · 64 KiBAbout 64 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 330 ms faster on a phone.
Shopify adds 307 ms
307 msShopify costs a phone 307 ms of main-thread work and 782 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.
hsappstatic.net adds 358 ms
358 mshsappstatic.net costs a phone 358 ms of main-thread work and 125 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.
Facebook adds 345 ms
345 msFacebook costs a phone 345 ms of main-thread work and 224 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.
Hubspot adds 289 ms
289 msHubspot costs a phone 289 ms of main-thread work and 210 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 301 ms. During a long task the page ignores taps.
Google Tag Manager adds 255 ms
255 msGoogle Tag Manager costs a phone 255 ms of main-thread work and 162 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,911 HTML elements
The page has 1,911 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
53 KiB3 images could be 53 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
34 KiBPolyfills for old browsers add 34 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.
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: 15 ms
15 msYour server sent the HTML in 15 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.
Largest Contentful Paint: 11.8 s
11.8 sYour largest element takes 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Möbelmanufaktur BARTMANN. - Küche in grünem Linoleum und ge…”.
Time to Interactive: 17.5 s
17.5 sThe page becomes fully interactive after 17.5 s. Good is under 3.8 s.
Total Blocking Time: 990 ms
990 msScripts block taps and scrolling for 990 ms in total while the page loads. Good is under 200 ms.
Speed Index: 6.6 s
6.6 sVisually, the page fills in at 6.6 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 211 ms
211 msReal visitors wait 211 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 44% slower for real visitors
+44%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 143 ms to 211 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 477 ms
477 msReal visitors wait 477 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 3.4 MB in 240 requests
3.4 MBYour homepage downloads 3.4 MB in 240 requests on a phone: scripts 1.4 MB (77), other files 969 KiB (105) and images 728 KiB (26). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
kueche-linoleum-4175-eiche-edelstahl-bartmann-berlin-37_1_38 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).
6 images in older formats
6 images (245 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.
1 image below the first screen load straight away
1 image further down the page (50 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
0.96 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.96 g of CO₂e: 115.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
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 32 images in the HTML carry an alt attribute.
30 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 31 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“.logo_image { max-height: unset!important; width:…” and “.logo_image { max-height: unset!important; width:…”). One clear main headline is easier for people and search engines.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
140 internal links, 9 external
The homepage links to 140 pages on bartmannberlin.de and 9 external pages.
7 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Möbelmanufaktur aus Berlin: Betten und Tische aus eigener Kollektion, Küchen, Einbauschränke und Innenausbau nach Maß –…”.
Title: 60 characters
Your title is a healthy 60 characters: “BARTMANN – Möbelmanufaktur Berlin | Kollektion und Maßarbeit”.
Canonical URL set
The canonical URL is https://bartmannberlin.de/.
Structured data in place
Structured data found: ImageGallery and Organization.
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://bartmannberlin.de/sitemap.xml.
AI search readiness
No llms.txt
There is no https://bartmannberlin.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.
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,555 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://bartmannberlin.de/collections/all is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://bartmannberlin.de/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://bartmannberlin.de/collections/all has 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 52 found) and read each the way a search engine does.
4 checks passed
Linked pages load
1 page 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 a title
All 1 page that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://bartmannberlin.de/.
11 small tap targets
11 of 29 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 130 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 935 words of copy
The homepage carries about 935 words of visible text.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “Zurück zum Shop”.
3 short forms
3 short forms (0 fields at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 2 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
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 2 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.
27 cookies set on arrival
27Opening the homepage sets 27 cookies, 6 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.
39 other companies contacted
Loading the homepage contacts 39 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 bartmannberlin.de, 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
Consentmo Gdpr · Gg Product Gallery · Xo Gallery · Judge Me Reviews · Ymq Product Options · Forms · Gdpr Backpack · luckyorange.com · amazonaws.com · hubapi.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
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on bartmannberlin.de, including 22 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.