Website review, no card needed

artofliving.org logo

artofliving.org website review

Visit site (opens in a new tab)Reviewed 1 November 202643 issues · 91 checks

This review found 43 issues worth fixing on artofliving.org, 14 of them high impact, across 91 checks. The most urgent: page weight: 59.7 MB in 322 requests. 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
2.1 s1.9 sMay 9Oct 242.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.0 s
May 16, 20261.9 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
246 ms203 msMay 9Oct 24237 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026215 ms
May 16, 2026214 ms
May 23, 2026211 ms
May 30, 2026209 ms
Jun 6, 2026209 ms
Jun 13, 2026208 ms
Jun 20, 2026210 ms
Jun 27, 2026211 ms
Jul 4, 2026211 ms
Jul 11, 2026212 ms
Jul 18, 2026212 ms
Jul 25, 2026213 ms
Aug 1, 2026214 ms
Aug 8, 2026217 ms
Aug 15, 2026220 ms
Aug 22, 2026223 ms
Aug 29, 2026225 ms
Sep 5, 2026227 ms
Sep 12, 2026229 ms
Sep 19, 2026233 ms
Sep 26, 2026237 ms
Oct 3, 2026241 ms
Oct 10, 2026241 ms
Oct 17, 2026237 ms
Oct 24, 2026237 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 artofliving.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. artofliving.org at 1.5 s1.5 s
  2. artofliving.org at 3.0 s3.0 s
  3. artofliving.org at 4.5 s4.5 s
  4. artofliving.org at 6.0 s6.0 s
  5. artofliving.org at 7.5 s7.5 s
  6. artofliving.org at 9.0 s9.0 s
  7. artofliving.org at 10.5 s10.5 s
  8. artofliving.org at 12.0 s12.0 s

Speed

14 to fix34
  • Improve image delivery

    3.9 s · 1,022 KiB

    6 images could be 1,022 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.9 s faster on a phone.

  • Reduce unused JavaScript

    1.4 s · 2.6 MB

    About 2.6 MB 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.

  • Google Tag Manager adds 1.8 s

    1.8 s

    Google Tag Manager costs a phone 1.8 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 11.3 s

    A phone's processor spends 11.3 s on main-thread work while loading, 6.1 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.

  • Use efficient cache lifetimes

    450 ms · 52.3 MB

    83 files are served with short cache lifetimes, so returning visitors download them again (52.3 MB).

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 58.1 MB and 3.4 s of main-thread time.

  • Render-blocking requests

    450 ms

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

  • Vimeo adds 209 ms

    209 ms

    Vimeo costs a phone 209 ms of main-thread work and 2.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.

  • Facebook adds 382 ms

    382 ms

    Facebook costs a phone 382 ms of main-thread work and 321 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 397 ms. During a long task the page ignores taps.

  • TikTok adds 361 ms

    361 ms

    TikTok costs a phone 361 ms of main-thread work and 288 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

    300 ms · 61 KiB

    About 61 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.

  • Hubspot adds 253 ms

    253 ms

    Hubspot costs a phone 253 ms of main-thread work and 142 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

    150 ms · 99 KiB

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

  • Minify JavaScript

    150 ms · 17 KiB

    17 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

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

  • Duplicated JavaScript

    22 KiB

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

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 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: 14.3 s

    14.3 s

    Your largest element takes 14.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Calm your mind by controlling your breath Regain your calm …”.

  • Time to Interactive: 45.6 s

    45.6 s

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

  • Speed Index: 14.0 s

    14.0 s

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

  • Total Blocking Time: 3.3 s

    3.3 s

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Real-user INP: 229 ms

    229 ms

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • 18 images without width and height

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

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

    +10%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

3 checks passed
  • Real-user CLS: 0.03

    0.03

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

  • Real-user TTFB: 610 ms

    610 ms

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

  • Cumulative Layout Shift: 0.02

    0.02

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

Images and page weight

1 to fix70
  • Page weight: 59.7 MB in 322 requests

    59.7 MB

    Your homepage downloads 59.7 MB in 322 requests on a phone: media 51.5 MB (8), scripts 5.2 MB (116) and images 2.3 MB (78). Under 2 MB keeps phones on slow connections fast.

  • 6 images below the first screen load straight away

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

  • 2 images in older formats

    2 images (123 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 16.9 g of CO₂ per visit

    16.91 g

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

5 to fixGoogle 8691
  • Certain ARIA roles must contain particular children (2 elements)

    Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical 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.

  • Links must have discernible text (13 elements)

    Links must have discernible text: 13 elements on the page fail this check, rated serious by axe-core.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

2 checks passed
  • Every image has alt text

    All 102 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

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

SEO

5 to fixGoogle 9282
  • 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 long (178 characters)

    Your meta description is 178 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.artofliving.org/llms.txt, so Google discovers your pages only by following links.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 107 internal links, 51 external

    The homepage links to 107 pages on artofliving.org and 51 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Calm your mind by controlling your breath”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Art of Living | Meditation, Breathwork & Wellness Programs”.

  • Canonical URL set

    The canonical URL is https://www.artofliving.org/us-en.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

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 (919 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.artofliving.org/llms.txt (195 KiB, 1,861 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix83
  • 13 pages share a title

    https://www.artofliving.org/us-en/courses/art-of-living-part1, https://www.artofliving.org/us-en/courses/sahaj-samadhi-meditation, https://www.artofliving.org/us-en/courses/art-of-living-premium, https://www.artofliving.org/us-en/courses/sri-sri-yoga-foundation, https://www.artofliving.org/us-en/courses/sleep-anxiety-protocol and https://www.artofliving.org/us-en/courses/art-of-living-part2 and 7 others all use the title “Art of Living US Site”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://www.artofliving.org/us-en/start-here/5-day-breath-challenge, https://www.artofliving.org/us-en/start-here/7-day-meditation-challenge, https://www.artofliving.org/us-en/courses/art-of-living-part1, https://www.artofliving.org/us-en/courses/sahaj-samadhi-meditation, https://www.artofliving.org/us-en/courses/art-of-living-premium and https://www.artofliving.org/us-en/courses/sri-sri-yoga-foundation and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 links to non-canonical URLs

    Your homepage links to 15 pages by a URL that isn't their canonical one, for example https://www.artofliving.org/us-en/start-here/5-day-breath-challenge, whose canonical is https://www.artofliving.org/us-en/us-en/start-here/5-day-breath-challenge. 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 69 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

4 to fixGoogle 5483
  • 2 small tap targets

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

  • 2 third-party cookies

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 536 words of copy

    The homepage carries about 536 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact Us”, “Call us” and “Learn More”.

  • Social proof on the page

    Social proof on the homepage: 23 testimonial or review blocks and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 cookies, 2 of them by other companies (measured from a US location before any click).

  • 67 other companies contacted

    Loading the homepage contacts 67 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 artofliving.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Webflow
Framework
jQuery
Analytics
Google Tag Manager
Hosting
CloudFront

Company

Founded
1981
Headquarters
Bengaluru

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on artofliving.org, including 24 speed issues and 5 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