teamgazelle.com website review

About 294 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, Accessibe Accessibility Overlay and richpanel.com and others), adding 814 KiB and 571 ms of main-thread time.

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

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

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

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

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

Polyfills for old browsers add 21 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 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.

5 KiB could be saved by minifying JavaScript.

4 KiB could be saved by minifying CSS.

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

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

Visually, the page fills in at 7.0 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.8 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

2 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 78 ms to 75 ms 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.

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

1 button has no accessible name, so screen readers announce just “button”.

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

1 element hidden from screen readers can still receive keyboard focus.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

Main 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 main 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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

2 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.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

Your title is only 12 characters: “Team Gazelle”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Your Essential Guide to Understanding Club Orders” and “Find your Team - PLACE YOUR ORDER”). One clear main headline is easier for people and search engines.

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

Structured data found (Organization) but with 1 problem, for example “Organization: sameAs is not an absolute URL ("https://www.facebook.com/Team Gazelle")”.

The homepage links to 15 pages on teamgazelle.com and 2 external pages.

https://teamgazelle.com/pages/frequently-asked-questions has no meta description, so Google writes the search snippet from whatever text it finds.

https://teamgazelle.com/pages/find-your-club and https://teamgazelle.com/pages/our-story use the same meta description. A description written for each page earns more clicks.

We fetched 8 pages linked from your homepage 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=28001626&Ver=2&mid=7fef88e0-fada-40fc-9f4e-e8c405258250&bo=1&sid=3284be20de9311f19916db772894ffff&vid=3284b590de9311f193120d25dbf563de&vids=1&msclkid=N&pi=918639831&lg.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 298 words of visible text.

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