strollgolf.com website review

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

Google Tag Manager costs a phone 1.0 s of main-thread work and 907 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

A phone's processor spends 4.7 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, TikTok and Klaviyo and others), adding 1.9 MB and 1.8 s of main-thread time.

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

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

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

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

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

About 35 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 71 KiB JavaScript that modern phones do not need.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB JavaScript is shipped twice across bundles.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

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

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 104 ms to 106 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 1.1 s to 1.1 s 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.

Your homepage downloads 4.6 MB in 346 requests on a phone: scripts 2.2 MB (116), images 1.2 MB (29) and other files 800 KiB (151). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example DSCF0369_1.png at 1,200 px wide, shown at 191 px. Resized copies would save about 262 KiB.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

Your title is only 23 characters: “Stroll Golf – 1764 Golf”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 38 pages on strollgolf.com and 4 external pages.

/ and https://1764golf.com/a/gifthero/balance all use the title “1764 Golf”. Search engines can't tell which page to show for a search, so each competes with the others.

https://1764golf.com/collections/all, https://1764golf.com/collections/stroll-shop-all, https://1764golf.com/collections/stroll-new-arrivals, https://1764golf.com/collections/stroll-mens, https://1764golf.com/collections/stroll-womens and https://1764golf.com/collections/stroll-accessories and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://1764golf.com/pages/above-the-links has no <h1> headline, so visitors and search engines get no clear main topic.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).

3 errors were logged to the browser console while the page loaded, for example “customerLoggedIn is not defined”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

The homepage carries about 254 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 21 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 42 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.