Website review, no card needed
mukitchen.com website review
Visit site (opens in a new tab)Reviewed 9 November 202626 issues · 77 checks
This review found 26 issues worth fixing on mukitchen.com, 9 of them high impact, across 77 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
88B- #4,773 of 97,165 reviewed websitesbeats 93%
- #2,536 of 52,810 online storesbeats 93%
- #2,459 of 47,864 Shopify storesbeats 92%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.0 s |
| Jun 6, 2026 | 1.0 s |
| Jun 13, 2026 | 981 ms |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 976 ms |
| Jul 4, 2026 | 989 ms |
| Jul 11, 2026 | 1.0 s |
| Jul 18, 2026 | 981 ms |
| Jul 25, 2026 | 984 ms |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 964 ms |
| Aug 15, 2026 | 939 ms |
| Aug 22, 2026 | 960 ms |
| Aug 29, 2026 | 849 ms |
| Sep 5, 2026 | 868 ms |
| Sep 12, 2026 | 887 ms |
| Sep 19, 2026 | 895 ms |
| Sep 26, 2026 | 956 ms |
| Oct 3, 2026 | 964 ms |
| Oct 10, 2026 | 974 ms |
| Oct 17, 2026 | 963 ms |
| Oct 24, 2026 | 931 ms |
| Oct 31, 2026 | 912 ms |
| Nov 7, 2026 | 909 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 97 ms |
| May 30, 2026 | 103 ms |
| Jun 6, 2026 | 104 ms |
| Jun 13, 2026 | 108 ms |
| Jun 20, 2026 | 111 ms |
| Jun 27, 2026 | 111 ms |
| Jul 4, 2026 | 111 ms |
| Jul 11, 2026 | 116 ms |
| Jul 18, 2026 | 106 ms |
| Jul 25, 2026 | 108 ms |
| Aug 1, 2026 | 119 ms |
| Aug 8, 2026 | 113 ms |
| Aug 15, 2026 | 119 ms |
| Aug 22, 2026 | 121 ms |
| Aug 29, 2026 | 131 ms |
| Sep 5, 2026 | 123 ms |
| Sep 12, 2026 | 121 ms |
| Sep 19, 2026 | 117 ms |
| Sep 26, 2026 | 106 ms |
| Oct 3, 2026 | 105 ms |
| Oct 10, 2026 | 101 ms |
| Oct 17, 2026 | 112 ms |
| Oct 24, 2026 | 104 ms |
| Oct 31, 2026 | 96 ms |
| Nov 7, 2026 | 109 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
1.2 s · 244 KiBAbout 244 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
282 KiB8 images could be 282 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Shopify adds 99 ms
99 msShopify costs a phone 99 ms of main-thread work and 570 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.
3 third-party services on the page
3 third-party services load with your homepage (Shopify, shop.app and myshopify.com), adding 595 KiB and 99 ms of main-thread time.
Use efficient cache lifetimes
5 KiB3 files are served with short cache lifetimes, so returning visitors download them again (5 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.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 378 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 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: 7.2 s
7.2 sYour largest element takes 7.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Real-user TTFB: 912 ms
912 msReal visitors wait 912 ms for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 7.3 s
7.3 sThe page becomes fully interactive after 7.3 s. Good is under 3.8 s.
Speed Index: 3.9 s
3.9 sVisually, the page fills in at 3.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 97 ms to 109 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 156 ms
156 msReal visitors wait 156 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.1 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.4 MB in 232 requests
2.4 MBYour homepage downloads 2.4 MB in 232 requests on a phone: other files 791 KiB (97), images 761 KiB (21) and scripts 700 KiB (82). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (95 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.
3 images below the first screen load straight away
3 images further down the page (77 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.67 g of CO₂e: 80.2 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
39 text elements with low contrast
39 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
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.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (6 elements)
Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 22 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
One H1 headline
Your <h1> is empty.
86 internal links, 5 external
The homepage links to 86 pages on mukitchen.com and 5 external pages.
7 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Shop MUkitchen for premium kitchen textiles where function meets style. Shop oven mitts, towels, aprons & more designed…”.
Title: 38 characters
Your title is a healthy 38 characters: “MUkitchen | Where Function Meets Style”.
Canonical URL set
The canonical URL is https://www.mukitchen.com/.
Structured data in place
Structured data found: Organization and WebSite.
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.mukitchen.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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (638 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.mukitchen.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.mukitchen.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.mukitchen.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
12 pages without a meta description
https://www.mukitchen.com/collections/all, https://www.mukitchen.com/customer_authentication/redirect, https://www.mukitchen.com/policies/shipping-policy, https://www.mukitchen.com/collections/vibe, https://www.mukitchen.com/pages/towels-dishcloths and https://www.mukitchen.com/collections/aprons and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
11 pages without an H1
https://www.mukitchen.com/collections/all, https://www.mukitchen.com/customer_authentication/redirect, https://www.mukitchen.com/collections/vibe, https://www.mukitchen.com/pages/towels-dishcloths, https://www.mukitchen.com/collections/aprons and https://www.mukitchen.com/collections/potholders and 5 others 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 35 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.
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.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
24 of 24 tappable elements near the top are at least 24 px.
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 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 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.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 428 words of copy
The homepage carries about 428 words of visible text.
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact” and “Contact information”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
17 other companies contacted
Loading the homepage contacts 17 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 mukitchen.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
Sami Wholesale · Linkedoption · Forms · Moast
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 26 issues on mukitchen.com, including 10 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.