Website review, no card needed
mototechgear.com website review
Visit site (opens in a new tab)Reviewed 10 November 202628 issues · 80 checks
This review found 28 issues worth fixing on mototechgear.com, 6 of them high impact, across 80 checks. The most urgent: fails Core Web Vitals for real visitors. 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
86B- #10,841 of 109,350 reviewed websitesbeats 86%
- #6,657 of 61,859 online storesbeats 85%
- #6,459 of 56,401 Shopify storesbeats 84%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.2 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.2 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.2 s |
| Nov 7, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 112 ms |
| May 30, 2026 | 110 ms |
| Jun 6, 2026 | 107 ms |
| Jun 13, 2026 | 109 ms |
| Jun 20, 2026 | 109 ms |
| Jun 27, 2026 | 109 ms |
| Jul 4, 2026 | 112 ms |
| Jul 11, 2026 | 113 ms |
| Jul 18, 2026 | 115 ms |
| Jul 25, 2026 | 115 ms |
| Aug 1, 2026 | 116 ms |
| Aug 8, 2026 | 116 ms |
| Aug 15, 2026 | 113 ms |
| Aug 22, 2026 | 112 ms |
| Aug 29, 2026 | 111 ms |
| Sep 5, 2026 | 111 ms |
| Sep 19, 2026 | 119 ms |
| Sep 26, 2026 | 126 ms |
| Oct 3, 2026 | 129 ms |
| Oct 10, 2026 | 128 ms |
| Oct 17, 2026 | 128 ms |
| Oct 24, 2026 | 128 ms |
| Oct 31, 2026 | 125 ms |
| Nov 7, 2026 | 125 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,052 HTML elements
The page has 3,052 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
800 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Reduce unused JavaScript
264 KiBAbout 264 KiB of JavaScript is downloaded but never used on this page.
bevycommerce.com adds 2 ms
2 msbevycommerce.com costs a phone 2 ms of main-thread work and 429 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.
6 third-party services on the page
6 third-party services load with your homepage (Shopify, aivalabs.com and Cloudflare CDN and others), adding 736 KiB and 325 ms of main-thread time.
Improve image delivery
200 ms · 173 KiB7 images could be 173 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 204 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
30 KiB4 files are served with short cache lifetimes, so returning visitors download them again (30 KiB).
Reduce unused CSS
10 KiBAbout 10 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.
Legacy JavaScript
3 KiBPolyfills for old browsers add 3 KiB JavaScript that modern phones do not need.
1 checks passed
Server response: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 4.7 s
4.7 sYour largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 7.4 s
7.4 sThe page becomes fully interactive after 7.4 s. Good is under 3.8 s.
Real-user TTFB: 868 ms
868 msReal visitors wait 868 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 442 ms
442 msScripts block taps and scrolling for 442 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.164
0.164The layout shifts by 0.164 while loading, so content jumps under the reader's thumb. Good is under 0.1.
15 images without width and height
15 images have no width and height attributes, so the layout jumps as each one loads.
Speed Index: 3.5 s
3.5 sVisually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 112 ms to 125 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 148 ms
148 msReal visitors wait 148 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.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 2.3 MB in 207 requests
2.3 MBYour homepage downloads 2.3 MB in 207 requests on a phone: other files 932 KiB (105), scripts 676 KiB (46) and images 573 KiB (20). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (34 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.67 g of CO₂e: 79.9 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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
27 text elements with low contrast
27 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
2 checks passed
Every image has alt text
All 48 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. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (80 characters)
Your title is 80 characters, so Google will cut it off around 60: “Adventure Motorcycle Accessories & Riding Gear, India - MotoTech – MOTOTECH Gear”.
Meta description is long (205 characters)
Your meta description is 205 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
One H1 headline
Your <h1> is empty.
77 internal links, 10 external
The homepage links to 77 pages on mototechgear.com and 10 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://mototechgear.com/.
Structured data in place
Structured data found: Organization, Store and WebSite.
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://mototechgear.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 (1,880 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://mototechgear.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://mototechgear.com/collections/high-quality-bungee-cords-tie-downs and https://mototechgear.com/collections/bungee-cords-and-tie-downs all use the title “High-Quality Bungee Cords & Tie-Downs for Secure Transport – MOTOTECH…”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://mototechgear.com/collections/high-quality-bungee-cords-tie-downs and https://mototechgear.com/collections/bungee-cords-and-tie-downs 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://mototechgear.com/collections/bungee-cords-and-tie-downs, whose canonical is https://mototechgear.com/collections/high-quality-bungee-cords-tie-downs. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 41 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Every page has a meta description
All 14 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
14 of 14 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 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 1,051 words of copy
The homepage carries about 1,051 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Download MOTOTECH eCatalogs”.
7 calls to action
The homepage has 7 calls to action, for example “Download MOTOTECH eCatalogs”, “SHOP” and “SHOP NOW”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 123 testimonial or review blocks, a star rating and 2 trust badges.
Opening hours shown
Your opening hours are on the homepage.
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
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
18 other companies contacted
Loading the homepage contacts 18 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 mototechgear.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Smart Seo · Bucks · Judge Me Reviews · Doran Shoppable Videos · hulkapps.com · aivalabs.com · amazonaws.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
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Mumbai
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on mototechgear.com, including 14 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.