Website review, no card needed

kutchina.com logo

kutchina.com website review

Visit site (opens in a new tab)Reviewed 1 November 202655 issues · 87 checks

This review found 55 issues worth fixing on kutchina.com, 22 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. 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
3.7 s1.8 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.2 s
May 16, 20262.1 s
May 23, 20262.2 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.3 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.1 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.8 s
Sep 19, 20263.4 s
Sep 26, 20263.5 s
Oct 3, 20263.4 s
Oct 10, 20262.9 s
Oct 17, 20262.4 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
222 ms126 msMay 9Oct 24184 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026137 ms
May 16, 2026141 ms
May 23, 2026142 ms
May 30, 2026143 ms
Jun 6, 2026144 ms
Jun 13, 2026145 ms
Jun 20, 2026153 ms
Jun 27, 2026160 ms
Jul 4, 2026163 ms
Jul 11, 2026164 ms
Jul 18, 2026164 ms
Jul 25, 2026161 ms
Aug 1, 2026160 ms
Aug 8, 2026161 ms
Aug 15, 2026165 ms
Aug 22, 2026167 ms
Aug 29, 2026167 ms
Sep 5, 2026167 ms
Sep 12, 2026185 ms
Sep 19, 2026207 ms
Sep 26, 2026210 ms
Oct 3, 2026211 ms
Oct 10, 2026195 ms
Oct 17, 2026183 ms
Oct 24, 2026184 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 kutchina.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kutchina.com at 1.0 s1.0 s
  2. kutchina.com at 1.9 s1.9 s
  3. kutchina.com at 2.9 s2.9 s
  4. kutchina.com at 3.8 s3.8 s
  5. kutchina.com at 4.8 s4.8 s
  6. kutchina.com at 5.8 s5.8 s
  7. kutchina.com at 6.7 s6.7 s
  8. kutchina.com at 7.7 s7.7 s

Speed

18 to fix34
  • Use efficient cache lifetimes

    4.8 s · 2.2 MB

    119 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).

  • Improve image delivery

    2.6 s · 4.2 MB

    32 images could be 4.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.

  • Reduce unused JavaScript

    4.5 s · 1,004 KiB

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

  • Render-blocking requests

    3.0 s

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

  • Font display

    1.9 s

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.9 s).

  • Google Tag Manager adds 1.7 s

    1.7 s

    Google Tag Manager costs a phone 1.7 s of main-thread work and 1.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 34

    34/100

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

  • Main-thread work: 5.9 s

    A phone's processor spends 5.9 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, Facebook and Google Maps and others), adding 2.2 MB and 2.8 s of main-thread time.

  • 20 long tasks on the main thread

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

  • Reduce initial server response time

    568 ms

    Reduce initial server response time. Google estimates savings of 568 ms on a phone.

  • Document request latency

    550 ms

    The HTML itself could arrive about 550 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Legacy JavaScript

    450 ms · 42 KiB

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

  • Facebook adds 414 ms

    414 ms

    Facebook costs a phone 414 ms of main-thread work and 313 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.

  • Google Maps adds 316 ms

    316 ms

    Google Maps costs a phone 316 ms of main-thread work and 515 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.

  • Reduce unused CSS

    300 ms · 63 KiB

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

  • 1,929 HTML elements

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

  • Server response: 668 ms

    668 ms

    Your server takes 668 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Minify JavaScript

    27 KiB

    27 KiB could be saved by minifying JavaScript.

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

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

Core Web Vitals

12 to fix0
  • 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.

  • Real-user CLS: 0.26

    0.26

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

  • Largest Contentful Paint: 59.6 s

    59.6 s

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

  • Time to Interactive: 62.9 s

    62.9 s

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

  • Speed Index: 14.9 s

    14.9 s

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

  • Total Blocking Time: 2.2 s

    2.2 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user INP: 229 ms

    229 ms

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

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

    +32%

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

  • Real-user TTFB: 956 ms

    956 ms

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

  • 62 images without width and height

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

  • First Contentful Paint: 2.5 s

    2.5 s

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

2 checks passed
  • Real-user FCP: 1.8 s

    1.8 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 19.1 MB in 196 requests

    19.1 MB

    Your homepage downloads 19.1 MB in 196 requests on a phone: images 16.4 MB (85), scripts 2.4 MB (62) and fonts 111 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 9 images over 500 KB

    9 images weigh 9.5 MB together. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    699 KiB

    6 images are downloaded at several times the size a phone draws them, for example 1780406829Blogimage1jpeg.jpeg at 1,600 px wide, shown at 360 px. Resized copies would save about 699 KiB.

  • 40 images in older formats

    40 images (15.6 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.

  • 22 images below the first screen load straight away

    22 images further down the page (3.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 5.4 g of CO₂ per visit

    5.41 g

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

Accessibility

8 to fixGoogle 8788
  • Unlabelled dropdowns

    1 dropdown has no label.

  • 8 text elements with low contrast

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

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

  • 8 images without alt text

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

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

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

  • 29 form fields without a label

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

  • 6 links without text

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

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.

1 checks passed
  • 48 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: 48 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 7780
  • No structured data

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

  • Meta description is long (299 characters)

    Your meta description is 299 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

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

  • 4 links crawlers can't follow

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

  • 3 links with vague text

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

  • One H1 headline

    Your <h1> is empty.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 122 internal links, 20 external

    The homepage links to 122 pages on kutchina.com and 20 external pages.

4 checks passed
  • Title: 61 characters

    Your title is a healthy 61 characters: “Leading Home and Kitchen Appliances brand in India - Kutchina”.

  • Canonical URL set

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

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.kutchina.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.

  • No llms.txt

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

  • Text is in the HTML

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

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

3 to fixGoogle 9285
  • 14 small tap targets

    14 of 49 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 “Element with ID "before-image" not found.”.

  • 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

1 to fix92
  • A 16-field form

    Your longest form asks for 16 fields (7 required). Every extra field lowers completion.

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

    The homepage carries about 1,396 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: “Shop Online” and “Book My Appointment”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Contact Us”, “Shop Online” and “Book My Appointment”.

  • Social proof on the page

    Social proof on the homepage: 16 testimonial or review blocks, 1 customer or partner logo and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 6 email links.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot 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.

  • 8 cookies set on arrival

    8

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

  • 26 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Hostinger

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 55 issues on kutchina.com, including 30 speed issues, 6 SEO issues and 1 conversion gap. 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