Website review, no card needed

drvaidyas.com logo

drvaidyas.com website review

Visit site (opens in a new tab)Reviewed 5 November 202654 issues · 92 checks

This review found 54 issues worth fixing on drvaidyas.com, 16 of them high impact, across 92 checks. The most urgent: 13,046 HTML elements. 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
5.7 s4.5 sMay 16Oct 315.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.6 s
May 23, 20264.6 s
May 30, 20264.6 s
Jun 6, 20264.7 s
Jun 13, 20264.7 s
Jun 20, 20264.8 s
Jun 27, 20264.7 s
Jul 4, 20264.7 s
Jul 11, 20264.8 s
Jul 18, 20264.9 s
Jul 25, 20264.9 s
Aug 1, 20265.0 s
Aug 8, 20264.9 s
Aug 15, 20264.8 s
Aug 22, 20264.7 s
Aug 29, 20264.7 s
Sep 5, 20264.7 s
Sep 12, 20264.8 s
Sep 19, 20265.0 s
Sep 26, 20265.2 s
Oct 3, 20265.3 s
Oct 10, 20265.5 s
Oct 17, 20265.6 s
Oct 24, 20265.5 s
Oct 31, 20265.5 s
Real-visitor tap response (INP)75th percentile, phones
408 ms244 msMay 16Oct 31389 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026263 ms
May 23, 2026276 ms
May 30, 2026291 ms
Jun 6, 2026302 ms
Jun 13, 2026302 ms
Jun 20, 2026296 ms
Jun 27, 2026293 ms
Jul 4, 2026292 ms
Jul 11, 2026294 ms
Jul 18, 2026299 ms
Jul 25, 2026307 ms
Aug 1, 2026314 ms
Aug 8, 2026320 ms
Aug 15, 2026326 ms
Aug 22, 2026329 ms
Aug 29, 2026322 ms
Sep 5, 2026319 ms
Sep 12, 2026323 ms
Sep 19, 2026324 ms
Sep 26, 2026340 ms
Oct 3, 2026354 ms
Oct 10, 2026364 ms
Oct 17, 2026377 ms
Oct 24, 2026386 ms
Oct 31, 2026389 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 drvaidyas.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. drvaidyas.com at 1.0 s1.0 s
  2. drvaidyas.com at 2.1 s2.1 s
  3. drvaidyas.com at 3.1 s3.1 s
  4. drvaidyas.com at 4.1 s4.1 s
  5. drvaidyas.com at 5.2 s5.2 s
  6. drvaidyas.com at 6.2 s6.2 s
  7. drvaidyas.com at 7.2 s7.2 s
  8. drvaidyas.com at 8.3 s8.3 s

Speed

11 to fix23
  • 13,046 HTML elements

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

  • Mobile performance score: 23

    23/100

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

  • Main-thread work: 8.9 s

    A phone's processor spends 8.9 s on main-thread work while loading, 4.1 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, Shopify and gokwik.co and others), adding 2.7 MB and 1.9 s of main-thread time.

  • Reduce unused JavaScript

    300 ms · 1.0 MB

    About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 880 ms

    880 ms

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

  • Shopify adds 597 ms

    597 ms

    Shopify costs a phone 597 ms of main-thread work and 905 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.

  • Use efficient cache lifetimes

    477 KiB

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

  • Improve image delivery

    150 ms · 276 KiB

    14 images could be 276 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 18 long tasks on the main thread

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

  • gokwik.co adds 167 ms

    167 ms

    gokwik.co costs a phone 167 ms of main-thread work and 505 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

    73 KiB

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

  • Legacy JavaScript

    58 KiB

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

  • Minify JavaScript

    41 KiB

    41 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    18 KiB

    18 KiB JavaScript is shipped twice across bundles.

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

1 checks passed
  • Server response: 27 ms

    27 ms

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

Core Web Vitals

14 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.79

    0.79

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

  • Time to Interactive: 27.1 s

    27.1 s

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

  • Cumulative Layout Shift: 0.818

    0.818

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

  • Largest Contentful Paint: 6.8 s

    6.8 s

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

  • Speed Index: 8.8 s

    8.8 s

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

  • Total Blocking Time: 914 ms

    914 ms

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

  • Real-user LCP: 3.6 s

    3.6 s

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

  • Real-user INP: 380 ms

    380 ms

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

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

    +44%

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

  • Largest content (LCP) got 20% slower for real visitors

    +20%

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • 1 image without width and height

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

1 checks passed
  • First Contentful Paint: 1.5 s

    1.5 s

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

Images and page weight

3 to fix60
  • Page weight: 6.5 MB in 491 requests

    6.5 MB

    Your homepage downloads 6.5 MB in 491 requests on a phone: images 2.4 MB (117), scripts 2.2 MB (89) and other files 1.2 MB (246). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    ACV_Juice_Mobile_Banner_1080_by_1080.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 2 images far larger than shown

    157 KiB

    2 images are downloaded at several times the size a phone draws them, for example Flipkart_Bag_Logo.png at 2,062 px wide, shown at 32 px. Resized copies would save about 157 KiB.

  • 1 image in older formats

    1 image (64 KiB) is 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.

  • 2 images below the first screen load straight away

    2 images further down the page (158 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.9 g of CO₂ per visit

    1.85 g

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

Accessibility

10 to fixGoogle 7287
  • Unlabelled dropdowns

    38 dropdowns have no label.

  • 26 text elements with low contrast

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

  • <marquee> elements are deprecated and must not be used (1 element)

    <marquee> elements are deprecated and must not be used: 1 element on the page fails this check, rated serious by axe-core.

  • 4 images without alt text

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

  • 520 form fields without a label

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

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

    All page content should be contained by landmarks: 13 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.

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

  • 9 links without text

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

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

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

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

1 checks passed
  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 10 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 7781
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Buy Ayurvedic Medicine & Products Online @ Upto 25% Off – Dr Vaidya's”.

  • No social preview image

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

  • 5 links crawlers can't follow

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

  • 4 links with vague text

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

  • 226 internal links, 2 external

    The homepage links to 226 pages on drvaidyas.com and 2 external pages.

5 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Avail Ayurvedic Medicine Online at great prices. Boost your Health with Best Ayurvedic Products for Piles, Liver & much…”.

  • Canonical URL set

    The canonical URL is https://drvaidyas.com/.

  • 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://drvaidyas.com/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: 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 (3,659 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix81
  • 2 pages share a title

    https://drvaidyas.com/collections/liver-health and https://drvaidyas.com/collections/liver-care all use the title “Liver Care Essentials: Ayurvedic Medicine for Liver Detox | Dr. Vaidy…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://drvaidyas.com/collections/pain-relief, https://drvaidyas.com/collections/womens-health-1, https://drvaidyas.com/collections/others and https://drvaidyas.com/collections/herboslim have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://drvaidyas.com/collections/liver-health and https://drvaidyas.com/collections/liver-care use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://drvaidyas.com/collections/fitness, whose canonical is https://drvaidyas.com/collections/weight-management. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

3 to fixGoogle 7385
  • 52 small tap targets

    52 of 128 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 third-party cookies

    3 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 “gtag is not defined”.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

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

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

    The homepage carries about 2,033 words of visible text.

3 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop All Products”, “Shop By Concern” and “Shop by Product”.

  • 134 short forms

    134 short forms (2 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

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.

  • 26 cookies set on arrival

    26

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

  • 34 other companies contacted

    Loading the homepage contacts 34 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 drvaidyas.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 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Noindexly · Hulk Form Builder · Judge Me Reviews · Cooee · Eg Auto Add To Cart · Foxkit Upsell Bundles · Cowlendar · gokwik.co

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

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

Company

Headquarters
Dhadhra

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 54 issues on drvaidyas.com, including 25 speed issues, 5 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