randa.org website review

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

About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.3 s faster on a phone.

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

About 260 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.3 s faster on a phone.

Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Civic and others), adding 1.2 MB and 729 ms of main-thread time.

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

Google Tag Manager costs a phone 293 ms of main-thread work and 493 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.3 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

11 KiB could be saved by minifying JavaScript.

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

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

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.

Your largest element takes 33.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Some of these cookies are necessary to make our site work, …”.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 9.6 MB in 145 requests on a phone: images 6.0 MB (36), scripts 2.9 MB (58) and stylesheets 327 KiB (18). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example womens-amateur-latin-america-logo.png at 750 px wide, shown at 43 px. Resized copies would save about 241 KiB.

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

Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is only 7 characters: “The R&A”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 5 <h1> headlines (“Asia-Pacific Amateur Championship”, “We work to” and “Global Participation”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Structured data found (ImageObject and Organization) but with 1 problem, for example “Organization: missing name”.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 28 pages on randa.org and 12 external pages.

Your Organization JSON-LD is missing name, url, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.randa.org/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.

https://www.randa.org/rules/rules-hub, https://www.randa.org/news/all-news, https://www.randa.org/championships/event-calendar and https://www.randa.org/pace-of-play/manual/1-introduction have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.randa.org/news/all-news and https://www.randa.org/championships/event-calendar have 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.

https://www.randa.org/about-us took over 3 s to send its HTML from our server.

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

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

Large scripts ship without source maps.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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

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

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

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

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

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