lagshotgolf.com website review

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

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

About 220 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Wistia and Hotjar and others), adding 6.1 MB and 3.2 s of main-thread time.

About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 890 ms faster on a phone.

Wistia costs a phone 756 ms of main-thread work and 3.3 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 799 ms of main-thread work and 707 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.

Hotjar costs a phone 404 ms of main-thread work and 72 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 images could be 388 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

cloudfront.net costs a phone 306 ms of main-thread work and 300 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.

Facebook costs a phone 287 ms of main-thread work and 282 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,671 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

65 KiB could be saved by minifying JavaScript.

17 KiB JavaScript is shipped twice across bundles.

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 CSS.

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

The page becomes fully interactive after 42.2 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 text “What Can Just 12 Swings With this "Blue Shafted Beauty" Do …”.

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

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

The layout shifts by 0.383 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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-10-31, real Chrome visitors' tap response (inp) went from 135 ms to 146 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 2.3 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.0 MB in 438 requests on a phone: scripts 3.5 MB (205), other files 2.0 MB (172) and media 1.9 MB (1). Under 2 MB keeps phones on slow connections fast.

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

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

3 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.

9 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Elements with visible text labels do not have matching accessible names. (1 element).

There are 3 <h1> headlines (“What Can Just 12 Swings With this "Blue Shafted B…”, “What Can Just 12 Swings With this "Blue Shafted B…” and “Just $99.00”). One clear main headline is easier for people and search engines.

Structured data found (Product) but with 1 problem, for example “Product: image is not an absolute URL ("//lagshotgolf.com/cdn/shop/files/golf_club_9_to_112.jpg?cro…”.

5 links have no real href, so search engines can't follow them.

The homepage links to 57 pages on lagshotgolf.com and 9 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://lagshotgolf.com/pages/mens-golf-swing-trainers, https://lagshotgolf.com/pages/ladies-golf-swing-trainers, https://lagshotgolf.com/pages/junior-golf-swing-trainers, https://lagshotgolf.com/pages/combo-golf-swing-trainers, https://lagshotgolf.com/pages/50-off and https://lagshotgolf.com/pages/promotions and 1 other all use the title “Shop Lag Shot Golf Swing Training Aid | #1 Swing Trainer in Golf!”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://lagshotgolf.com/pages/mens-golf-swing-trainers, https://lagshotgolf.com/pages/ladies-golf-swing-trainers, https://lagshotgolf.com/pages/junior-golf-swing-trainers, https://lagshotgolf.com/pages/combo-golf-swing-trainers, https://lagshotgolf.com/pages/50-off and https://lagshotgolf.com/pages/promotions and 1 other use the same meta description. A description written for each page earns more clicks.

https://lagshotgolf.com/pages/pga-teacher-reviews and https://lagshotgolf.com/products/lag-shot-baby-driver-kids-golf-2-4 have 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.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=134605143&Ver=2&mid=00e5c8c5-d92b-4056-8762-84f0e1fdfbf1&bo=1&sid=9d2bc150d94311f184bd7dc53680c7c7&vid=9d2be090d94311f183fc75c6361a02c2&vids=1&msclkid=N&pi=918639831&l.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

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.

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.

The homepage carries about 756 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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

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