Programmable

Website review, no card needed

wellnessnest.co logo

wellnessnest.co website review

Visit site (opens in a new tab)Reviewed 12 November 202633 issues · 73 checks

This review found 33 issues worth fixing on wellnessnest.co, 5 of them high impact, across 73 checks. The most urgent: fails Core Web Vitals for real visitors. 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

Site score

78C

Closest competitors among Shopify stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
5.1 s1.2 sMay 23Nov 73.4 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20262.0 s
Jul 4, 20262.4 s
Jul 11, 20263.2 s
Jul 18, 20263.9 s
Jul 25, 20264.2 s
Aug 1, 20264.2 s
Aug 8, 20264.2 s
Aug 15, 20264.4 s
Aug 22, 20264.4 s
Aug 29, 20264.6 s
Sep 5, 20264.6 s
Sep 12, 20264.6 s
Sep 19, 20264.6 s
Sep 26, 20264.4 s
Oct 3, 20264.6 s
Oct 10, 20264.6 s
Oct 17, 20264.6 s
Oct 24, 20264.7 s
Oct 31, 20264.1 s
Nov 7, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
382 ms198 msMay 23Nov 7219 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026350 ms
May 30, 2026359 ms
Jun 6, 2026346 ms
Jun 13, 2026361 ms
Jun 20, 2026345 ms
Jun 27, 2026344 ms
Jul 4, 2026360 ms
Jul 11, 2026329 ms
Jul 18, 2026318 ms
Jul 25, 2026303 ms
Aug 1, 2026312 ms
Aug 8, 2026324 ms
Aug 15, 2026318 ms
Aug 22, 2026287 ms
Aug 29, 2026283 ms
Sep 5, 2026262 ms
Sep 12, 2026255 ms
Sep 19, 2026269 ms
Sep 26, 2026253 ms
Oct 3, 2026268 ms
Oct 10, 2026271 ms
Oct 17, 2026254 ms
Oct 24, 2026239 ms
Oct 31, 2026238 ms
Nov 7, 2026219 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

wellnessnest.co (opens in a new tab)
Full-page screenshot of wellnessnest.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wellnessnest.co at 0.7 s0.7 s
  2. wellnessnest.co at 1.4 s1.4 s
  3. wellnessnest.co at 2.2 s2.2 s
  4. wellnessnest.co at 2.9 s2.9 s
  5. wellnessnest.co at 3.6 s3.6 s
  6. wellnessnest.co at 4.3 s4.3 s
  7. wellnessnest.co at 5.1 s5.1 s
  8. wellnessnest.co at 5.8 s5.8 s

Speed

8 to fix67

  • Mobile performance score: 67

    67/100

    Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    600 ms · 127 KiB

    About 127 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Improve image delivery

    150 ms · 461 KiB

    11 images could be 461 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.

  • Reduce unused CSS

    300 ms · 68 KiB

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

  • Render-blocking requests

    350 ms

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

  • Google Tag Manager adds 205 ms

    205 ms

    Google Tag Manager costs a phone 205 ms of main-thread work and 307 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: 2.1 s

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

  • 1,560 HTML elements

    The page has 1,560 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 (Google Tag Manager, Clarity and Klaviyo and others), adding 659 KiB and 444 ms of main-thread time.

  • Use efficient cache lifetimes

    150 ms · 41 KiB

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

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    19 KiB

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

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

1 checks passed

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

10 to fix33

  • 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: 11.7 s

    11.7 s

    Your largest element takes 11.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “ShilaSource Himalayan Shilajit Resin tube and jar, AgeAura …”.

  • Time to Interactive: 11.7 s

    11.7 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Real-user INP: 236 ms

    236 ms

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

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

    +123%

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Speed Index: 5.6 s

    5.6 s

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

4 checks passed

  • Real-user CLS: 0.00

    0.00

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

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

    -36%

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

  • Total Blocking Time: 147 ms

    147 ms

    Scripts block the page for only 147 ms while loading. Good is under 200 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 fix69

  • Page weight: 3.2 MB in 303 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 303 requests on a phone: other files 1.2 MB (195), images 910 KiB (19) and scripts 759 KiB (77). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    wn-gen-v5-hero-shila-s-900.webp 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).

  • 10 images in older formats

    10 images (655 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 0.9 g of CO₂ per visit

    0.90 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 107.6 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

1 to fixGoogle 10099

  • 22 links without text

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

2 checks passed

  • Every image has alt text

    All 81 images in the HTML carry an alt attribute.

  • 58 automated accessibility rules passed

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

SEO

3 to fixGoogle 10088

  • No structured data

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

  • Meta description is short (51 characters)

    Your meta description is only 51 characters: “Boosts Mental Clarity and Brain Processing Capacity”. 70 to 160 characters is enough to sell the click.

  • No social preview image

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

  • 98 internal links, 1 external

    The homepage links to 98 pages on wellnessnest.co and 1 external page.

5 checks passed

  • One H1 headline

    Your main headline reads: “Fuel the body you still use hard.”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “Wellness Nest - Shilajit Essential Extract”.

  • Canonical URL set

    The canonical URL is https://wellnessnest.co/.

  • 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://wellnessnest.co/sitemap.xml.

AI search readiness

1 to fix88

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

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,543 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix68

  • 2 pages without a title

    https://wellnessnest.co/a/loop_subscriptions/customer and https://wellnessnest.co/customer_authentication/redirect have no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://wellnessnest.co/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 5 pages without a meta description

    https://wellnessnest.co/pages/reviews, https://wellnessnest.co/a/loop_subscriptions/customer, https://wellnessnest.co/collections/all, https://wellnessnest.co/customer_authentication/redirect and https://wellnessnest.co/blogs/news have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://wellnessnest.co/products/florafresh-vaginal-probiotics-gummies, https://wellnessnest.co/collections/shop-all, https://wellnessnest.co/pages/reviews, https://wellnessnest.co/a/loop_subscriptions/customer, https://wellnessnest.co/collections/all and https://wellnessnest.co/customer_authentication/redirect 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 23 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

2 to fixGoogle 9678

  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187088123&tm=gtm002&Ver=2&mid=6b1eb5a3-272d-4ce8-83e6-541ca2973819&bo=1&sid=40e07c80de3e11f1b7a6bf4dd5356bfc&vid=40e0a790de3e11f1b7078917311a93dc&vids=1&msclkid=N&gtm_.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught Error: Goaffpro is already loaded. This message prevents duplicate loading of the script. Kindly ignore.”.

2 checks passed

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100

  • About 440 words of copy

    The homepage carries about 440 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: “SHOP THE 3 FORMULAS”.

  • 20 calls to action

    The homepage has 20 calls to action, for example “Shop the 3 formulas”, “View clinicians & learn more” and “Shop ShilaSource”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 5 testimonial or review blocks, a star rating and “41,000+ reviews”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix

  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 4 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.

  • 21 cookies set on arrival

    21

    Opening the homepage sets 21 cookies, 2 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.

  • 33 other companies contacted

    Loading the homepage contacts 33 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 wellnessnest.co, 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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Aftersell · Trueprofit · trustpilot.com · goaffpro.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
Bootstrap
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on wellnessnest.co, including 18 speed issues and 3 SEO issues. 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