puntersgolf.com website review

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

YouTube costs a phone 1.3 s of main-thread work and 2.9 MB 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.

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

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

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

11 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.

8 third-party services load with your homepage (YouTube, Shopify and Klaviyo and others), adding 5.9 MB and 1.8 s of main-thread time.

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

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

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

Klaviyo costs a phone 114 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.

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

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

Polyfills for old browsers add 30 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.

3 KiB could be saved by minifying JavaScript.

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

Your largest element takes 39.8 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 42.7 s. Good is under 3.8 s.

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

Scripts block taps and scrolling for 465 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.

Your homepage downloads 24.3 MB in 303 requests on a phone: media 13.5 MB (4), images 5.1 MB (37) and scripts 3.9 MB (101). Under 2 MB keeps phones on slow connections fast.

12 images are downloaded at several times the size a phone draws them, for example menu-balls.jpg at 3,648 px wide, shown at 60 px. Resized copies would save about 3.5 MB.

menu-balls.jpg weighs 1.5 MB. On a phone connection a single image that size takes seconds.

5 images further down the page (1.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

mobile-banner.png 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 (197 KiB) 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.

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

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

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

1 element hidden from screen readers can still receive keyboard focus.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

1 form field has 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.

Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.

Your title is only 12 characters: “Punters Golf”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 68 pages on puntersgolf.com and 1 external page.

https://puntersgolf.us/collections/sale and https://puntersgolf.us/collections/best-sellers all use the title “Best Sellers– Punters Golf”. Search engines can't tell which page to show for a search, so each competes with the others.

https://puntersgolf.us/products/pulse-launch-monitor, https://puntersgolf.us/products/p1-irons, https://puntersgolf.us/products/p1-irons-copy, https://puntersgolf.us/collections/golf-clubs, https://puntersgolf.us/collections/clothing and https://puntersgolf.us/collections/sale and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://puntersgolf.us/products/pulse-launch-monitor, whose canonical is https://puntersgolf.us/products/launch-monitor. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://puntersgolf.us/collections/golf-clubs, https://puntersgolf.us/collections/clothing, https://puntersgolf.us/collections/sale, https://puntersgolf.us/collections/hats, https://puntersgolf.us/collections/accessories and https://puntersgolf.us/collections/all 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 22 found) and read each the way a search engine does.

2 images failed to load on a phone, for example https://puntersgolf.us/cdn/shop/files/en.svg?v=5692.

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

5 errors were logged to the browser console while the page loaded, for example “Invalid left-hand side in assignment”.

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

Social proof on the homepage: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 425 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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 18 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 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.