Website review, no card needed

knitco.in logo

knitco.in website review

Visit site (opens in a new tab)Reviewed 16 November 202637 issues · 77 checks

This review found 37 issues worth fixing on knitco.in, 11 of them high impact, across 77 checks. The most urgent: 2 buttons without a name. 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 knitco.in (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. knitco.in at 1.0 s1.0 s
  2. knitco.in at 2.0 s2.0 s
  3. knitco.in at 3.1 s3.1 s
  4. knitco.in at 4.1 s4.1 s
  5. knitco.in at 5.1 s5.1 s
  6. knitco.in at 6.1 s6.1 s
  7. knitco.in at 7.1 s7.1 s
  8. knitco.in at 8.2 s8.2 s

Speed

8 to fix69
  • 8 third-party services on the page

    8 third-party services load with your homepage (Sentry, Facebook and Google Tag Manager and others), adding 1.2 MB and 1.1 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.

  • Sentry adds 342 ms

    342 ms

    Sentry costs a phone 342 ms of main-thread work and 16 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.3 s

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

  • cloudfront.net adds 210 ms

    210 ms

    cloudfront.net costs a phone 210 ms of main-thread work and 579 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 JavaScript

    268 KiB

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

  • Google Tag Manager adds 221 ms

    221 ms

    Google Tag Manager costs a phone 221 ms of main-thread work and 299 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,006 HTML elements

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

  • 9 long tasks on the main thread

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

  • Use efficient cache lifetimes

    192 KiB

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

  • Legacy JavaScript

    11 KiB

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

  • Improve image delivery

    9 KiB

    1 image could be 9 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

    253 ms

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

Core Web Vitals

4 to fix71
  • Time to Interactive: 9.8 s

    9.8 s

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

  • Speed Index: 7.2 s

    7.2 s

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

  • Total Blocking Time: 558 ms

    558 ms

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

  • Cumulative Layout Shift: 0.198

    0.198

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

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

2 checks passed
  • Largest Contentful Paint: 2.0 s

    2.0 s

    Your largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image “BANNER_undefined__undefined”.

  • First Contentful Paint: 0.9 s

    0.9 s

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

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.36 g

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

4 checks passed
  • Page weight: 1.3 MB in 65 requests

    1.3 MB

    Your homepage downloads 1.3 MB in 65 requests on a phone: scripts 876 KiB (29), other files 185 KiB (21) and fonts 103 KiB (2). That is a lean page.

  • 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

9 to fixGoogle 7482
  • 2 buttons without a name

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

  • Hidden but focusable

    24 elements hidden from screen readers can still receive keyboard focus.

  • 12 text elements with low contrast

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 links without text

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

  • 1 form field without a label

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

2 checks passed
  • Every image has alt text

    All 114 images in the HTML carry an alt attribute.

  • 27 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 27 passed and 8 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10082
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 86 internal links, 3 external

    The homepage links to 86 pages on knitco.in and 3 external pages.

5 checks passed
  • Meta description: 118 characters

    Your meta description is 118 characters: “Welcome to Knitco website, we are an MSE based out of India. We aim to deliver high-quality products to our customers.”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Buy Knitco products online at best prices on https://knitco.in”.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://knitco.in/sitemap.xml.

AI search readiness

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

  • Some text only appears after JavaScript runs

    30%

    The HTML your server sends has 391 of the 1,299 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

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.

  • llms.txt published

    The site publishes https://knitco.in/llms.txt (3 KiB, 16 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix67
  • 2 pages without a title

    https://knitco.in/orders and https://knitco.in/bag have no <title>, so Google invents the link text in results.

  • 2 pages share a title

    https://knitco.in/collection/DlPZ5qyc and https://knitco.in/SWEATER-VEST/collection/DlPZ5qyc all use the title “Knitco SWEATER VEST - Buy SWEATER VEST from https://knitco.in online …”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://knitco.in/orders and https://knitco.in/bag have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://knitco.in/collection/DlPZ5qyc and https://knitco.in/SWEATER-VEST/collection/DlPZ5qyc use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://knitco.in/orders, https://knitco.in/bag, https://knitco.in/Red-Boys-Round-Neck--Colour-Regular-Fit-Acrylic-Full/catalogue/8oy1ohjl/cjPnFJh_ and https://knitco.in/Yellow-Girls-Round-Neck-Striped--Colour-Regular-Fit-Full/catalogue/6IBjJnmi/VFRfWJ7D have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://knitco.in/bag has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 2 pages slow to respond

    https://knitco.in/SKIVI/collection/6bES2Gmx and https://knitco.in/KIDS-PULLOVERS/collection/hcRzL9qT took over 3 s to send their HTML from our server.

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 9678
  • 3 broken images

    3 images failed to load on a phone, for example https://d1311wbk6unapo.cloudfront.net/NushopWebsiteAsset/tr:w-300,,f-webp,fo-auto/66acb26f9c1091a349ae242a_logo_OX2HPLNGRC_2024-08-12.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getRegistrations')”.

2 checks passed
  • Tap targets are thumb-sized

    50 of 52 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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.

  • Thin social proof

    Social proof on the homepage: 49 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

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

2 checks passed
  • Analytics in place

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

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

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, Meta Pixel and Microsoft Clarity (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.

  • 6 cookies set on arrival

    6

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

  • 20 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on knitco.in, including 12 speed issues, 3 SEO issues and 3 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