Website review, no card needed

butlers.com logo

butlers.com website review

Visit site (opens in a new tab)Reviewed 5 November 202627 issues · 79 checks

This review found 27 issues worth fixing on butlers.com, 6 of them high impact, across 79 checks. The most urgent: scrollable region must have keyboard access (3 elements). 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.1 s688 msMay 16Oct 31781 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026730 ms
May 23, 2026750 ms
May 30, 2026776 ms
Jun 6, 2026800 ms
Jun 13, 2026839 ms
Jun 20, 2026867 ms
Jun 27, 2026887 ms
Jul 4, 2026929 ms
Jul 11, 2026898 ms
Jul 18, 2026876 ms
Jul 25, 2026934 ms
Aug 1, 2026985 ms
Aug 8, 2026984 ms
Aug 15, 20261.0 s
Aug 22, 2026952 ms
Aug 29, 2026893 ms
Sep 5, 2026895 ms
Sep 12, 2026850 ms
Sep 19, 2026832 ms
Sep 26, 2026825 ms
Oct 3, 2026816 ms
Oct 10, 2026818 ms
Oct 17, 2026817 ms
Oct 24, 2026787 ms
Oct 31, 2026781 ms
Real-visitor tap response (INP)75th percentile, phones
114 ms95 msMay 16Oct 31111 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202698 ms
May 23, 202699 ms
May 30, 202698 ms
Jun 6, 202697 ms
Jun 13, 202699 ms
Jun 20, 2026101 ms
Jun 27, 2026103 ms
Jul 4, 2026105 ms
Jul 11, 2026106 ms
Jul 18, 2026106 ms
Jul 25, 2026109 ms
Aug 1, 2026110 ms
Aug 8, 2026110 ms
Aug 15, 2026109 ms
Aug 22, 2026107 ms
Aug 29, 2026105 ms
Sep 5, 2026105 ms
Sep 12, 2026106 ms
Sep 19, 2026110 ms
Sep 26, 2026111 ms
Oct 3, 2026112 ms
Oct 10, 2026112 ms
Oct 17, 2026112 ms
Oct 24, 2026111 ms
Oct 31, 2026111 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 butlers.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. butlers.com at 0.8 s0.8 s
  2. butlers.com at 1.6 s1.6 s
  3. butlers.com at 2.5 s2.5 s
  4. butlers.com at 3.3 s3.3 s
  5. butlers.com at 4.1 s4.1 s
  6. butlers.com at 4.9 s4.9 s
  7. butlers.com at 5.7 s5.7 s
  8. butlers.com at 6.5 s6.5 s

Speed

6 to fix80
  • Mobile performance score: 80

    80/100

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

  • Render-blocking requests

    950 ms

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

  • Improve image delivery

    350 ms · 281 KiB

    9 images could be 281 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • baqend.com adds 337 ms

    337 ms

    baqend.com costs a phone 337 ms of main-thread work and 112 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: 3.0 s

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

  • 2,854 HTML elements

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (baqend.com, Shopify and shop.app and others), adding 309 KiB and 439 ms of main-thread time.

  • 5 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 14 KiB

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

  • Reduce unused JavaScript

    98 KiB

    About 98 KiB of JavaScript is downloaded but never used on this page.

  • Use efficient cache lifetimes

    9 KiB

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

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

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 4.1 s

    4.1 s

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

  • Time to Interactive: 6.4 s

    6.4 s

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

  • Speed Index: 4.2 s

    4.2 s

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

  • Total Blocking Time: 235 ms

    235 ms

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

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

    +13%

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.2 s

    1.2 s

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

  • Real-user INP: 110 ms

    110 ms

    Real visitors wait 110 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: 0.9 s

    0.9 s

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

  • Real-user TTFB: 470 ms

    470 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.5 MB in 227 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 227 requests on a phone: images 945 KiB (53), other files 814 KiB (100) and scripts 483 KiB (49). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.70 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 8893
  • Scrollable region must have keyboard access (3 elements)

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

  • Elements must only use permitted ARIA attributes (2 elements)

    Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

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

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

  • 25 links without text

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

  • 16 text elements with low contrast

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

  • Headings skip levels

    Headings skip levels (h2 → h4), 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 74 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

3 to fixGoogle 9289
  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//www.butlers.com/cdn/shop/files/Boogie-01.jpg?v=1761837550…”.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • One H1 headline

    Your <h1> is empty.

  • 324 internal links, 11 external

    The homepage links to 324 pages on butlers.com and 11 external pages.

6 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “Entdecke unsere modernen Wohnaccessoires & alles für den gedeckten Tisch. 🏠 Deko, Möbel, Geschirr & mehr – jetzt beque…”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “BUTLERS Online Shop | Stilvolle Deko & Wohnaccessoires ✨”.

  • Canonical URL set

    The canonical URL is https://www.butlers.com/.

  • 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.butlers.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.butlers.com/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.

  • Organization data: 5 of 6 facts

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

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 3 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 3 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 16 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'controller')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix43
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

2 checks passed
  • 6 short forms

    6 short forms (3 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and TikTok Pixel.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Klaviyo (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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 7 other companies contacted

    Loading the homepage contacts 7 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 butlers.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 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Speed Kit · Klaviyo Email Marketing Sms · Gdpr Cookie Consent

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
Tailwind CSS
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

Company

Employees
240
Founded
1999
Headquarters
Cologne

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on butlers.com, including 10 speed issues, 3 SEO 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