infinityhoop.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user LCP: 3.1 s

  3.1 s

  Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

• Real-user FCP: 2.5 s

  2.5 s

  Real visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.

• Real-user TTFB: 860 ms

  860 ms

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

• Tap response (INP) held steady for real visitors

  -5%

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

• Largest content (LCP) got 14% slower for real visitors

  +14%

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

• Page weight: 5.7 MB

  5.7 MB

  Your homepage downloads 5.7 MB on a phone, 684 KiB of it images (12%). Under 2 MB keeps phones on slow connections fast.

• About 1.6 g of CO₂ per visit

  1.62 g

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

• Elements must only use permitted ARIA attributes (15 elements)

  Elements must only use permitted ARIA attributes: 15 elements on the page fail this check, rated serious by axe-core.

  Elements (3)

• 2 text elements with low contrast

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

  Elements (2)

• Scrollable region must have keyboard access (2 elements)

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

  Elements (2)

• 6 images without alt text

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

  Elements (3)

• All page content should be contained by landmarks (17 elements)

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

  Elements (3)

• Title is short (13 characters)

  Your title is only 13 characters: “Infinity Hoop”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• 2 H1 headlines

  There are 2 <h1> headlines (“” and “BLACK FRIDAYVIP SALE”). One clear main headline is easier for people and search engines.

  View source

• 157 internal links, 19 external

  The homepage links to 157 pages on infinityhoop.com and 19 external pages.

• 2 pages share a title

  / and /apps/17TRACK all use the title “Infinity Hoop”. Search engines can't tell which page to show for a search, so each competes with the others.

  Elements (2)

• 9 pages without a meta description

  /collections/all, /pages/ugc-creators, /pages/tiktok-shop-creators, /pages/affiliate, /apps/17TRACK and /products/infinity-community and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (8)

• 3 links to non-canonical URLs

  Your homepage links to 3 pages by a URL that isn't their canonical one, for example /apps/17TRACK, whose canonical is /apps/17track. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  Elements (3)

• 9 pages without an H1

  /collections/all, /pages/affiliate, /pages/contact-us, /pages/faq, /products/infinity-flow%E2%84%A2 and /products/infinity-hoop-plus and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

• 2 pages with very little text

  /apps/17TRACK and /products/infinity-hoop-plus have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

• 15 internal pages checked

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

• 15 small tap targets

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

• 4 JavaScript errors while loading

  4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

• Local business without LocalBusiness data

  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.

  View source

• No opening hours

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

• Phone number is not tap-to-call

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

• No map or directions link

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

• About 1,333 words of copy

  The homepage carries about 1,333 words of visible text.

• 9 trackers load before any consent

  9

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 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.

• 47 cookies set on arrival

  47

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

• No consent tool detected

  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.

• 63 other companies contacted

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