Website review, no card needed
truwomen.com website review
Visit site (opens in a new tab)Reviewed 9 November 202638 issues · 85 checks
This review found 38 issues worth fixing on truwomen.com, 16 of them high impact, across 85 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76C- #76,562 of 126,458 reviewed websitesbeats 35%
- #48,652 of 70,479 online storesbeats 26%
- #46,032 of 63,977 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 115 ms |
| May 30, 2026 | 113 ms |
| Jun 6, 2026 | 112 ms |
| Jun 13, 2026 | 112 ms |
| Jun 20, 2026 | 113 ms |
| Jun 27, 2026 | 116 ms |
| Jul 4, 2026 | 117 ms |
| Jul 11, 2026 | 120 ms |
| Jul 18, 2026 | 120 ms |
| Jul 25, 2026 | 121 ms |
| Aug 1, 2026 | 121 ms |
| Aug 8, 2026 | 121 ms |
| Aug 15, 2026 | 121 ms |
| Aug 22, 2026 | 122 ms |
| Aug 29, 2026 | 123 ms |
| Sep 5, 2026 | 128 ms |
| Sep 12, 2026 | 130 ms |
| Sep 19, 2026 | 132 ms |
| Sep 26, 2026 | 138 ms |
| Oct 3, 2026 | 142 ms |
| Oct 10, 2026 | 141 ms |
| Oct 17, 2026 | 139 ms |
| Oct 24, 2026 | 139 ms |
| Oct 31, 2026 | 140 ms |
| Nov 7, 2026 | 140 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
Speed
Improve image delivery
1.4 s · 3.0 MB28 images could be 3.0 MB 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.
Reduce unused JavaScript
1.5 s · 996 KiBAbout 996 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
8,893 HTML elements
The page has 8,893 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 6.7 s
A phone's processor spends 6.7 s on main-thread work while loading, 3.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
900 ms · 531 KiB24 files are served with short cache lifetimes, so returning visitors download them again (531 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Curalate and corso.com and others), adding 1.8 MB and 998 ms of main-thread time.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 276 ms
276 msGoogle Tag Manager costs a phone 276 ms of main-thread work and 322 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 279 ms. During a long task the page ignores taps.
pearcommerce.com adds 113 ms
113 mspearcommerce.com costs a phone 113 ms of main-thread work and 460 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
150 ms · 162 KiB162 KiB could be saved by minifying JavaScript.
Render-blocking requests
250 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 250 ms.
Legacy JavaScript
33 KiBPolyfills for old browsers add 33 KiB JavaScript that modern phones do not need.
Reduce unused CSS
31 KiBAbout 31 KiB of CSS is downloaded but never applied on this page.
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: 18 ms
18 msYour server sent the HTML in 18 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 25.6 s
25.6 sYour largest element takes 25.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 35.9 s
35.9 sThe page becomes fully interactive after 35.9 s. Good is under 3.8 s.
Speed Index: 11.1 s
11.1 sVisually, the page fills in at 11.1 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 115 ms to 140 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 549 ms
549 msScripts block taps and scrolling for 549 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 128 ms
128 msReal visitors wait 128 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 546 ms
546 msReal visitors wait 546 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 18.3 MB in 361 requests
18.3 MBYour homepage downloads 18.3 MB in 361 requests on a phone: media 9.1 MB (2), images 5.5 MB (89) and scripts 2.7 MB (126). Under 2 MB keeps phones on slow connections fast.
9 images far larger than shown
1.6 MB9 images are downloaded at several times the size a phone draws them, for example Trubar_Wrapper_Peppermint.png at 4,000 px wide, shown at 176 px. Resized copies would save about 1.6 MB.
11 images below the first screen load straight away
11 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.2 g of CO₂ per visit
5.18 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.18 g of CO₂e: 621.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Unlabelled dropdowns
2 dropdowns have no label.
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.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
Summary elements must have discernible text (1 element)
Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (21 elements)
All page content should be contained by landmarks: 21 elements on the page fail this check, rated moderate by axe-core.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h5 and h1 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 8 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “TRUBAR Protein Bars | Plant-Based, All-Natural Ingredients – TRUBRANDS”.
Meta description is long (199 characters)
Your meta description is 199 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.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
One H1 headline
Your <h1> is empty.
85 internal links, 9 external
The homepage links to 85 pages on truwomen.com and 9 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.trubar.com/.
Structured data in place
Structured data found: Brand, BreadcrumbList, LocalBusiness, Organization and WebPage.
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.
XML sitemap found
Your XML sitemap is reachable at https://www.trubar.com/sitemap.xml.
AI search readiness
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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (577 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.trubar.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 35 found) and read each the way a search engine does.
1 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Best practices
1 broken image
1 image failed to load on a phone, for example https://sp.analytics.yahoo.com/sp.pl?a=10000&d=Mon%2C%2009%20Nov%202026%2011%3A39%3A22%20GMT&n=0&b=TRUBAR%20Protein%20Bars%20%7C%20Plant-Based%2C%20All-Natural%20Ingredients%20%E2%80%93%20TRUBRANDS&.y.
13 small tap targets
13 of 49 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 “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 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 588 words of copy
The homepage carries about 588 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW” and “SHOP TRUBARS”.
10 calls to action
The homepage has 10 calls to action, for example “Shop Now”, “SHOP TRUBARS” and “Shop TRUBAR KiDS!”.
3 short forms
3 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 4 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
29 cookies set on arrival
29Opening the homepage sets 29 cookies, 1 of them by other companies (measured from a US location before any click).
63 other companies contacted
Loading the homepage contacts 63 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 truwomen.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 21 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Blockify Fraud Filter · Bubblehouse For Trubrands · Pm779l583 Opensend · Triplewhale · Hulk Form Builder · Wsh Wholesale Pricing · Geoip Country Redirect · Klaviyo Email Marketing Sms · Judge Me Reviews · Xo Insert Code · Gorgias Live Chat Helpdesk · Microsoft Clarity · Region Restrictions · Applovin Shop Integration · Cartbite · cloudfront.net · bazaarvoice.com · corso.com · curalate.com · socialsnowball.io · zigpoll.com
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
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Denver
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on truwomen.com, including 15 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.