savvytouch.com website review

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.4 s faster on a phone.

Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (cloudfront.net, Shopify and Google CDN and others), adding 2.1 MB and 1.2 s of main-thread time.

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

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

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

cloudfront.net costs a phone 292 ms of main-thread work and 767 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.

Shopify costs a phone 192 ms of main-thread work and 475 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.

Google CDN costs a phone 190 ms of main-thread work and 298 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.

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

Polyfills for old browsers add 36 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

10 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying CSS.

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.

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

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

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

The first text or image appears after 3.6 s on a phone. Good is under 1.8 s.

Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

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

6 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 195 ms to 233 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.2 MB in 462 requests on a phone: scripts 2.9 MB (178), other files 1,014 KiB (199) and images 690 KiB (34). Under 2 MB keeps phones on slow connections fast.

Bottle1.png 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 is downloaded at several times the size a phone draws it, for example Bottle1.png at 1,920 px wide, shown at 589 px. Resized copies would save about 9 KiB.

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

9 tap targets are too small or too close together to hit reliably with a finger.

1 frame has no title, so screen-reader users cannot tell what it contains.

All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

6 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h1 → h6, h1 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.

There are 2 <h1> headlines (“” and “ROCKET FUEL Trusted By 250,000+ Customers”). One clear main headline is easier for people and search engines.

Your meta description is 245 characters; Google truncates after about 160, so the end of your pitch is cut.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 40 pages on savvytouch.com and 6 external pages.

https://savvytouch.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://savvytouch.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://savvytouch.com/collections/all-products and https://savvytouch.com/collections/all-products-a-z all use the title “All Products (A-Z) – Savvy Touch”. Search engines can't tell which page to show for a search, so each competes with the others.

https://savvytouch.com/collections/all, https://savvytouch.com/customer_authentication/redirect, https://savvytouch.com/policies/shipping-policy, https://savvytouch.com/bundle, https://savvytouch.com/pages/rewards and https://savvytouch.com/pages/reviews have no meta description, so Google writes the search snippet from whatever text it finds.

https://savvytouch.com/collections/all-products and https://savvytouch.com/collections/all-products-a-z use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://savvytouch.com/bundle, whose canonical is https://savvytouch.com/apps/bundles/bb/yxvqnbkm9l. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://savvytouch.com/customer_authentication/redirect, https://savvytouch.com/bundle, https://savvytouch.com/collections/all-products, https://savvytouch.com/pages/rewards and https://savvytouch.com/collections/all-products-a-z have no <h1> headline, so visitors and search engines get no clear main topic.

https://savvytouch.com/customer_authentication/redirect, https://savvytouch.com/bundle, https://savvytouch.com/collections/all-products, https://savvytouch.com/pages/rewards, https://savvytouch.com/pages/reviews and https://savvytouch.com/collections/all-products-a-z and 3 others took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 24 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=355001978&Ver=2&mid=2722fde3-6ef1-4a6a-be45-db70af189f06&bo=1&sid=dd5cdaf0dcbf11f185ebc313820b8f95&vid=dd5d03a0dcbf11f19996f9c6676018d5&vids=1&msclkid=N&pi=918639831&l.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “CartItems is not defined”.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 844 words of visible text.

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

Opening the homepage sets 27 cookies (measured from a US location before any click).

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.

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