Website review, no card needed

tivityhealth.com logo

tivityhealth.com website review

Visit site (opens in a new tab)Reviewed 31 October 202643 issues · 94 checks

This review found 43 issues worth fixing on tivityhealth.com, 16 of them high impact, across 94 checks. The most urgent: use efficient cache lifetimes. 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.5 s2.8 sMay 9Oct 243.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.0 s
May 16, 20263.2 s
May 23, 20263.3 s
May 30, 20263.3 s
Jun 6, 20263.4 s
Jun 13, 20263.1 s
Jun 20, 20263.1 s
Jun 27, 20262.9 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.9 s
Aug 15, 20262.9 s
Aug 22, 20262.9 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20263.0 s
Sep 19, 20263.2 s
Sep 26, 20263.2 s
Oct 3, 20263.2 s
Oct 10, 20263.1 s
Oct 17, 20263.2 s
Oct 24, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
74 ms71 msMay 9Oct 2473 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202671 ms
May 16, 202671 ms
May 23, 202671 ms
May 30, 202671 ms
Jun 6, 202672 ms
Jun 13, 202672 ms
Jun 20, 202672 ms
Jun 27, 202671 ms
Jul 4, 202674 ms
Jul 11, 202672 ms
Jul 18, 202674 ms
Jul 25, 202672 ms
Aug 1, 202671 ms
Aug 8, 202672 ms
Aug 15, 202671 ms
Aug 22, 202671 ms
Aug 29, 202671 ms
Sep 5, 202671 ms
Sep 12, 202672 ms
Sep 19, 202672 ms
Sep 26, 202673 ms
Oct 3, 202672 ms
Oct 10, 202673 ms
Oct 17, 202673 ms
Oct 24, 202673 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 tivityhealth.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tivityhealth.com at 1.0 s1.0 s
  2. tivityhealth.com at 2.0 s2.0 s
  3. tivityhealth.com at 2.9 s2.9 s
  4. tivityhealth.com at 3.9 s3.9 s
  5. tivityhealth.com at 4.9 s4.9 s
  6. tivityhealth.com at 5.9 s5.9 s
  7. tivityhealth.com at 6.8 s6.8 s
  8. tivityhealth.com at 7.8 s7.8 s

Speed

10 to fix43
  • Use efficient cache lifetimes

    5.4 s · 1.7 MB

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

  • Improve image delivery

    1.4 s · 578 KiB

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

  • Render-blocking requests

    1.6 s

    22 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

  • Mobile performance score: 43

    43/100

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Facebook and TrustArc and others), adding 1.1 MB and 1.1 s of main-thread time.

  • Reduce unused JavaScript

    450 ms · 415 KiB

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

  • Google Tag Manager adds 659 ms

    659 ms

    Google Tag Manager costs a phone 659 ms of main-thread work and 507 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 306 ms

    306 ms

    Facebook costs a phone 306 ms of main-thread work and 210 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.8 s

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

  • TrustArc adds 146 ms

    146 ms

    TrustArc costs a phone 146 ms of main-thread work and 374 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.

  • 9 long tasks on the main thread

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

  • Font display

    150 ms

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

  • Reduce unused CSS

    35 KiB

    About 35 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    13 KiB

    Polyfills for old browsers add 13 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 36 ms

    36 ms

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

Core Web Vitals

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

  • Real-user FCP: 3.3 s

    3.3 s

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

  • Real-user TTFB: 1.9 s

    1.9 s

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

  • Speed Index: 12.5 s

    12.5 s

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

  • Largest Contentful Paint: 6.3 s

    6.3 s

    Your largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Live Healthy. Live Long.tm”. Most of its time is resource load delay (5.6 s).

  • Time to Interactive: 11.8 s

    11.8 s

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

  • Total Blocking Time: 729 ms

    729 ms

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

  • Real-user LCP: 3.8 s

    3.8 s

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

  • Cumulative Layout Shift: 0.156

    0.156

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

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

3 checks passed
  • Real-user INP: 70 ms

    70 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

Images and page weight

1 to fix85
  • Page weight: 2.6 MB in 89 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 89 requests on a phone: scripts 1.1 MB (29), images 1,002 KiB (17) and fonts 529 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.75 g

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

9 to fixGoogle 9191
  • 5 text elements with low contrast

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

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

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

  • Banner landmark should not be contained in another landmark (1 element)

    Banner 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 banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails 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.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails 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.

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h2 → h4 and h3 → h5), which makes the page harder to scan with a screen reader.

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

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 7 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 10 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 9276
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (13 characters)

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

  • Meta description is long (185 characters)

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

  • 4 links with vague text

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

  • 52 internal links, 2 external

    The homepage links to 52 pages on tivityhealth.com and 2 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://www.tivityhealth.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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.tivityhealth.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.tivityhealth.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

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

Other pages

6 to fix69
  • 1 linked page hidden from search

    https://www.tivityhealth.com/brands/silversneakers-fitness is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://www.tivityhealth.com/about/our-company and https://www.tivityhealth.com/about all use the title “Our Company - Tivity Health”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://www.tivityhealth.com/leadership, https://www.tivityhealth.com/careers, https://www.tivityhealth.com/brands, https://www.tivityhealth.com/brands/wholehealth-living, https://www.tivityhealth.com/contact and https://www.tivityhealth.com/terms-of-use and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.tivityhealth.com/about/our-company and https://www.tivityhealth.com/about use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.tivityhealth.com/about, whose canonical is https://www.tivityhealth.com/about/our-company. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 7 pages without an H1

    https://www.tivityhealth.com/about/our-company, https://www.tivityhealth.com/about/tivity-cares, https://www.tivityhealth.com/brands/silversneakers-fitness, https://www.tivityhealth.com/brands/foreverfit-tivityhealth, https://www.tivityhealth.com/brands/wholehealth-living and https://www.tivityhealth.com/about and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://www.tivityhealth.com/careers, https://www.tivityhealth.com/about/tivity-cares, https://www.tivityhealth.com/brands/silversneakers-fitness and https://www.tivityhealth.com/contact took over 3 s to send their HTML from our server.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

2 checks passed
  • Linked pages load

    All 12 pages we checked loaded without an error.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9684
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=211075943&tm=gtm002&Ver=2&mid=9a7f9bc0-6091-421d-a87f-6f98c0e85b05&bo=1&sid=605448f0d57811f1a9a427d267c62481&vid=60549f80d57811f1bac0bbd1dbdaebf0&vids=1&msclkid=N&pi=9.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix69
  • 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.

  • No social proof

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

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

  • About 335 words of copy

    The homepage carries about 335 words of visible text.

5 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact”, “Learn more” and “LEARN MORE”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 5 trackers load before any consent

    5

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

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies (measured from a US location before any click).

  • 10 other companies contacted

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

1 checks passed
  • Consent tool: TrustArc

    A consent management tool (TrustArc) 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 tivityhealth.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
AWS

Company

Employees
443
Founded
1981
Headquarters
Franklin

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 tivityhealth.com, including 19 speed issues, 4 SEO issues and 3 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