taylorgear.com website review

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

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

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

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

8 third-party services load with your homepage (ContentSquare, Hubspot and Google Tag Manager and others), adding 1.4 MB and 394 ms of main-thread time.

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

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

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

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

5 images could be 137 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.

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

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.

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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.

Your homepage downloads 3.3 MB in 270 requests on a phone: images 1.3 MB (112), scripts 965 KiB (48) and other files 723 KiB (99). Under 2 MB keeps phones on slow connections fast.

header_01.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 ac.svg at 9,750 px wide, shown at 20 px. Resized copies would save about 121 KiB.

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

Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

11 images have no alt text, which hurts accessibility and image search.

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 85 characters, so Google will cut it off around 60: “Taylor University Campus Store | Official Apparel, Gear & Merch – Taylor Campus Store”.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 170 pages on taylorgear.com and 8 external pages.

https://taylorgear.com/collections/mens-show-all, https://taylorgear.com/collections/mens-tshirts, https://taylorgear.com/collections/mens-sweatshirts, https://taylorgear.com/collections/mens-tops, https://taylorgear.com/collections/mens-bottoms and https://taylorgear.com/collections/mens-professional-wear and 9 others use the same meta description. A description written for each page earns more clicks.

https://taylorgear.com/collections/mens-show-all, https://taylorgear.com/collections/mens-tshirts, https://taylorgear.com/collections/mens-sweatshirts, https://taylorgear.com/collections/mens-tops, https://taylorgear.com/collections/mens-bottoms and https://taylorgear.com/collections/mens-professional-wear and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'fade')”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

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

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, HubSpot and Meta Pixel (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 23 cookies, 8 of them by other companies (measured from a US location before any click).

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