urbangolfperformance.com website review

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

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

Your mobile performance score is 44 (desktop: 71). 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, Shopify and Facebook and others), adding 1.3 MB and 1.4 s of main-thread time.

About 462 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 970 ms faster on a phone.

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

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

Shopify costs a phone 319 ms of main-thread work and 245 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 275 ms of main-thread work and 222 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.

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

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

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

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

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

Desktop scores 71 but mobile only 44. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

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

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

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

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

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

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

Your homepage downloads 8.8 MB in 226 requests on a phone: media 6.3 MB (1), scripts 1.5 MB (94) and other files 673 KiB (83). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

There are 11 <h1> headlines (“”, “BETTER GOLF@media (min-width: 768px) { body #fres…” and “STARTS WITH STRUCTURE@media (min-width: 768px) { …”). One clear main headline is easier for people and search engines.

The homepage links to 34 pages on urbangolfperformance.com and 6 external pages.

https://www.urbangolfperformance.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.urbangolfperformance.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.urbangolfperformance.com/collections/all, https://www.urbangolfperformance.com/customer_authentication/redirect, https://www.urbangolfperformance.com/pages/our-story, https://www.urbangolfperformance.com/blogs/tournament-recaps, https://www.urbangolfperformance.com/blogs/podcasts and https://www.urbangolfperformance.com/pages/events and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.urbangolfperformance.com/customer_authentication/redirect, https://www.urbangolfperformance.com/pages/locations and https://www.urbangolfperformance.com/pages/contact have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.urbangolfperformance.com/pages/contact has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 14 pages linked from your homepage and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 448 words of visible text.

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