zootsports.com website review

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

8 third-party services load with your homepage (amaicdn.com, Shopify and Clarity and others), adding 1.4 MB and 1.4 s of main-thread time.

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

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

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

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

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

amaicdn.com costs a phone 307 ms of main-thread work and 353 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 292 ms of main-thread work and 279 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.

Klaviyo costs a phone 268 ms of main-thread work and 333 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.

Clarity costs a phone 292 ms of main-thread work and 29 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.

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

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

azurefd.net costs a phone 108 ms of main-thread work and 321 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 42 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 104 KiB JavaScript that modern phones do not need.

9 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 50 ms faster on a phone.

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.

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

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

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

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

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

Your largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Two runners jogging outdoors in bright athletic wear, with …”.

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

Your homepage downloads 4.5 MB in 420 requests on a phone: images 1.5 MB (26), scripts 1.4 MB (110) and other files 1.4 MB (264). Under 2 MB keeps phones on slow connections fast.

MobilePRO_9ecc9d09-228c-4a79-9c6b-da3bac924f82.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 is downloaded at several times the size a phone draws it, for example c34ab161-99eb-46da-a213-625cbf40f7e3.jpeg at 971 px wide, shown at 185 px. Resized copies would save about 58 KiB.

1 image (86 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.

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

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

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

The homepage links to 183 pages on zootsports.com and 3 external pages.

https://zootsports.com/collections/rouler, https://zootsports.com/collections/separates-collection, https://zootsports.com/collections/pro-series, https://zootsports.com/collections/elite, https://zootsports.com/collections/new-p1x and https://zootsports.com/collections/limited-edition-racesuits have no meta description, so Google writes the search snippet from whatever text it finds.

https://zootsports.com/collections/mens-triathlon, https://zootsports.com/collections/mens-triathlon-tops and https://zootsports.com/collections/mens-triathlon-shorts use the same meta description. A description written for each page earns more clicks.

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

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

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

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

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