learntm.org website review

About 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 11.7 s faster on a phone.

Facebook costs a phone 11.1 s of main-thread work and 281 KiB 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.

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.4 s.

About 223 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

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

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

Google CDN costs a phone 305 ms of main-thread work and 1.4 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.

Trust Pilot costs a phone 147 ms of main-thread work and 304 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.

Google Maps costs a phone 116 ms of main-thread work and 448 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.

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

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

1 image could be 97 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 KiB JavaScript is shipped twice across bundles.

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.

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

Your largest element takes 33.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A woman meditating in a bright, quiet room”.

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

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

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

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

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

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

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

Your homepage downloads 8.1 MB in 199 requests on a phone: scripts 5.0 MB (80), other files 1.7 MB (68) and fonts 443 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

8 tap targets are too small or too close together to hit reliably with a finger.

Some lists contain elements other than list items, which screen readers announce wrongly.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

There are 3 <h1> headlines (“The only meditation that's”, “The only meditation that's” and “Find your local TM Center”). One clear main headline is easier for people and search engines.

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

The homepage links to 51 pages on learntm.org and 7 external pages.

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.

https://www.tm.org/en-us/transcendental-meditation-explained is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.tm.org/en-us/centers and https://www.tm.org/centers all use the title “TM Centers in the US | Transcendental Meditation”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.tm.org/en-us/centers and https://www.tm.org/centers have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.tm.org/en-us/theinnerwellpodcast, https://www.tm.org/en-us/faq and https://www.tm.org/en-us/benefits/mentalhealth use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.tm.org/centers, whose canonical is https://www.tm.org/en-us/centers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.tm.org/en-us/what-is-tm, https://www.tm.org/en-us/transcendental-meditation-explained, https://www.tm.org/en-us/contact-us, https://www.tm.org/en-us/benefits/health and https://www.tm.org/en-us/benefits/brain have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=4030906&tm=gtm002&Ver=2&mid=bda3a33c-6d3b-466b-a884-59334aec7517&bo=1&sid=b0cd1c10d4e011f18037219e84af1484&vid=b0cd5b50d4e011f18316691a73befc8d&vids=1&msclkid=N&pi=918.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage carries about 495 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 2 mores (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.

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

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