Website review, no card needed

kitchesnaid.us logo

kitchesnaid.us website review

Visit site (opens in a new tab)Reviewed 10 November 202642 issues · 88 checks

This review found 42 issues worth fixing on kitchesnaid.us, 13 of them high impact, across 88 checks. The most urgent: unlabelled dropdowns. 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 kitchesnaid.us (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix69
  • 3,739 HTML elements

    The page has 3,739 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 (Google Tag Manager, VWO and kitchenaid.com.au and others), adding 1.5 MB and 1.2 s of main-thread time.

  • Mobile performance score: 69

    69/100

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

  • Render-blocking requests

    850 ms

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

  • Reduce unused JavaScript

    150 ms · 641 KiB

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

  • Use efficient cache lifetimes

    150 ms · 602 KiB

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

  • Main-thread work: 3.5 s

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

  • Google Tag Manager adds 303 ms

    303 ms

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

  • VWO adds 268 ms

    268 ms

    VWO costs a phone 268 ms of main-thread work and 170 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.

  • 51.la adds 101 ms

    101 ms

    51.la costs a phone 101 ms of main-thread work and 357 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.

  • 8 long tasks on the main thread

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

  • Improve image delivery

    38 KiB

    2 images could be 38 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    27 KiB

    Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    11 KiB

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

1 checks passed
  • Server response: 136 ms

    136 ms

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

Core Web Vitals

6 to fix70
  • Time to Interactive: 21.8 s

    21.8 s

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

  • Largest Contentful Paint: 4.2 s

    4.2 s

    Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Purchasing on KitchenAid.com.au Price Match Chat now Free D…”. Most of its time is element render delay (1.9 s).

  • Speed Index: 5.9 s

    5.9 s

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

  • 52 images without width and height

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

  • Total Blocking Time: 412 ms

    412 ms

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

  • First Contentful Paint: 1.8 s

    1.8 s

    The first text or image appears after 1.8 s on a phone. Good is under 1.8 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.

1 checks passed
  • Cumulative Layout Shift: 0.049

    0.049

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

Images and page weight

1 to fix85
  • Page weight: 3.2 MB in 221 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 221 requests on a phone: scripts 2.2 MB (115), HTML 432 KiB (12) and images 307 KiB (32). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (58 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.92 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

10 to fixGoogle 6585
  • Unlabelled dropdowns

    11 dropdowns have no label.

  • Invalid ARIA attributes

    10 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • 2 buttons without a name

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

  • 98 tap targets too small

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

  • 30 text elements with low contrast

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

  • 6 images without alt text

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

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 34 form fields without a label

    34 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 12 links without text

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

1 checks passed
  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 9 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 3864
  • Page is set to noindex

    The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • 26 links with vague text

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 458 internal links, 8 external

    The homepage links to 458 pages on kitchesnaid.us and 8 external pages.

7 checks passed
  • Meta description: 127 characters

    Your meta description is 127 characters: “Shop KitchenAid Australia for premium kitchen appliances, including stand mixers, blenders, food processors, kettles, a…”.

  • One H1 headline

    Your main headline reads: “Shopping with KitchenAid Australia”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “KitchenAid | Countertop Kitchen Appliances”.

  • Canonical URL set

    The canonical URL is https://www.kitchesnaid.us/.

  • Structured data in place

    Structured data found: Corporation and OnlineStore.

  • 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.kitchesnaid.us/sitemap.xml.

AI search readiness

100
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, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

4 to fix81
  • 13 linked pages hidden from search

    https://www.kitchesnaid.us/blogs/kitchenthusiast, https://www.kitchesnaid.us/pages/contact-us, https://www.kitchesnaid.us/apps/iwish, https://www.kitchesnaid.us/pages/new-in, https://www.kitchesnaid.us/collections/stand-mixers and https://www.kitchesnaid.us/collections/espresso-coffee-machines and 7 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 4 pages without a meta description

    https://www.kitchesnaid.us/apps/iwish, https://www.kitchesnaid.us/pages/new-in, https://www.kitchesnaid.us/collections/small-appliances and https://www.kitchesnaid.us/collections/utensils have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.kitchesnaid.us/collections/stand-mixers and https://www.kitchesnaid.us/collections/stand-mixers/type-tilt-head use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://www.kitchesnaid.us/blogs/kitchenthusiast has no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages slow to respond

    https://www.kitchesnaid.us/pages/new-in, https://www.kitchesnaid.us/collections/espresso-coffee-machines, https://www.kitchesnaid.us/collections/cordless, https://www.kitchesnaid.us/collections/utensils, https://www.kitchesnaid.us/collections/toys and https://www.kitchesnaid.us/collections/bundles and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7385
  • 36 small tap targets

    36 of 55 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.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 5 low-resolution images

    5 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • No social proof

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • 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 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 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 1,504 words of copy

    The homepage carries about 1,504 words of visible text.

  • Urgency cues

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more”.

  • 82 calls to action

    The homepage has 82 calls to action, for example “Shop All Stand Mixers →”, “Shop All Attachments and Accessories →” and “Shop All Coffee Machines →”.

  • 37 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Privacy and tracking

  • 23 cookies set on arrival

    23

    Opening the homepage sets 23 cookies, 1 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.

  • 16 other companies contacted

    Loading the homepage contacts 16 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 kitchesnaid.us, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

No apps were seen in the code your storefront loads.

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
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on kitchesnaid.us, including 16 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