tryinfinity-hoop.com website review

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.3 s faster on a phone.

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

21 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and alia-prod.com and others), adding 1.9 MB and 1.3 s of main-thread time.

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

Google Tag Manager costs a phone 392 ms of main-thread work and 512 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.

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

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

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

vitals.app costs a phone 118 ms of main-thread work and 324 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.

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

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

Polyfills for old browsers add 76 KiB JavaScript that modern phones do not need. 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.

3 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

Your largest element takes 21.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “If your domain uses a suffix other than ".com" (e.g., ".de"…”.

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

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

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

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 18.5 MB in 403 requests on a phone: media 13.0 MB (1), scripts 2.6 MB (114) and images 1.5 MB (45). Under 2 MB keeps phones on slow connections fast.

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

Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Your canonical URL points to infinityhoop.com, not tryinfinity-hoop.com, so Google may credit that host instead.

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

No XML sitemap at https://tryinfinity-hoop.com/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 125 pages on tryinfinity-hoop.com and 51 external pages.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/collections/all, /pages/ugc-creators, /pages/tiktok-shop-creators, /pages/affiliate and /collections/waist-trimmers have no meta description, so Google writes the search snippet from whatever text it finds.

/products/infinity-sculpt%E2%84%A2 and /products/infinity-roller%E2%84%A2 use the same meta description. A description written for each page earns more clicks.

/collections/all, /pages/affiliate, /collections/waist-trimmers and /products/infinity-roller%E2%84%A2 have no <h1> headline, so visitors and search engines get no clear main topic.

/collections/all has 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.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

tryinfinity-hoop.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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.

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

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

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.

tryinfinity-hoop.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

DMARC is set to p=none, so mail pretending to be tryinfinity-hoop.com is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.