totencarry.com website review

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

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

3 images could be 81 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.

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

The page has 1,568 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Clarity, Klaviyo and Shopify and others), adding 674 KiB and 261 ms of main-thread time.

About 39 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.

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

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

About 54 KiB of JavaScript is downloaded but never used on this page.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Polyfills for old browsers add 38 KiB JavaScript that modern phones do not need.

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.

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 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

Your homepage downloads 2.1 MB in 250 requests on a phone: other files 851 KiB (112), scripts 652 KiB (99) and images 333 KiB (21). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (10 elements).

Your title is 68 characters, so Google will cut it off around 60: “Tote&Carry® Official Site - New Luggage Sets, Suitcases, Travel Bags”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 3 <h1> headlines (“Tote&Carry”, “ELITE BAGS ATBLACK FRIDAY PRICES.EXCLUSIVE, EVERY…” and “Any month, same lounge.”). One clear main headline is easier for people and search engines.

The homepage links to 171 pages on totencarry.com and 7 external pages.

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.

https://www.totencarry.com/collections/tc-travel-sets, https://www.totencarry.com/collections/luggage-sets, https://www.totencarry.com/collections/rolling-duffle-bags, https://www.totencarry.com/collections/suitcases, https://www.totencarry.com/collections/duffle-bags and https://www.totencarry.com/collections/bundle-and-save-3-pcs-sets and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.totencarry.com/collections/travel-sets, https://www.totencarry.com/collections/tc-travel-sets, https://www.totencarry.com/collections/luggage-sets, https://www.totencarry.com/collections/rolling-duffle-bags, https://www.totencarry.com/collections/suitcases and https://www.totencarry.com/collections/duffle-bags and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://shopify-extension.getredo.com/7036-a115bc9f.css' from origin 'https://www.totencar…”.

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

Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

The homepage carries about 363 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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 37 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 42 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.