tuckgear.ca website review

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

2 third-party services load with your homepage (Shopify and shop.app), adding 28.9 MB and 18 ms of main-thread time.

Shopify costs a phone 18 ms of main-thread work and 28.9 MB 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.

7 images could be 203 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

About 22 KiB of CSS is downloaded but never applied on this page.

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

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

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

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

13 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 87 ms to 85 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 30.6 MB in 168 requests on a phone: media 28.9 MB (4), other files 841 KiB (116) and images 566 KiB (11). Under 2 MB keeps phones on slow connections fast.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

Your title is only 26 characters: “Tuck Gear Shop – Tuck gear”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your meta description is only 40 characters: “Custom school and team clothing company.”. 70 to 160 characters is enough to sell the click.

The homepage links to 791 pages on tuckgear.ca and 2 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.tuckgear.ca/pages/schools, https://www.tuckgear.ca/pages/a-lorne-cassidy-elementary-school, https://www.tuckgear.ca/pages/agincourt-road-public-school, https://www.tuckgear.ca/pages/all-saints-high-school and https://www.tuckgear.ca/pages/briargreen-public-school have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.tuckgear.ca/collections/a-lorne-cassidy-elementary-school, https://www.tuckgear.ca/collections/agincourt-road-public-school-spiritwear, https://www.tuckgear.ca/collections/agincourt-class-of and https://www.tuckgear.ca/collections/all-saints-theather use the same meta description. A description written for each page earns more clicks.

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

1 image failed to load on a phone, for example https://www.tuckgear.ca/.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

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 300 words of visible text.

Opening the homepage sets 6 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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.