Website review, no card needed
bandwerk.com website review
Visit site (opens in a new tab)Reviewed 7 November 202633 issues · 82 checks
This review found 33 issues worth fixing on bandwerk.com, 8 of them high impact, across 82 checks. The most urgent: main-thread work: 4.5 s. 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
84B- #21,761 of 121,612 reviewed websitesbeats 77%
- #14,098 of 68,795 online storesbeats 73%
- #13,678 of 62,685 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Main-thread work: 4.5 s
A phone's processor spends 4.5 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 77
77/100Your mobile performance score is 77. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
536 KiB6 images could be 536 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
1,983 HTML elements
The page has 1,983 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (weglot.com, Shopify and cloudfront.net and others), adding 525 KiB and 190 ms of main-thread time.
Reduce unused JavaScript
150 ms · 54 KiBAbout 54 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
200 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.
Reduce unused CSS
150 ms · 26 KiBAbout 26 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.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 129 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
89 KiB7 files are served with short cache lifetimes, so returning visitors download them again (89 KiB).
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
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: 55 ms
55 msYour server sent the HTML in 55 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 6.6 s
6.6 sThe page becomes fully interactive after 6.6 s. Good is under 3.8 s.
Largest Contentful Paint: 3.6 s
3.6 sYour largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Cumulative Layout Shift: 0.143
0.143The layout shifts by 0.143 while loading, so content jumps under the reader's thumb. Good is under 0.1.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
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
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.
Total Blocking Time: 40 ms
40 msScripts block the page for only 40 ms while loading. Good is under 200 ms.
Images and page weight
1 image over 500 KB
Sonderedition_Pepita_Apple_Watch_Armband_2_1.webp weighs 1.4 MB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
1.3 MB1 image is downloaded at several times the size a phone draws it, for example Sonderedition_Pepita_Apple_Watch_Armband_2_1.webp at 3,982 px wide, shown at 357 px. Resized copies would save about 1.3 MB.
Page weight: 3.0 MB in 308 requests
3.0 MBYour homepage downloads 3.0 MB in 308 requests on a phone: other files 1.3 MB (237), images 977 KiB (16) and scripts 487 KiB (42). Under 2 MB keeps phones on slow connections fast.
5 images in older formats
5 images (1.7 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.
An image on the first screen is lazy-loaded
Sonderedition_Pepita_Apple_Watch_Armband_2_1.webp 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.9 g of CO₂ per visit
0.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.85 g of CO₂e: 102.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5), 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).
2 checks passed
Every image has alt text
All 51 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “Edles Apple Zubehör » Apple Watch Armbänder, iPhone 17 Hüllen & mehr”.
Meta description is long (172 characters)
Your meta description is 172 characters; Google truncates after about 160, so the end of your pitch is cut.
76 internal links, 17 external
The homepage links to 76 pages on bandwerk.com and 17 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Aus dem Rennanzug von Michael Schumacher”.
Canonical URL set
The canonical URL is https://bandwerk.com/.
Structured data in place
Structured data found: LocalBusiness.
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://bandwerk.com/sitemap.xml.
AI search readiness
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, sameAs (social profiles), description and contact details; logo would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (816 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://bandwerk.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://bandwerk.com/products/magbase-max declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
4 pages share 2 titles
/ and https://bandwerk.com/products/magbase-max all use the title “Edles Apple Zubehör » Apple Watch Armbänder, iPhone 17 Hüllen & mehr”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://bandwerk.com/pages/outlet has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://bandwerk.com/collections/alle-apple-watch-armbaender and https://bandwerk.com/collections/apple-watch-armbaender use the same meta description. A description written for each page earns more clicks.
10 pages without an H1
https://bandwerk.com/collections/alle-apple-watch-armbaender, https://bandwerk.com/collections/apple-watch-bander-leather, https://bandwerk.com/collections/metall-armbaender, https://bandwerk.com/collections/sportarmbaender-fuer-die-apple-watch, https://bandwerk.com/collections/iphone-huellen and https://bandwerk.com/collections/iphone-17-hullen and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://bandwerk.com/collections/apple-watch-bander-leather took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 39 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
8 small tap targets
8 of 25 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.
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.
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.
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 671 words of copy
The homepage carries about 671 words of visible text.
6 checks passed
1 call to action
The homepage has 1 call to action, for example “Shop Now”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
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
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo and Pinterest Tag (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
20 other companies contacted
Loading the homepage contacts 20 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 bandwerk.com, 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
Pandectes Gdpr · Sc Easy Redirects · Weglot Translate Your Store · Klaviyo Email Marketing Sms · Microsoft Clarity · Gdpr Cookie Consent · Konfigurator · luckyorange.com · freshify.click · useamp.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
- CMS
- Webflow
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | 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 33 issues on bandwerk.com, including 9 speed issues, 2 SEO issues and 2 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.