Website review, no card needed

twc.health logo

twc.health website review

Visit site (opens in a new tab)Reviewed 25 October 202642 issues · 91 checks

This review found 42 issues worth fixing on twc.health, 15 of them high impact, across 91 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.4 s2.7 sMay 2Oct 172.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.8 s
May 9, 20262.8 s
May 16, 20262.9 s
May 23, 20262.9 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20263.0 s
Jun 20, 20263.0 s
Jun 27, 20263.0 s
Jul 4, 20263.0 s
Jul 11, 20263.0 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Aug 1, 20263.1 s
Aug 8, 20263.2 s
Aug 15, 20263.3 s
Aug 22, 20263.3 s
Aug 29, 20263.3 s
Sep 5, 20263.3 s
Sep 12, 20263.3 s
Sep 19, 20263.2 s
Sep 26, 20263.2 s
Oct 3, 20263.1 s
Oct 10, 20263.0 s
Oct 17, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
168 ms133 msMay 2Oct 17154 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026137 ms
May 9, 2026137 ms
May 16, 2026138 ms
May 23, 2026140 ms
May 30, 2026144 ms
Jun 6, 2026146 ms
Jun 13, 2026150 ms
Jun 20, 2026150 ms
Jun 27, 2026150 ms
Jul 4, 2026149 ms
Jul 11, 2026147 ms
Jul 18, 2026148 ms
Jul 25, 2026152 ms
Aug 1, 2026154 ms
Aug 8, 2026155 ms
Aug 15, 2026161 ms
Aug 22, 2026162 ms
Aug 29, 2026162 ms
Sep 5, 2026164 ms
Sep 12, 2026163 ms
Sep 19, 2026162 ms
Sep 26, 2026161 ms
Oct 3, 2026158 ms
Oct 10, 2026154 ms
Oct 17, 2026154 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 twc.health (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. twc.health at 1.5 s1.5 s
  2. twc.health at 3.0 s3.0 s
  3. twc.health at 4.4 s4.4 s
  4. twc.health at 5.9 s5.9 s
  5. twc.health at 7.4 s7.4 s
  6. twc.health at 8.8 s8.8 s
  7. twc.health at 10.3 s10.3 s
  8. twc.health at 11.8 s11.8 s

Speed

14 to fix31
  • Reduce unused JavaScript

    1.4 s · 1.6 MB

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

  • Render-blocking requests

    1.2 s

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

  • Main-thread work: 10.5 s

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

  • Mobile performance score: 31

    31/100

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

  • 8 third-party services on the page

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

  • Use efficient cache lifetimes

    150 ms · 948 KiB

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

  • Google CDN adds 652 ms

    652 ms

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

  • Reduce unused CSS

    480 ms · 100 KiB

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

  • Improve image delivery

    496 KiB

    15 images could be 496 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Google Tag Manager adds 346 ms

    346 ms

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

  • ContentSquare adds 312 ms

    312 ms

    ContentSquare costs a phone 312 ms of main-thread work and 177 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 296 ms. During a long task the page ignores taps.

  • 2,876 HTML elements

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

  • rechargecdn.com adds 98 ms

    98 ms

    rechargecdn.com costs a phone 98 ms of main-thread work and 297 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.

  • Minify JavaScript

    45 KiB

    45 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    38 KiB

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

1 checks passed
  • Server response: 34 ms

    34 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 10.0 s

    10.0 s

    Your largest element takes 10.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Medical Emergency Kit and supplement bottles”.

  • Time to Interactive: 41.6 s

    41.6 s

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

  • Total Blocking Time: 1.7 s

    1.7 s

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

  • Speed Index: 9.2 s

    9.2 s

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

  • First Contentful Paint: 4.6 s

    4.6 s

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

  • 9 images without width and height

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

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

    +12%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 137 ms to 154 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-17, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user INP: 142 ms

    142 ms

    Real visitors wait 142 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.

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 445 ms

    445 ms

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

  • Cumulative Layout Shift: 0.009

    0.009

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

Images and page weight

3 to fix50
  • Page weight: 8.4 MB in 532 requests

    8.4 MB

    Your homepage downloads 8.4 MB in 532 requests on a phone: scripts 3.7 MB (125), other files 2.7 MB (287) and images 1.2 MB (71). Under 2 MB keeps phones on slow connections fast.

  • 8 images in older formats

    8 images (1.0 MB) 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.

  • 4 images far larger than shown

    292 KiB

    4 images are downloaded at several times the size a phone draws them, for example senior-woman-video-call-wellness-care-mobile.webp at 446 px wide, shown at 109 px. Resized copies would save about 292 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (23 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.4 g of CO₂ per visit

    2.38 g

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

Accessibility

9 to fixGoogle 8488
  • 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.

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Malformed lists

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

  • 4 images without alt text

    4 images have no alt text, which hurts accessibility and image search.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 11 links without text

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

3 to fixGoogle 7789
  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “Emergency Kits, RX Access & Premium Supplements | The Wellness Company”.

  • 5 links crawlers can't follow

    5 links have no real href, so search engines can't follow them.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 426 internal links, 10 external

    The homepage links to 426 pages on twc.health and 10 external pages.

7 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Get emergency medical kits, RX access & physician-formulated supplements for everyday wellness from The Wellness Compan…”.

  • One H1 headline

    Your main headline reads: “The Wellness Company”.

  • Canonical URL set

    The canonical URL is https://www.twc.health/.

  • Structured data in place

    Structured data found: Organization 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.twc.health/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,907 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 2 pages without a meta description

    https://www.twc.health/pages/stock-up-and-save and https://www.twc.health/pages/replenish have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.twc.health/pages/medical-emergency-kit-study, https://www.twc.health/pages/ivermectin-mebendazole-cancer-study, https://www.twc.health/pages/stock-up-and-save, https://www.twc.health/products/ultimate-spike-detox, https://www.twc.health/products/emergency-preparedness-kit and https://www.twc.health/products/tirzepatide and 9 others 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 99 found) and read each the way a search engine does.

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

  • 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

3 to fixGoogle 7385
  • 11 small tap targets

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

  • 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 “Missing initializer in const declaration”.

  • Missing source maps

    Large scripts ship without source maps.

  • Requests the notification permission on page load

    Requests the notification permission on page load.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

    The homepage carries about 746 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: “Shop” and “Shop the Collection”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “Shop Best Sellers”, “Shop All Products” and “Talk to a Doc - Book An Appointment”.

  • 9 short forms

    9 short forms (3 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 50 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 11 trackers load before any consent

    11

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

  • 41 cookies set on arrival

    41

    Opening the homepage sets 41 cookies (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.

  • 91 other companies contacted

    Loading the homepage contacts 91 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 twc.health, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify Hosted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on twc.health, including 20 speed issues, 3 SEO issues and 1 conversion gap. 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