Website review, no card needed

69golf.com logo

69golf.com website review

Visit site (opens in a new tab)Reviewed 28 October 202629 issues · 77 checks

This review found 29 issues worth fixing on 69golf.com, 5 of them high impact, across 77 checks. The most urgent: main-thread work: 6.8 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.0 s887 msMay 9Oct 24983 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026951 ms
May 16, 2026949 ms
May 23, 2026937 ms
May 30, 2026919 ms
Jun 6, 2026933 ms
Jun 13, 2026913 ms
Jun 20, 2026912 ms
Jun 27, 2026906 ms
Jul 4, 2026914 ms
Jul 11, 2026954 ms
Jul 18, 2026979 ms
Jul 25, 20261.0 s
Aug 1, 20261.0 s
Aug 8, 20261.0 s
Aug 15, 20261.0 s
Aug 22, 20261.0 s
Aug 29, 20261.0 s
Sep 5, 20261.0 s
Sep 12, 20261.0 s
Sep 19, 2026978 ms
Sep 26, 2026960 ms
Oct 3, 2026963 ms
Oct 10, 2026971 ms
Oct 17, 2026983 ms
Oct 24, 2026983 ms
Real-visitor tap response (INP)75th percentile, phones
137 ms95 msMay 9Oct 24132 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026101 ms
May 16, 2026100 ms
May 23, 2026104 ms
May 30, 2026104 ms
Jun 6, 2026108 ms
Jun 13, 2026112 ms
Jun 20, 2026112 ms
Jun 27, 2026114 ms
Jul 4, 2026120 ms
Jul 11, 2026121 ms
Jul 18, 2026121 ms
Jul 25, 2026121 ms
Aug 1, 2026124 ms
Aug 8, 2026126 ms
Aug 15, 2026127 ms
Aug 22, 2026127 ms
Aug 29, 2026128 ms
Sep 5, 2026127 ms
Sep 12, 2026128 ms
Sep 19, 2026128 ms
Sep 26, 2026125 ms
Oct 3, 2026128 ms
Oct 10, 2026129 ms
Oct 17, 2026129 ms
Oct 24, 2026132 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of 69golf.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 69golf.com at 0.6 s0.6 s
  2. 69golf.com at 1.2 s1.2 s
  3. 69golf.com at 1.8 s1.8 s
  4. 69golf.com at 2.4 s2.4 s
  5. 69golf.com at 3.1 s3.1 s
  6. 69golf.com at 3.7 s3.7 s
  7. 69golf.com at 4.3 s4.3 s
  8. 69golf.com at 4.9 s4.9 s

Speed

8 to fix60
  • Main-thread work: 6.8 s

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

  • Mobile performance score: 60

    60/100

    Your mobile performance score is 60 (desktop: 93). Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Klaviyo and Google CDN and others), adding 1.6 MB and 815 ms of main-thread time.

  • Use efficient cache lifetimes

    600 ms · 156 KiB

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

  • Shopify adds 396 ms

    396 ms

    Shopify costs a phone 396 ms of main-thread work and 994 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 long tasks on the main thread

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

  • Reduce unused JavaScript

    150 ms · 258 KiB

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

  • 2,229 HTML elements

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

  • Legacy JavaScript

    100 ms · 25 KiB

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

  • Improve image delivery

    29 KiB

    1 image could be 29 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    27 KiB

    About 27 KiB of CSS is downloaded but never applied on this page.

  • Phones get a much slower page than desktops

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

  • Chained critical requests

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

  • Forced reflow

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

1 checks passed
  • Server response: 5 ms

    5 ms

    Your server sent the HTML in 5 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix100
  • Time to Interactive: 16.4 s

    16.4 s

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

  • Largest Contentful Paint: 4.7 s

    4.7 s

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

  • Total Blocking Time: 601 ms

    601 ms

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

  • Tap response (INP) got 30% slower for real visitors

    +30%

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

  • Speed Index: 5.8 s

    5.8 s

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

  • 33 images without width and height

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.1 s

    1.1 s

    Real visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 131 ms

    131 ms

    Real visitors wait 131 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 452 ms

    452 ms

    Real visitors wait 452 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.009

    0.009

    The layout barely moves while loading (CLS 0.009, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 3.5 MB in 465 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 465 requests on a phone: other files 1.4 MB (223), scripts 1.3 MB (169) and fonts 300 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    1.00 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

1 to fixGoogle 9798
  • 57 text elements with low contrast

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

2 checks passed
  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

  • 56 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 56 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10090
  • Meta description is long (274 characters)

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

  • One H1 headline

    Your <h1> is empty.

  • 47 internal links, 7 external

    The homepage links to 47 pages on 69golf.com and 7 external pages.

6 checks passed
  • Title: 37 characters

    Your title is a healthy 37 characters: “69 Golf - Home of the 69 Degree Wedge”.

  • Canonical URL set

    The canonical URL is https://www.69golf.com/.

  • Structured data in place

    Structured data found: Organization, ProductGroup and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.69golf.com/sitemap.xml.

AI search readiness

1 to fix88
  • Some text only appears after JavaScript runs

    45%

    The HTML your server sends has 342 of the 763 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • llms.txt published

    The site publishes https://www.69golf.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix86
  • 2 pages share a title

    https://www.69golf.com/products/the-69-degree-wedge and https://www.69golf.com/products/the-69-wedge-black all use the title “69 Degree Wedge – 69 Golf”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages without a meta description

    https://www.69golf.com/collections/wedges, https://www.69golf.com/collections/irons, https://www.69golf.com/collections/woods, https://www.69golf.com/collections/putters, https://www.69golf.com/collections/golf-bag and https://www.69golf.com/collections/69golf-clubs and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.69golf.com/products/the-69-degree-wedge and https://www.69golf.com/products/the-69-wedge-black use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the…”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    78 of 84 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

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

  • No analytics detected

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

  • No direct contact details

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

  • No risk reducer

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

  • About 763 words of copy

    The homepage carries about 763 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop All Products”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Shop All”, “Shop All Products” and “Contact”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    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.

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 36 other companies contacted

    Loading the homepage contacts 36 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at 69golf.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on 69golf.com, including 15 speed issues, 2 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25