tourstriker.com website review

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

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

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

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

8 third-party services load with your homepage (loox.io, Clarity and Klaviyo and others), adding 1.9 MB and 618 ms of main-thread time.

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

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

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

loox.io costs a phone 223 ms of main-thread work and 587 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.

Vimeo costs a phone 81 ms of main-thread work and 535 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 58 ms of main-thread work and 463 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.

Polyfills for old browsers add 57 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

About 50 KiB of CSS is downloaded but never applied on this page.

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.

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

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

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

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

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

Your homepage downloads 6.2 MB in 299 requests on a phone: images 3.6 MB (59), scripts 1.3 MB (115) and other files 660 KiB (91). Under 2 MB keeps phones on slow connections fast.

antiswingdesign_dd1320c7-9c24-4d8b-b461-d5de5218f743.gif weighs 1.4 MB. On a phone connection a single image that size takes seconds.

1 image (1.4 MB) 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.

swing_trainer_hero_mobile.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 further down the page (32 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

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

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

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

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

Your title is 74 characters, so Google will cut it off around 60: “Tour Striker Golf Training Aids and Online Golf Academy – Tour Striker Inc”.

There are 2 <h1> headlines (“” and “Smart Ball Sleeve Training System”). One clear main headline is easier for people and search engines.

Structured data found (Organization, Product and WebSite) but with 6 problems, for example “Organization: sameAs is not an absolute URL ("#")”.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 219 pages on tourstriker.com and 12 external pages.

https://www.tourstriker.com/collections/best-sellers has no meta description, so Google writes the search snippet from whatever text it finds.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

4 errors were logged to the browser console while the page loaded, for example “[object ProgressEvent]”.

Chrome logged issues while loading the page (“Cookie”).

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 shows no opening hours. If customers visit or call, show when.

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

The homepage carries about 886 words of visible text.

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

Opening the homepage sets 36 cookies, 3 of them by other companies (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 54 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.