pgatour.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

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

• Real-user LCP: 2.6 s

  2.6 s

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

• Real-user INP: 317 ms

  317 ms

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

• Real-user CLS: 0.12

  0.12

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

• Largest content (LCP) got 21% slower for real visitors

  +21%

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

• Page weight: 5.4 MB

  5.4 MB

  Your homepage downloads 5.4 MB on a phone, 284 KiB of it images (5%). Under 2 MB keeps phones on slow connections fast.

• 1 image below the first screen load straight away

  1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  Elements (1)

• About 1.5 g of CO₂ per visit

  1.52 g

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

• 3 tap targets too small

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

  Elements (3)

• ARIA commands must have an accessible name (1 element)

  ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

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

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

  Elements (3)

• Contentinfo landmark should not be contained in another landmark (1 element)

  Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• Document should not have more than one contentinfo landmark (1 element)

  Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

  Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• Zoom is disabled

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

  Elements (1)

• Alternative text of images should not be repeated as text (1 element)

  Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  Elements (1)

• No H1 headline

  There is no <h1>, so neither visitors nor Google get a clear main headline.

• No structured data

  No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

• No social preview image

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

  View source

• No X (Twitter) card tag

  No twitter:card tag. X falls back to Open Graph, which is incomplete here.

• 154 internal links, 11 external

  The homepage links to 154 pages on pgatour.com and 11 external pages.

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

• 6 pages without a meta description

  https://www.pgatour.com/watch, https://www.pgatour.com/players, https://www.pgatour.com/fantasy-betting, https://www.pgatour.com/dp-world-tour-eligibility-rankings, https://www.pgatour.com/tickets and https://www.pgatour.com/shop have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (6)

• 2 pages without an H1

  https://www.pgatour.com/aon-better-decisions and https://www.pgatour.com/pgatour-champions have no <h1> headline, so visitors and search engines get no clear main topic.

• 15 internal pages checked

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

• 56 small tap targets

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

• 4 JavaScript errors while loading

  4 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: t.setTudeMeta is not a function”.

• Thin social proof

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

• 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 form on the homepage

  There is no form on the homepage, so every lead has to click through to another page first.

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

  The homepage carries about 419 words of visible text.

• 11 trackers load before any consent

  11

  Before a visitor clicks anything, the page loads Amazon Ads, Amplitude, Comscore, Criteo and Google Ads and 6 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

• 25 cookies set on arrival

  25

  Opening the homepage sets 25 cookies, 1 of them by other companies (measured from a US location before any click).

• 90 other companies contacted

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