Website review, no card needed

trcaa.com logo

trcaa.com website review

Visit site (opens in a new tab)Reviewed 24 October 202626 issues · 70 checks

This review found 26 issues worth fixing on trcaa.com, 8 of them high impact, across 70 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

Real-visitor load time (LCP)75th percentile, phones
2.7 s1.2 sMay 2Oct 172.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.7 s
May 9, 20261.7 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.8 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.0 s
Jul 11, 20261.6 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.8 s
Sep 5, 20261.6 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.6 s
Oct 3, 20262.2 s
Oct 10, 20262.4 s
Oct 17, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
89 ms76 msMay 2Oct 1781 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202679 ms
May 9, 202684 ms
May 16, 202684 ms
May 23, 202687 ms
May 30, 202687 ms
Jun 6, 202681 ms
Jun 13, 202681 ms
Jun 20, 202677 ms
Jun 27, 202677 ms
Jul 4, 202683 ms
Jul 11, 202687 ms
Jul 18, 202687 ms
Jul 25, 202687 ms
Aug 1, 202687 ms
Aug 8, 202682 ms
Aug 15, 202679 ms
Aug 22, 202677 ms
Aug 29, 202678 ms
Sep 5, 202679 ms
Sep 12, 202679 ms
Sep 19, 202682 ms
Sep 26, 202684 ms
Oct 3, 202684 ms
Oct 10, 202683 ms
Oct 17, 202681 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 trcaa.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. trcaa.com at 0.4 s0.4 s
  2. trcaa.com at 0.8 s0.8 s
  3. trcaa.com at 1.1 s1.1 s
  4. trcaa.com at 1.5 s1.5 s
  5. trcaa.com at 1.9 s1.9 s
  6. trcaa.com at 2.3 s2.3 s
  7. trcaa.com at 2.6 s2.6 s
  8. trcaa.com at 3.0 s3.0 s

Speed

3 to fix88
  • Render-blocking requests

    2.5 s

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

  • Mobile performance score: 88

    88/100

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

  • Font display

    300 ms

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

  • Use efficient cache lifetimes

    200 ms · 190 KiB

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

  • Reduce unused CSS

    150 ms · 43 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 257 KiB and 121 ms of main-thread time.

  • Reduce unused JavaScript

    135 KiB

    About 135 KiB of JavaScript is downloaded but never used on this page.

  • 2 long tasks on the main thread

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

  • Improve image delivery

    18 KiB

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

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

2 checks passed
  • Main-thread work: 0.7 s

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

  • Server response: 94 ms

    94 ms

    Your server sent the HTML in 94 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 TTFB: 2.1 s

    2.1 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

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

    +49%

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Largest Contentful Paint: 3.0 s

    3.0 s

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

  • Speed Index: 3.6 s

    3.6 s

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

  • Time to Interactive: 4.1 s

    4.1 s

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

  • Tap response (INP) held steady for real visitors

    +1%

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

4 checks passed
  • Real-user INP: 79 ms

    79 ms

    Real visitors wait 79 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.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 42 ms

    42 ms

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

Images and page weight

100
  • About 0.2 g of CO₂ per visit

    0.19 g

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

4 checks passed
  • Page weight: 684 KiB in 48 requests

    684 KiB

    Your homepage downloads 684 KiB in 48 requests on a phone: scripts 344 KiB (18), fonts 174 KiB (3) and stylesheets 125 KiB (20). That is a lean page.

  • 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

2 to fixGoogle 9397
  • Zoom is disabled

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

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

2 checks passed
  • Every image has alt text

    All 4 images in the HTML carry an alt attribute.

  • 33 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 2 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 9277
  • No meta description

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

  • No H1 headline

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

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 9 internal links, 0 external

    The homepage links to 9 pages on trcaa.com and 0 external pages.

5 checks passed
  • Title: 43 characters

    Your title is a healthy 43 characters: “The Renaissance Club - The Renaissance Club”.

  • Canonical URL set

    The canonical URL is https://trcaa.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://trcaa.com/sitemap_index.xml.

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), 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.

  • No llms.txt

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

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

Other pages

2 to fix90
  • 3 pages without a meta description

    https://trcaa.com/scottish-open, https://trcaa.com/trc-membership and https://trcaa.com/form have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://trcaa.com/scottish-open, https://trcaa.com/trc-membership and https://trcaa.com/form have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://trcaa.com/trc-membership and https://trcaa.com/form 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.

  • 4 internal pages checked

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

5 checks passed
  • Linked pages load

    All 4 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 3 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix42
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

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

  • Only about 7 words

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

2 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 2 cookies set on arrival

    2

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

  • 5 other companies contacted

    Loading the homepage contacts 5 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 trcaa.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

Company

Founded
2008

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on trcaa.com, including 12 speed issues, 3 SEO issues and 4 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