whygolf.com website review

8 third-party services load with your homepage (Google Tag Manager, Facebook and Intercom and others), adding 7.3 MB and 924 ms of main-thread time.

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

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

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

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

Shopify costs a phone 39 ms of main-thread work and 5.7 MB 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.

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

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

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

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

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

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

Polyfills for old browsers add 31 KiB JavaScript that modern phones do not need.

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.

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

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

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

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

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

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

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

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

Your homepage downloads 9.1 MB in 314 requests on a phone: media 4.1 MB (6), scripts 2.0 MB (103) and images 1.8 MB (44). Under 2 MB keeps phones on slow connections fast.

whygolf-golf-app-hero-mobile.webp 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 is downloaded at several times the size a phone draws it, for example darker_hero.png at 1,800 px wide, shown at 390 px. Resized copies would save about 83 KiB.

3 images (238 KiB) are 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.

1 image further down the page (144 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 2.58 g of CO₂e: 309.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

9 tap targets are too small or too close together to hit reliably with a finger.

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

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

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

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

There are 3 <h1> headlines (“”, “PRACTICE SMARTER.SUCK LESS.” and “WhyGolf creates golf training aids and a mobile a…”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 188 pages on whygolf.com and 28 external pages.

https://whygolf.com/pages/build-your-bundle, https://whygolf.com/pages/quiz-v2 and https://whygolf.com/pages/reviews have no meta description, so Google writes the search snippet from whatever text it finds.

https://whygolf.com/products/putting-thing, https://whygolf.com/products/wrist-x, https://whygolf.com/products/pressure-plate, https://whygolf.com/products/alignment-disc, https://whygolf.com/products/putting-system and https://whygolf.com/products/alignment-disc-lite and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=355011369&tm=gtm002&Ver=2&mid=e970353c-678c-4cea-b4b2-ed56fea12fa2&bo=1&sid=3dc08830dbd111f1b61c55d5fd4eb94b&vid=3dc0bb20dbd111f181c0d922d811bab5&vids=1&msclkid=N&gtm_.

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 975 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 (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.