Website review, no card needed
ayushakti.com website review
Visit site (opens in a new tab)Reviewed 22 October 202637 issues · 86 checks
This review found 37 issues worth fixing on ayushakti.com, 10 of them high impact, across 86 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
77C- #69,071 of 124,541 reviewed websitesbeats 39%
- #44,662 of 69,950 online storesbeats 31%
- #42,460 of 63,592 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.2 s |
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.6 s |
| Aug 15, 2026 | 3.5 s |
| Aug 22, 2026 | 3.5 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 251 ms |
| May 9, 2026 | 239 ms |
| May 16, 2026 | 249 ms |
| May 23, 2026 | 239 ms |
| May 30, 2026 | 238 ms |
| Jun 6, 2026 | 239 ms |
| Jun 13, 2026 | 233 ms |
| Jun 20, 2026 | 229 ms |
| Jun 27, 2026 | 218 ms |
| Jul 4, 2026 | 212 ms |
| Jul 11, 2026 | 227 ms |
| Jul 18, 2026 | 232 ms |
| Jul 25, 2026 | 236 ms |
| Aug 1, 2026 | 309 ms |
| Aug 8, 2026 | 354 ms |
| Aug 15, 2026 | 355 ms |
| Aug 22, 2026 | 360 ms |
| Aug 29, 2026 | 359 ms |
| Sep 5, 2026 | 335 ms |
| Sep 12, 2026 | 332 ms |
| Sep 19, 2026 | 309 ms |
| Sep 26, 2026 | 261 ms |
| Oct 3, 2026 | 211 ms |
| Oct 10, 2026 | 210 ms |
| Oct 17, 2026 | 213 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.4 s · 245 KiBAbout 245 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Shopify and others), adding 1.4 MB and 879 ms of main-thread time.
Mobile performance score: 52
52/100Your mobile performance score is 52 (desktop: 92). Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
450 ms · 207 KiB9 files are served with short cache lifetimes, so returning visitors download them again (207 KiB).
Google Tag Manager adds 554 ms
554 msGoogle Tag Manager costs a phone 554 ms of main-thread work and 504 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
300 ms10 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
2,259 HTML elements
The page has 2,259 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 84 ms
84 msShopify costs a phone 84 ms of main-thread work and 710 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.
Improve image delivery
150 ms · 92 KiB3 images could be 92 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 235 ms. During a long task the page ignores taps.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 92 but mobile only 52. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 14 ms
14 msYour server sent the HTML in 14 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: 15.1 s
15.1 sYour largest element takes 15.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “World Renowned Healing Solutions. Trusted Globally Experien…”.
Time to Interactive: 15.8 s
15.8 sThe page becomes fully interactive after 15.8 s. Good is under 3.8 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Speed Index: 6.3 s
6.3 sVisually, the page fills in at 6.3 s (Speed Index). Good is under 3.4 s.
Real-user INP: 330 ms
330 msReal visitors wait 330 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 472 ms
472 msScripts block taps and scrolling for 472 ms in total while the page loads. Good is under 200 ms.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 773 ms
773 msReal visitors wait 773 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 251 ms to 213 ms 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).
Images and page weight
1 image over 500 KB
gempages_528723949530383382-3e0ae3cd-b661-4aac-8261-5d8e9e1b weighs 493 KiB. On a phone connection a single image that size takes seconds.
Page weight: 2.7 MB in 205 requests
2.7 MBYour homepage downloads 2.7 MB in 205 requests on a phone: scripts 955 KiB (58), images 825 KiB (46) and other files 692 KiB (76). Under 2 MB keeps phones on slow connections fast.
6 images in older formats
6 images (1.1 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.
13 images below the first screen load straight away
13 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.78 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.78 g of CO₂e: 93.4 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
12 images without alt text
12 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.
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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5 and h2 → h5), 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 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (83 characters)
Your title is 83 characters, so Google will cut it off around 60: “Best Ayurvedic Treatments & Natural Remedies for Chronic Diseases – Ayushakti India”.
67 internal links, 16 external
The homepage links to 67 pages on ayushakti.com and 16 external pages.
7 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “With over 37 years of experience, we offer proven herbal remedies for chronic diseases and transformative education to …”.
One H1 headline
Your main headline reads: “Ayurvedic Treatment & Natural Remedies Backed by 30+ Years of Healing Expertise”.
Canonical URL set
The canonical URL is https://www.ayushakti.com/.
Structured data in place
Structured data found: @LocalBusiness, 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.ayushakti.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 (1,111 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.ayushakti.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.ayushakti.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.ayushakti.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 pages without a meta description
https://www.ayushakti.com/collections/all, https://www.ayushakti.com/customer_authentication/redirect, https://www.ayushakti.com/pages/acidity-treatment, https://www.ayushakti.com/pages/arthritis-treatment, https://www.ayushakti.com/pages/asthama-treatment and https://www.ayushakti.com/pages/blood-pressuretreatment and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
14 pages without an H1
https://www.ayushakti.com/customer_authentication/redirect, https://www.ayushakti.com/pages/acidity-treatment, https://www.ayushakti.com/pages/arthritis-treatment, https://www.ayushakti.com/pages/asthama-treatment, https://www.ayushakti.com/pages/blood-pressuretreatment and https://www.ayushakti.com/pages/hairfall-treatment and 8 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 32 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
6 broken images
6 images failed to load on a phone, for example https://www.ayushakti.com/.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “jQuery is not defined”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
8 of 8 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 720 words of copy
The homepage carries about 720 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book My Consultation”.
12 calls to action
The homepage has 12 calls to action, for example “Shop”, “Book My Consultation” and “Book my Consultation”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (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.
9 cookies set on arrival
9Opening the homepage sets 9 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.
25 other companies contacted
Loading the homepage contacts 25 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 ayushakti.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
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 ayushakti.com, including 17 speed issues, 1 SEO issue and 2 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.