Website review, no card needed

troonnorthgolf.com logo

troonnorthgolf.com website review

Visit site (opens in a new tab)Reviewed 26 October 202631 issues · 81 checks

This review found 31 issues worth fixing on troonnorthgolf.com, 14 of them high impact, across 81 checks. The most urgent: improve image delivery. 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.4 s1.0 sMay 9Oct 241.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.3 s
May 16, 20261.3 s
May 23, 20261.2 s
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.2 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
107 ms79 msMay 9Oct 24104 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202682 ms
May 16, 202687 ms
May 23, 202687 ms
May 30, 202688 ms
Jun 6, 202692 ms
Jun 13, 202691 ms
Jun 20, 202694 ms
Jun 27, 202694 ms
Jul 4, 202696 ms
Jul 11, 202696 ms
Jul 18, 202698 ms
Jul 25, 202699 ms
Aug 1, 202695 ms
Aug 8, 202696 ms
Aug 15, 202695 ms
Aug 22, 202694 ms
Aug 29, 202693 ms
Sep 5, 202692 ms
Sep 12, 202693 ms
Sep 19, 202696 ms
Sep 26, 202696 ms
Oct 3, 2026101 ms
Oct 10, 2026103 ms
Oct 17, 2026103 ms
Oct 24, 2026104 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 troonnorthgolf.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. troonnorthgolf.com at 0.4 s0.4 s
  2. troonnorthgolf.com at 0.9 s0.9 s
  3. troonnorthgolf.com at 1.3 s1.3 s
  4. troonnorthgolf.com at 1.7 s1.7 s
  5. troonnorthgolf.com at 2.2 s2.2 s
  6. troonnorthgolf.com at 2.6 s2.6 s
  7. troonnorthgolf.com at 3.0 s3.0 s
  8. troonnorthgolf.com at 3.5 s3.5 s

Speed

7 to fix52
  • Improve image delivery

    12.3 s · 2.7 MB

    8 images could be 2.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 12.3 s faster on a phone.

  • Render-blocking requests

    4.0 s

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

  • Mobile performance score: 52

    52/100

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

  • Reduce unused JavaScript

    300 ms · 475 KiB

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

  • Reduce unused CSS

    630 ms · 107 KiB

    About 107 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 630 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Google Analytics and others), adding 946 KiB and 504 ms of main-thread time.

  • Google Tag Manager adds 299 ms

    299 ms

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

  • Use efficient cache lifetimes

    218 KiB

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

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    35 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 86 but mobile only 52. 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.

2 checks passed
  • Main-thread work: 1.3 s

    A phone's processor spends 1.3 s on main-thread work while loading, 567 ms of it running JavaScript. That is comfortably low.

  • Server response: 12 ms

    12 ms

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

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user CLS: 0.28

    0.28

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

  • Largest Contentful Paint: 18.5 s

    18.5 s

    Your largest element takes 18.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Privacy & Cookies: This site uses cookies. By continuing to…”.

  • Time to Interactive: 21.2 s

    21.2 s

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

  • First Contentful Paint: 4.8 s

    4.8 s

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

  • Speed Index: 6.7 s

    6.7 s

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

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

    +22%

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

  • Cumulative Layout Shift: 0.162

    0.162

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

  • 2 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

5 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 96 ms

    96 ms

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 437 ms

    437 ms

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

  • Total Blocking Time: 109 ms

    109 ms

    Scripts block the page for only 109 ms while loading. Good is under 200 ms.

Images and page weight

4 to fix28
  • Page weight: 4.5 MB in 105 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 105 requests on a phone: images 2.9 MB (16), scripts 1.2 MB (46) and fonts 247 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 1.9 MB together. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    853 KiB

    2 images are downloaded at several times the size a phone draws them, for example signup-home3.jpg at 951 px wide, shown at 195 px. Resized copies would save about 853 KiB.

  • 7 images below the first screen load straight away

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

  • About 1.3 g of CO₂ per visit

    1.28 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

2 to fixGoogle 9697
  • Links must have discernible text (2 elements)

    Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Elements with visible text labels do not have matching accessible names.

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

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 9279
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (28 characters)

    Your title is only 28 characters: “HOME - Troon North Golf Club”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, GolfCourse, ImageObject and WebPage) but with 1 problem, for example “WebPage: keywords is an empty list”.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 118 internal links, 11 external

    The homepage links to 118 pages on troonnorthgolf.com and 11 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Welcome to Troon”.

  • Canonical URL set

    The canonical URL is https://www.troonnorthgolf.com/.

  • 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.troonnorthgolf.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.troonnorthgolf.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (621 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 15 pages without a meta description

    https://www.troonnorthgolf.com/book_tt, https://www.troonnorthgolf.com/category/uncategorized, https://www.troonnorthgolf.com/golf_club_shipping, https://www.troonnorthgolf.com/club_rentals, https://www.troonnorthgolf.com/course and https://www.troonnorthgolf.com/golf_shop and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • 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

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    15 of 18 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    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.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 418 words of copy

    The homepage carries about 418 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “BOOK TEE TIMES” and “SHOP”.

  • 22 calls to action

    The homepage has 22 calls to action, for example “BOOK TEE TIMES”, “SHOP” and “Golf Shop”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Comscore, Google Ads, Google Analytics, Google Tag Manager 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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 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.

  • 18 other companies contacted

    Loading the homepage contacts 18 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 troonnorthgolf.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
React
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on troonnorthgolf.com, including 16 speed issues, 3 SEO issues and 2 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