Website review, no card needed

xarashilajit.com logo

xarashilajit.com website review

Visit site (opens in a new tab)Reviewed 6 November 202646 issues · 94 checks

This review found 46 issues worth fixing on xarashilajit.com, 18 of them high impact, across 94 checks. The most urgent: reduce unused JavaScript. 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.9 s2.5 sMay 16Oct 313.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.5 s
May 23, 20263.5 s
May 30, 20263.6 s
Jun 6, 20263.4 s
Jun 13, 20263.3 s
Jun 20, 20263.2 s
Jun 27, 20263.2 s
Jul 4, 20263.1 s
Jul 11, 20263.1 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Aug 1, 20262.8 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.8 s
Sep 5, 20263.0 s
Sep 12, 20263.2 s
Sep 19, 20263.6 s
Sep 26, 20263.7 s
Oct 3, 20263.8 s
Oct 10, 20263.7 s
Oct 17, 20263.5 s
Oct 24, 20263.4 s
Oct 31, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
378 ms144 msMay 16Oct 31207 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026351 ms
May 23, 2026348 ms
May 30, 2026344 ms
Jun 6, 2026338 ms
Jun 13, 2026328 ms
Jun 20, 2026304 ms
Jun 27, 2026253 ms
Jul 4, 2026208 ms
Jul 11, 2026187 ms
Jul 18, 2026178 ms
Jul 25, 2026178 ms
Aug 1, 2026178 ms
Aug 8, 2026172 ms
Aug 15, 2026171 ms
Aug 22, 2026171 ms
Aug 29, 2026180 ms
Sep 5, 2026195 ms
Sep 12, 2026207 ms
Sep 19, 2026221 ms
Sep 26, 2026220 ms
Oct 3, 2026216 ms
Oct 10, 2026209 ms
Oct 17, 2026204 ms
Oct 24, 2026203 ms
Oct 31, 2026207 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 xarashilajit.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

15 to fix34
  • Reduce unused JavaScript

    4.6 s · 806 KiB

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

  • Improve image delivery

    3.5 s · 1.1 MB

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

  • Use efficient cache lifetimes

    3.5 s · 693 KiB

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

  • Main-thread work: 10.1 s

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

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

  • 7,866 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (alia-prod.com, Facebook and Google Tag Manager and others), adding 4.5 MB and 2.3 s of main-thread time.

  • alia-prod.com adds 484 ms

    484 ms

    alia-prod.com costs a phone 484 ms of main-thread work and 1.2 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.

  • Font display

    450 ms

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

  • Google Tag Manager adds 367 ms

    367 ms

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

  • Facebook adds 378 ms

    378 ms

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

  • Legacy JavaScript

    300 ms · 95 KiB

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

  • redretarget.com adds 292 ms

    292 ms

    redretarget.com costs a phone 292 ms of main-thread work and 111 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.

  • loox.io adds 281 ms

    281 ms

    loox.io costs a phone 281 ms of main-thread work and 27 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 261 ms. During a long task the page ignores taps.

  • Render-blocking requests

    250 ms

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

  • Reduce unused CSS

    150 ms · 10 KiB

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

  • Minify JavaScript

    12 KiB

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

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

    24 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 34.4 s

    34.4 s

    Your largest element takes 34.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “TRY YOUR LUCK Scratch below to see what you win You've got …”.

  • Time to Interactive: 38.0 s

    38.0 s

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

  • Speed Index: 14.2 s

    14.2 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Real-user TTFB: 807 ms

    807 ms

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Cumulative Layout Shift: 0.108

    0.108

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

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

4 checks passed
  • Real-user INP: 152 ms

    152 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Tap response (INP) got 41% faster for real visitors

    -41%

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

Images and page weight

1 to fix70
  • Page weight: 7.1 MB in 573 requests

    7.1 MB

    Your homepage downloads 7.1 MB in 573 requests on a phone: images 3.1 MB (265), scripts 2.3 MB (104) and other files 1.0 MB (153). Under 2 MB keeps phones on slow connections fast.

  • About 2.0 g of CO₂ per visit

    2.02 g

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

3 checks passed
  • 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

6 to fixGoogle 9191
  • 15 text elements with low contrast

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

  • <dt> and <dd> elements must be contained by a <dl> (8 elements)

    <dt> and <dd> elements must be contained by a <dl>: 8 elements on the page fail this check, rated serious by axe-core.

  • <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements (3 elements)

    <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 3 elements on the page fail this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

  • 1 form field without a label

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

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

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

2 checks passed
  • Every image has alt text

    All 737 images in the HTML carry an alt attribute.

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

SEO

4 to fixGoogle 9275
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (13 characters)

    Your title is only 13 characters: “XARA Shilajit”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 3 H1 headlines

    There are 3 <h1> headlines (“”, “Pure Himalayan energy, without the mess” and “Ancient Resin.Modern Daily Ritual.”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 41 internal links, 10 external

    The homepage links to 41 pages on xarashilajit.com and 10 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.xarashilajit.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://www.xarashilajit.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 (1,869 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix83
  • 2 pages share a title

    https://www.xarashilajit.com/pages/cancellation-policy and https://www.xarashilajit.com/policies/subscription-policy all use the title “Cancellation Policy – XARA Shilajit”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages without a meta description

    https://www.xarashilajit.com/pages/subscription-management, https://www.xarashilajit.com/collections/performance-drive, https://www.xarashilajit.com/collections/brain-nerve, https://www.xarashilajit.com/collections/thyroid-immunity, https://www.xarashilajit.com/collections/bundles-1 and https://www.xarashilajit.com/collections/best-sellers-home and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://www.xarashilajit.com/pages/contact-us, https://www.xarashilajit.com/apps/track, https://www.xarashilajit.com/pages/subscription-management, https://www.xarashilajit.com/collections/performance-drive, https://www.xarashilajit.com/collections/brain-nerve and https://www.xarashilajit.com/collections/thyroid-immunity and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://www.xarashilajit.com/collections/bundles-1 and https://www.xarashilajit.com/collections/best-sellers-home took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 1 third-party cookie

    1 third-party cookie is 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 “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix72
  • 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.

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

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Only about 151 words

    The homepage has only about 151 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

  • Urgency cues

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

5 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “Contact Us”, “Track Your Order” and “Shop the gummies”.

  • 7 short forms

    7 short forms (5 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 6 testimonial or review blocks, 6 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics and TikTok Pixel.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Outbrain and 3 mores (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.

  • 36 cookies set on arrival

    36

    Opening the homepage sets 36 cookies, 3 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.

  • 59 other companies contacted

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

Apps your storefront loads

Wetracked Io Connect · Kaching Bundles · Triplewhale · Instant Ai Page Builder · Beast Currency Converter · Elevate Ab Testing · Simprosys Google Shopping Feed · Klaviyo Email Marketing Sms · Eg Auto Add To Cart · Countdown Timer · weglot.com · socialsnowball.io · redretarget.com · loox.io · cloudfront.net · archive-digger.com

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
Tailwind CSS
E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on xarashilajit.com, including 25 speed issues, 4 SEO issues and 4 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