Website review, no card needed

thermomix.com logo

thermomix.com website review

Visit site (opens in a new tab)Reviewed 4 November 202644 issues · 88 checks

This review found 44 issues worth fixing on thermomix.com, 17 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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
2.3 s1.9 sMay 16Oct 311.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20261.9 s
Oct 31, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
114 ms103 msMay 16Oct 31113 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026105 ms
May 23, 2026107 ms
May 30, 2026109 ms
Jun 6, 2026111 ms
Jun 13, 2026112 ms
Jun 20, 2026109 ms
Jun 27, 2026105 ms
Jul 4, 2026104 ms
Jul 11, 2026104 ms
Jul 18, 2026104 ms
Jul 25, 2026104 ms
Aug 1, 2026104 ms
Aug 8, 2026104 ms
Aug 15, 2026106 ms
Aug 22, 2026109 ms
Aug 29, 2026111 ms
Sep 5, 2026110 ms
Sep 12, 2026111 ms
Sep 19, 2026112 ms
Sep 26, 2026112 ms
Oct 3, 2026113 ms
Oct 10, 2026113 ms
Oct 17, 2026113 ms
Oct 24, 2026113 ms
Oct 31, 2026113 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 thermomix.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thermomix.com at 0.6 s0.6 s
  2. thermomix.com at 1.1 s1.1 s
  3. thermomix.com at 1.7 s1.7 s
  4. thermomix.com at 2.2 s2.2 s
  5. thermomix.com at 2.8 s2.8 s
  6. thermomix.com at 3.3 s3.3 s
  7. thermomix.com at 3.9 s3.9 s
  8. thermomix.com at 4.4 s4.4 s

Speed

12 to fix35
  • Reduce unused JavaScript

    5.0 s · 953 KiB

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

  • Use efficient cache lifetimes

    3.0 s · 611 KiB

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

  • Render-blocking requests

    1.1 s

    15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • Mobile performance score: 35

    35/100

    Your mobile performance score is 35. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.0 s

    A phone's processor spends 6.0 s on main-thread work while loading, 3.2 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 (Google Tag Manager, ContentSquare and Yotpo and others), adding 1.6 MB and 1.7 s of main-thread time.

  • Reduce unused CSS

    610 ms · 134 KiB

    About 134 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 610 ms faster on a phone.

  • Improve image delivery

    300 ms · 290 KiB

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

  • Google Tag Manager adds 442 ms

    442 ms

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

  • ContentSquare adds 372 ms

    372 ms

    ContentSquare costs a phone 372 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.

  • Yotpo adds 250 ms

    250 ms

    Yotpo costs a phone 250 ms of main-thread work and 294 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.

  • 2,002 HTML elements

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

  • 20 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 38 KiB

    38 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    100 ms · 73 KiB

    Polyfills for old browsers add 73 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

  • Duplicated JavaScript

    8 KiB

    8 KiB JavaScript is shipped twice across bundles.

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 13 ms

    13 ms

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

Core Web Vitals

9 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: 26.5 s

    26.5 s

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

  • Time to Interactive: 27.2 s

    27.2 s

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

  • Speed Index: 10.3 s

    10.3 s

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

  • Total Blocking Time: 824 ms

    824 ms

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Real-user CLS: 0.13

    0.13

    For real visitors the layout shifts by 0.13 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0.15

    0.15

    The layout shifts by 0.15 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 5 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +7%

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

5 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user INP: 109 ms

    109 ms

    Real visitors wait 109 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 368 ms

    368 ms

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

  • Largest content (LCP) got 13% faster for real visitors

    -13%

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

Images and page weight

3 to fix53
  • Page weight: 8.0 MB in 304 requests

    8.0 MB

    Your homepage downloads 8.0 MB in 304 requests on a phone: media 3.4 MB (2), scripts 2.5 MB (111) and other files 945 KiB (139). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Mobile_Hero_-_November.jpg 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).

  • 1 image far larger than shown

    114 KiB

    1 image is downloaded at several times the size a phone draws it, for example bento-box-interactive.webp at 680 px wide, shown at 138 px. Resized copies would save about 114 KiB.

  • 2 images in older formats

    2 images (263 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.

  • About 2.3 g of CO₂ per visit

    2.27 g

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

Accessibility

6 to fixGoogle 9290
  • 35 text elements with low contrast

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

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 13 images without alt text

    13 images have no alt text, which hurts accessibility and image search.

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

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

4 to fixGoogle 7785
  • Title is long (82 characters)

    Your title is 82 characters, so Google will cut it off around 60: “More than a Food Processor; The Best Multi Cooker | Thermomix® USA – Thermomix USA”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 6 links with vague text

    6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 50 internal links, 27 external

    The homepage links to 50 pages on thermomix.com and 27 external pages.

6 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Experience a new way of cooking with Thermomix! Enjoy simple and healthy recipes made with the most advanced kitchen ap…”.

  • One H1 headline

    Your main headline reads: “Thermomix USA”.

  • Canonical URL set

    The canonical URL is https://www.thermomix.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.thermomix.com/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.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,135 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.thermomix.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix85
  • 2 pages without a meta description

    https://www.thermomix.com/pages/the-cooking-demo and https://www.thermomix.com/pages/locations have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.thermomix.com/products/thermomix%C2%AE-tm7%E2%84%A2, whose canonical is https://www.thermomix.com/products/thermomix%c2%ae-tm7%e2%84%a2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://www.thermomix.com/pages/locations, https://www.thermomix.com/pages/thermomix-loyalty-program and https://www.thermomix.com/pages/financing-options 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 16 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

Best practices

4 to fixGoogle 7383
  • 7 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • 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.

  • About 835 words of copy

    The homepage carries about 835 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book a Demo” and “Order Now”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Book a Cooking Demo”, “Join Us” and “Shop”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo and Microsoft Clarity (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies (measured from a US location before any click).

  • 41 other companies contacted

    Loading the homepage contacts 41 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 thermomix.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 15 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Onetrust Consent Management · Yotpo Product Reviews · Accessibility Spark · Eg Auto Add To Cart · Yotpo Loyalty Rewards · Klaviyo Email Marketing Sms · Pumper Bundles · Minmaxify Order Limits · Essential Pre Order Presale · xecurify.com · googleapis.com · cart-bot.net · magefan.top · rise-ai.com · breadgateway.net

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
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Company

Employees
75
Headquarters
Thousand Oaks

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on thermomix.com, including 21 speed issues, 4 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

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