Website review, no card needed

brennangolfsales.com logo

brennangolfsales.com website review

Visit site (opens in a new tab)Reviewed 20 November 202627 issues · 74 checks

This review found 27 issues worth fixing on brennangolfsales.com, 7 of them high impact, across 74 checks. The most urgent: render-blocking requests. 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

Full-page screenshot of brennangolfsales.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. brennangolfsales.com at 2.1 s2.1 s
  2. brennangolfsales.com at 4.1 s4.1 s
  3. brennangolfsales.com at 6.2 s6.2 s
  4. brennangolfsales.com at 8.2 s8.2 s
  5. brennangolfsales.com at 10.3 s10.3 s
  6. brennangolfsales.com at 12.4 s12.4 s
  7. brennangolfsales.com at 14.4 s14.4 s
  8. brennangolfsales.com at 16.5 s16.5 s

Speed

6 to fix64
  • Render-blocking requests

    1.5 s

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

  • Main-thread work: 5.9 s

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

  • Improve image delivery

    500 ms · 648 KiB

    3 images could be 648 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    450 ms · 117 KiB

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

  • Reduce unused CSS

    300 ms · 73 KiB

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

  • Use efficient cache lifetimes

    150 ms · 19 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (19 KiB).

  • 3 third-party services on the page

    3 third-party services load with your homepage (GoDaddy, Google Fonts and secureserver.net), adding 170 KiB and 51 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 62 ms. During a long task the page ignores taps.

  • 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: 4 ms

    4 ms

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

Core Web Vitals

4 to fix66
  • Largest Contentful Paint: 9.0 s

    9.0 s

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

  • Time to Interactive: 9.2 s

    9.2 s

    The page becomes fully interactive after 9.2 s. Good is under 3.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.

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0.061

    0.061

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

  • Total Blocking Time: 12 ms

    12 ms

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

Images and page weight

2 to fix75
  • Page weight: 2.1 MB in 99 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 99 requests on a phone: images 1.2 MB (4), scripts 253 KiB (12) and fonts 248 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    74 KiB

    1 image is downloaded at several times the size a phone draws it, for example Brennan-Blue-Logo-png1.png at 1,558 px wide, shown at 185 px. Resized copies would save about 74 KiB.

  • 1 image in older formats

    1 image (85 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.

  • About 0.6 g of CO₂ per visit

    0.58 g

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

1 checks passed
  • Images load when needed

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

Accessibility

5 to fixGoogle 8293
  • Invalid ARIA attributes

    9 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • All page content should be contained by landmarks (23 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 4 links without text

    4 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 16 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

3 to fixGoogle 9290
  • 2 H1 headlines

    There are 2 <h1> headlines (“Golf Course Accessories, Equipment, and Supplies” and “for Golf Courses Homeowners Field and Grounds Care”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 25 internal links, 5 external

    The homepage links to 25 pages on brennangolfsales.com and 5 external pages.

6 checks passed
  • Meta description: 112 characters

    Your meta description is 112 characters: “Explore the latest golf equipment sales to enhance your game. Find great deals on clubs, balls, and accessories.”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “Golf Equipment Sales: Finding the Best Deals - Brennan Golf Sales”.

  • Canonical URL set

    The canonical URL is https://brennangolfsales.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

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

AI search readiness

100
  • No llms.txt

    There is no https://brennangolfsales.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.

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.

  • Text is in the HTML

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

Other pages

2 to fix70
  • 1 linked page is broken

    Your homepage links to https://brennangolfsales.com/product/inzecto-mosquito-trap, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 page without a meta description

    https://brennangolfsales.com/vendors has no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 internal pages checked

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

5 checks passed
  • 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 6 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8191
  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

  • 2 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix83
  • 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.

  • Thin social proof

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

  • Only about 223 words

    The homepage has only about 223 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

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

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Talk To An Expert”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Contact Us”, “Talk to an expert” and “Learn More”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

  • 4 cookies set on arrival

    4

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

  • 4 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 brennangolfsales.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
jQuery
Analytics
Google Analytics
Hosting
Cloudflare

Company

Headquarters
Atlantic Beach

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on brennangolfsales.com, including 10 speed issues, 3 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