Website review, no card needed

Anveshan logo

anveshan.farm website review

Visit site (opens in a new tab)Reviewed 23 October 202641 issues · 91 checks

This review found 41 issues worth fixing on anveshan.farm, 15 of them high impact, across 91 checks. The most urgent: main-thread work: 11.5 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Anveshan

  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.5 s1.9 sMay 2Oct 172.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.1 s
May 9, 20262.1 s
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
378 ms238 msMay 2Oct 17362 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026254 ms
May 9, 2026256 ms
May 16, 2026260 ms
May 23, 2026263 ms
May 30, 2026269 ms
Jun 6, 2026275 ms
Jun 13, 2026278 ms
Jun 20, 2026275 ms
Jun 27, 2026273 ms
Jul 4, 2026272 ms
Jul 11, 2026270 ms
Jul 18, 2026272 ms
Jul 25, 2026274 ms
Aug 1, 2026280 ms
Aug 8, 2026294 ms
Aug 15, 2026311 ms
Aug 22, 2026327 ms
Aug 29, 2026339 ms
Sep 5, 2026346 ms
Sep 12, 2026346 ms
Sep 19, 2026346 ms
Sep 26, 2026350 ms
Oct 3, 2026349 ms
Oct 10, 2026360 ms
Oct 17, 2026362 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 anveshan.farm (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. anveshan.farm at 1.7 s1.7 s
  2. anveshan.farm at 3.3 s3.3 s
  3. anveshan.farm at 5.0 s5.0 s
  4. anveshan.farm at 6.7 s6.7 s
  5. anveshan.farm at 8.3 s8.3 s
  6. anveshan.farm at 10.0 s10.0 s
  7. anveshan.farm at 11.7 s11.7 s
  8. anveshan.farm at 13.3 s13.3 s

Speed

11 to fix45
  • Main-thread work: 11.5 s

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

  • Mobile performance score: 45

    45/100

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

  • 3,809 HTML elements

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

  • Reduce unused JavaScript

    2.7 MB

    About 2.7 MB of JavaScript is downloaded but never used on this page.

  • 8 third-party services on the page

    8 third-party services load with your homepage (shiprocket.in, Freshchat and pickrr.com and others), adding 2.9 MB and 2.1 s of main-thread time.

  • shiprocket.in adds 542 ms

    542 ms

    shiprocket.in costs a phone 542 ms of main-thread work and 120 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.

  • pickrr.com adds 405 ms

    405 ms

    pickrr.com costs a phone 405 ms of main-thread work and 1.3 MB 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.

  • Freshchat adds 451 ms

    451 ms

    Freshchat costs a phone 451 ms of main-thread work and 763 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.

  • 20 long tasks on the main thread

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

  • Use efficient cache lifetimes

    364 KiB

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

  • anveshan.ai adds 182 ms

    182 ms

    anveshan.ai costs a phone 182 ms of main-thread work and 334 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.

  • Render-blocking requests

    200 ms

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

  • Improve image delivery

    137 KiB

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

  • Reduce unused CSS

    78 KiB

    About 78 KiB of CSS is downloaded but never applied on this page.

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

  • Duplicated JavaScript

    5 KiB

    5 KiB JavaScript is shipped twice across bundles.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 24 ms

    24 ms

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

Core Web Vitals

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

  • Time to Interactive: 33.8 s

    33.8 s

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

  • Largest Contentful Paint: 7.1 s

    7.1 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Speed Index: 6.2 s

    6.2 s

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

  • Real-user INP: 370 ms

    370 ms

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

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

    +42%

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

  • 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) got 14% slower for real visitors

    +14%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.4 s 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 CLS: 0.01

    0.01

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

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

  • Real-user TTFB: 583 ms

    583 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix35
  • Page weight: 6.4 MB in 380 requests

    6.4 MB

    Your homepage downloads 6.4 MB in 380 requests on a phone: scripts 2.4 MB (98), images 2.1 MB (83) and other files 1.2 MB (137). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    50-off-deals-exact-tight.svg weighs 744 KiB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    831 KiB

    2 images are downloaded at several times the size a phone draws them, for example 50-off-deals-exact-tight.svg at 1,205 px wide, shown at 37 px. Resized copies would save about 831 KiB.

  • 7 images in older formats

    7 images (315 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 1.8 g of CO₂ per visit

    1.81 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

7 to fixGoogle 9091
  • Elements must only use permitted ARIA attributes (41 elements)

    Elements must only use permitted ARIA attributes: 41 elements on the page fail this check, rated serious by axe-core.

  • 13 text elements with low contrast

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

  • Scrollable region must have keyboard access (3 elements)

    Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

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

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

  • Alternative text of images should not be repeated as text (18 elements)

    Alternative text of images should not be repeated as text: 18 elements on the page fail this check, rated minor by axe-core.

  • 2 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

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

    Elements with visible text labels do not have matching accessible names. (19 elements).

2 checks passed
  • Every image has alt text

    All 300 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 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

5 to fixGoogle 9278
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “🔥 POP30 Sale 30% OFF | Anveshan - Natural & Healthy Food Products”.

  • 5 H1 headlines

    There are 5 <h1> headlines (“”, “Welcome To Anveshan!” and “Native Ingredients. No Substitutes.”). One clear main headline is easier for people and search engines.

  • Meta description is long (295 characters)

    Your meta description is 295 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.

  • 18 links crawlers can't follow

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

  • 283 internal links, 3 external

    The homepage links to 283 pages on anveshan.farm and 3 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.anveshan.farm/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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.anveshan.farm/sitemap.xml.

AI search readiness

1 to fix88
  • Some text only appears after JavaScript runs

    52%

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

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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • llms.txt published

    The site publishes https://www.anveshan.farm/llms.txt (27 KiB, 216 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 5 pages without a meta description

    https://www.anveshan.farm/pages/gift-card, https://www.anveshan.farm/pages/gifting-collection, https://www.anveshan.farm/pages/affiliate, https://www.anveshan.farm/blogs/recipes and https://www.anveshan.farm/blogs/medicinal-recipes have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://www.anveshan.farm/collections/pop-sale, https://www.anveshan.farm/collections/desi-ghee, https://www.anveshan.farm/collections/wood-cold-pressed-oils, https://www.anveshan.farm/collections/a2-desi-ghee-wood-press-oil-combo-packs, https://www.anveshan.farm/collections/all-products and https://www.anveshan.farm/collections/khapli-atta and 2 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 60 found) and read each the way a search engine does.

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

  • 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

2 to fixGoogle 6991
  • 6 third-party cookies

    6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'register')”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Requests the notification permission on page load

    Requests the notification permission on page load.

2 checks passed
  • Tap targets are thumb-sized

    53 of 54 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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,492 words of copy

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

  • Urgency cues

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

5 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Shop”, “Shop Under ₹499” and “Shop Under ₹999”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 2 customer or partner logos and 7 trust badges.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 0 phone links 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.

  • 18 cookies set on arrival

    18

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

  • 35 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on anveshan.farm, including 19 speed issues, 5 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