Website review, no card needed

handetouch.com logo

handetouch.com website review

Visit site (opens in a new tab)Reviewed 11 November 202620 issues · 59 checks

This review found 20 issues worth fixing on handetouch.com, 7 of them high impact, across 59 checks. The most urgent: scrollable region must have keyboard access (1 element). 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

Full-page screenshot of handetouch.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. handetouch.com at 0.4 s0.4 s
  2. handetouch.com at 0.8 s0.8 s
  3. handetouch.com at 1.1 s1.1 s
  4. handetouch.com at 1.5 s1.5 s
  5. handetouch.com at 1.9 s1.9 s
  6. handetouch.com at 2.3 s2.3 s
  7. handetouch.com at 2.6 s2.6 s
  8. handetouch.com at 3.0 s3.0 s

Speed

2 to fix77
  • Mobile performance score: 77

    77/100

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

  • Render-blocking requests

    450 ms

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

  • Improve image delivery

    150 ms · 216 KiB

    6 images could be 216 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused JavaScript

    150 ms · 22 KiB

    About 22 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 5 third-party services on the page

    5 third-party services load with your homepage (jQuery CDN, Shopify and buynowbutton.us and others), adding 112 KiB and 75 ms of main-thread time.

  • Use efficient cache lifetimes

    5 KiB

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

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

2 checks passed
  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 246 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

3 to fix70
  • Largest Contentful Paint: 5.2 s

    5.2 s

    Your largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 5.2 s

    5.2 s

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

  • Cumulative Layout Shift: 0.116

    0.116

    The layout shifts by 0.116 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

  • Speed Index: 1.9 s

    1.9 s

    Visually, the page fills in at 1.9 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    your_home.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image in older formats

    1 image (51 KiB) is 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.

  • About 0.4 g of CO₂ per visit

    0.41 g

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

2 checks passed
  • Page weight: 1.4 MB in 159 requests

    1.4 MB

    Your homepage downloads 1.4 MB in 159 requests on a phone: other files 682 KiB (84), images 461 KiB (8) and scripts 210 KiB (38). That is a lean page.

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

1 checks passed
  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 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

3 to fixGoogle 8578
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (12 characters)

    Your title is only 12 characters: “Hand-E Touch”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • One H1 headline

    Your <h1> is empty.

  • 14 internal links, 1 external

    The homepage links to 14 pages on handetouch.com and 1 external page.

5 checks passed
  • Canonical URL set

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

  • 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://handetouch.com/sitemap.xml.

AI search readiness

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

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

  • llms.txt published

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

Other pages

2 to fix90
  • 4 pages without a meta description

    https://handetouch.com/collections/catalog, https://handetouch.com/collections/underpads-1, https://handetouch.com/collections/gloves and https://handetouch.com/collections/underpads have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://handetouch.com/collections/catalog, https://handetouch.com/collections/underpads-1, https://handetouch.com/collections/gloves and https://handetouch.com/collections/underpads have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 internal pages checked

    We fetched 4 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 4 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 4 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 3 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “window.jQuery is not a function”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix43
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 140 words

    The homepage has only about 140 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

Privacy and tracking

  • 7 cookies set on arrival

    7

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

  • 6 other companies contacted

    Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 handetouch.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 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

Bnb App Amazon Buy Now Button

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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 20 issues on handetouch.com, including 5 speed issues, 3 SEO issues and 5 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

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