Website review, no card needed
mymotive.com website review
Visit site (opens in a new tab)Reviewed 11 November 202640 issues · 89 checks
This review found 40 issues worth fixing on mymotive.com, 15 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. 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
82B- #30,886 of 108,881 reviewed websitesbeats 66%
- #20,614 of 61,767 online storesbeats 60%
- #19,944 of 56,365 Shopify storesbeats 58%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 105 ms |
| May 30, 2026 | 105 ms |
| Jun 6, 2026 | 120 ms |
| Jun 13, 2026 | 131 ms |
| Jun 20, 2026 | 138 ms |
| Jun 27, 2026 | 144 ms |
| Jul 4, 2026 | 138 ms |
| Jul 11, 2026 | 138 ms |
| Jul 18, 2026 | 138 ms |
| Jul 25, 2026 | 135 ms |
| Aug 1, 2026 | 131 ms |
| Aug 8, 2026 | 129 ms |
| Aug 15, 2026 | 122 ms |
| Aug 22, 2026 | 129 ms |
| Aug 29, 2026 | 122 ms |
| Sep 5, 2026 | 121 ms |
| Sep 12, 2026 | 121 ms |
| Sep 19, 2026 | 120 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 122 ms |
| Oct 10, 2026 | 123 ms |
| Oct 17, 2026 | 122 ms |
| Oct 24, 2026 | 117 ms |
| Oct 31, 2026 | 113 ms |
| Nov 7, 2026 | 110 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
Reduce unused JavaScript
5.2 s · 980 KiBAbout 980 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.2 s faster on a phone.
Use efficient cache lifetimes
3.4 s · 605 KiB39 files are served with short cache lifetimes, so returning visitors download them again (605 KiB).
Render-blocking requests
1.6 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 43
43/100Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.6 s
A phone's processor spends 5.6 s on main-thread work while loading, 3.2 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 (alia-prod.com, Google Tag Manager and Clarity and others), adding 1.8 MB and 1.6 s of main-thread time.
Reduce unused CSS
610 ms · 179 KiBAbout 179 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 610 ms faster on a phone.
alia-prod.com adds 475 ms
475 msalia-prod.com costs a phone 475 ms of main-thread work and 394 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.
Legacy JavaScript
450 ms · 56 KiBPolyfills for old browsers add 56 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 409 ms
409 msGoogle Tag Manager costs a phone 409 ms of main-thread work and 516 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.
Improve image delivery
50 ms · 286 KiB8 images could be 286 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.
Shopify adds 119 ms
119 msShopify costs a phone 119 ms of main-thread work and 377 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.
Duplicated JavaScript
150 ms · 23 KiB23 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 165 ms. During a long task the page ignores taps.
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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 30.8 s
30.8 sYour largest element takes 30.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WHAT IF AGING ISN'T THE REAL PROBLEM? Get 25% Off Your Firs…”.
Time to Interactive: 31.0 s
31.0 sThe page becomes fully interactive after 31.0 s. Good is under 3.8 s.
Speed Index: 11.0 s
11.0 sVisually, the page fills in at 11.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.7 s
4.7 sThe first text or image appears after 4.7 s on a phone. Good is under 1.8 s.
Total Blocking Time: 570 ms
570 msScripts block taps and scrolling for 570 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 105 ms to 110 ms 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.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 111 ms
111 msReal visitors wait 111 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 463 ms
463 msReal visitors wait 463 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 21.4 MB in 500 requests
21.4 MBYour homepage downloads 21.4 MB in 500 requests on a phone: media 16.0 MB (3), scripts 2.6 MB (109) and other files 1.4 MB (303). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
39 KiB1 image is downloaded at several times the size a phone draws it, for example motive-knee-3108064.jpg at 1,024 px wide, shown at 165 px. Resized copies would save about 39 KiB.
About 6.1 g of CO₂ per visit
6.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.06 g of CO₂e: 727.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
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.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (27 elements)
All page content should be contained by landmarks: 27 elements on the page fail this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (226 characters)
Your meta description is 226 characters; Google truncates after about 160, so the end of your pitch is cut.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
46 internal links, 8 external
The homepage links to 46 pages on mymotive.com and 8 external pages.
6 checks passed
One H1 headline
Your main headline reads: “.logo_image { max-height: unset!important; } @media screen and (max-width: 989px) { .logo_image { width: 80px; } } <img…”.
Title: 63 characters
Your title is a healthy 63 characters: “Muscle-Strengthening Therapy for Lasting Relief - Motive Health”.
Canonical URL set
The canonical URL is https://mymotive.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://mymotive.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (949 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://mymotive.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://mymotive.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://mymotive.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages share 2 titles
https://mymotive.com/products/motive-lower-back and https://mymotive.com/collections/knee-pain-treatments/products/motive-lower-back all use the title “Motive Lower Back – Motive Health”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://mymotive.com/customer_authentication/redirect and https://mymotive.com/policies/terms-of-service have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://mymotive.com/products/motive-lower-back and https://mymotive.com/collections/knee-pain-treatments/products/motive-lower-back use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://mymotive.com/collections/knee-pain-treatments/products/knee-pain-relief, whose canonical is https://mymotive.com/products/knee-pain-relief. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
10 pages without an H1
https://mymotive.com/products/knee-pain-relief, https://mymotive.com/collections/knee-pain-treatments, https://mymotive.com/pages/knee-pain-relief-products, https://mymotive.com/pages/the-motive-experience, https://mymotive.com/pages/blogs and https://mymotive.com/pages/about-us and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://mymotive.com/products/motive-lower-back and https://mymotive.com/collections/knee-pain-treatments took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 19 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
3 broken images
3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=97112061&tm=gtm002&Ver=2&mid=3bfbbba8-2aeb-47d8-b6d2-de8436c86f48&bo=1&sid=033edae0dda411f1ae9997fd11a92013&vid=033f1300dda411f1b155635d8ed9cee2&vids=1&msclkid=N&pi=91.
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: the server responded with a status of 402 ()”.
2 checks passed
Tap targets are thumb-sized
22 of 26 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Only about 191 words
The homepage has only about 191 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Lower Back”.
10 calls to action
The homepage has 10 calls to action, for example “Shop Lower Back”, “Shop Knee” and “Learn More”.
Social proof on the page
Social proof on the homepage: 22 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and LinkedIn Insight.
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.
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
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and LinkedIn Insight and 5 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.
36 cookies set on arrival
36Opening the homepage sets 36 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.
58 other companies contacted
Loading the homepage contacts 58 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 mymotive.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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Blocky Fraud Blocker · Convert Experiences · Convert Web Pixel · Aftersell · Countdown Timer · Avada Cookie Bar · Order Value Booster · Booster Kit By Qikify · rechargecdn.com · cloudfront.net · govx.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
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Scottsdale
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on mymotive.com, including 18 speed issues, 2 SEO issues and 2 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.