Website review, no card needed

gettrusupps.com logo

gettrusupps.com website review

Visit site (opens in a new tab)Reviewed 13 November 202625 issues · 78 checks

This review found 25 issues worth fixing on gettrusupps.com, 7 of them high impact, across 78 checks. The most urgent: page weight: 46.8 MB in 332 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.5 s1.6 sMay 23Nov 71.7 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.2 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.0 s
Aug 1, 20262.1 s
Aug 8, 20262.2 s
Aug 15, 20262.3 s
Aug 22, 20262.4 s
Aug 29, 20262.3 s
Sep 5, 20262.2 s
Sep 12, 20262.0 s
Sep 19, 20261.9 s
Sep 26, 20261.8 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Nov 7, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
135 ms81 msMay 23Nov 7111 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202687 ms
May 30, 202688 ms
Jun 6, 202690 ms
Jun 13, 202694 ms
Jun 20, 202696 ms
Jun 27, 202696 ms
Jul 4, 202696 ms
Jul 11, 202695 ms
Jul 18, 202694 ms
Jul 25, 202689 ms
Aug 1, 202695 ms
Aug 8, 202697 ms
Aug 15, 2026104 ms
Aug 22, 2026113 ms
Aug 29, 2026120 ms
Sep 5, 2026121 ms
Sep 12, 2026121 ms
Sep 19, 2026121 ms
Sep 26, 2026113 ms
Oct 3, 2026119 ms
Oct 10, 2026121 ms
Oct 17, 2026122 ms
Oct 24, 2026129 ms
Oct 31, 2026120 ms
Nov 7, 2026111 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 gettrusupps.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gettrusupps.com at 0.5 s0.5 s
  2. gettrusupps.com at 1.1 s1.1 s
  3. gettrusupps.com at 1.6 s1.6 s
  4. gettrusupps.com at 2.1 s2.1 s
  5. gettrusupps.com at 2.7 s2.7 s
  6. gettrusupps.com at 3.2 s3.2 s
  7. gettrusupps.com at 3.7 s3.7 s
  8. gettrusupps.com at 4.3 s4.3 s

Speed

10 to fix54
  • Main-thread work: 6.5 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Heroku and alia-prod.com and others), adding 1.8 MB and 1.4 s of main-thread time.

  • Mobile performance score: 54

    54/100

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

  • Reduce unused JavaScript

    835 KiB

    About 835 KiB of JavaScript is downloaded but never used on this page.

  • Render-blocking requests

    650 ms

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

  • Use efficient cache lifetimes

    540 KiB

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

  • Reduce unused CSS

    450 ms · 61 KiB

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

  • Improve image delivery

    439 KiB

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

  • Google Tag Manager adds 323 ms

    323 ms

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

  • alia-prod.com adds 181 ms

    181 ms

    alia-prod.com costs a phone 181 ms of main-thread work and 630 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.

  • 12 long tasks on the main thread

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

  • Legacy JavaScript

    52 KiB

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

  • Minify JavaScript

    36 KiB

    36 KiB could be saved by minifying JavaScript.

  • 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: 15 ms

    15 ms

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

Core Web Vitals

5 to fix100
  • Time to Interactive: 25.9 s

    25.9 s

    The page becomes fully interactive after 25.9 s. Good is under 3.8 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 image “Early Black Friday Sale”.

  • Speed Index: 7.7 s

    7.7 s

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

  • Total Blocking Time: 607 ms

    607 ms

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

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

    +32%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 87 ms to 111 ms 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: 1.4 s

    1.4 s

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

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

    1.0 s

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

  • Largest content (LCP) got 27% faster for real visitors

    -27%

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

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 46.8 MB in 332 requests

    46.8 MB

    Your homepage downloads 46.8 MB in 332 requests on a phone: media 41.4 MB (8), images 2.1 MB (60) and scripts 2.0 MB (103). Under 2 MB keeps phones on slow connections fast.

  • About 13.3 g of CO₂ per visit

    13.27 g

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

2 to fixGoogle 9797
  • 7 text elements with low contrast

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

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 65 images in the HTML carry an alt attribute.

  • 51 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: 51 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10096
  • Structured data has 4 problems

    Structured data found (ItemList, Organization, VideoObject and WebSite) but with 4 problems, for example “VideoObject: contentUrl is not an absolute URL ("//gettrusupps.com/cdn/shop/videos/c/vp/1d9c8acc69d…”.

  • 76 internal links, 10 external

    The homepage links to 76 pages on gettrusupps.com and 10 external pages.

7 checks passed
  • Meta description: 137 characters

    Your meta description is 137 characters: “Plant Based Supplements & Training Programs that are expertly designed and professional grade; with quality and results…”.

  • One H1 headline

    Your main headline reads: “A breakthrough in women’s health”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “TRU Supplements | Plant-Based Protein, Greens & Wellness”.

  • Canonical URL set

    The canonical URL is https://gettrusupps.com/.

  • 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://gettrusupps.com/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,048 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix83
  • 2 pages share a title

    / and https://gettrusupps.com/es all use the title “TRU Supplements | Plant-Based Protein, Greens & Wellness”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://gettrusupps.com/collections/all, https://gettrusupps.com/blogs/news, https://gettrusupps.com/blogs/tru-research-corner, https://gettrusupps.com/pages/rewards-lp and https://gettrusupps.com/pages/bundle-builder have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://gettrusupps.com/collections/all, https://gettrusupps.com/blogs/news, https://gettrusupps.com/blogs/tru-research-corner, https://gettrusupps.com/pages/join-the-family, https://gettrusupps.com/pages/tru-results and https://gettrusupps.com/pages/about-tru-supplements 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 31 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.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    15 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 414 words of copy

    The homepage carries about 414 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP SALE”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “SHOP ALL”, “Apply” and “SHOP SALE”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 9 testimonial or review blocks and 5 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Hotjar.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • 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
  • 7 trackers load before any consent

    7

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

  • 29 cookies set on arrival

    29

    Opening the homepage sets 29 cookies, 1 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.

  • 54 other companies contacted

    Loading the homepage contacts 54 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 gettrusupps.com, 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 16 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Experiment Engine Test Pablo · Klaviyo Email Marketing Sms · Checkmate · Redo · Powerful Form Builder · Impact Com · Reamaze Live Chat Helpdesk · Aftersell · Freegifts · Promo Engine Hpn · cloudfront.net · b-cdn.net · vidjet.io · herokuapp.com · bogos.io · loox.io

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
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Hotjar
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on gettrusupps.com, including 15 speed issues, 1 SEO issue 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