Website review, no card needed

garcesgroup.com logo

garcesgroup.com website review

Visit site (opens in a new tab)Reviewed 29 October 202638 issues · 76 checks

This review found 38 issues worth fixing on garcesgroup.com, 13 of them high impact, across 76 checks. The most urgent: use efficient cache lifetimes. 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 garcesgroup.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. garcesgroup.com at 0.4 s0.4 s
  2. garcesgroup.com at 0.9 s0.9 s
  3. garcesgroup.com at 1.3 s1.3 s
  4. garcesgroup.com at 1.8 s1.8 s
  5. garcesgroup.com at 2.2 s2.2 s
  6. garcesgroup.com at 2.7 s2.7 s
  7. garcesgroup.com at 3.1 s3.1 s
  8. garcesgroup.com at 3.6 s3.6 s

Speed

7 to fix62
  • Use efficient cache lifetimes

    24.9 s · 4.4 MB

    27 files are served with short cache lifetimes, so returning visitors download them again (4.4 MB).

  • Improve image delivery

    18.1 s · 3.4 MB

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

  • Render-blocking requests

    3.0 s

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

  • Mobile performance score: 62

    62/100

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

  • Reduce unused JavaScript

    600 ms · 61 KiB

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

  • Reduce unused CSS

    310 ms · 83 KiB

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

  • Adobe TypeKit adds 7 ms

    7 ms

    Adobe TypeKit costs a phone 7 ms of main-thread work and 830 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.

  • 4 third-party services on the page

    4 third-party services load with your homepage (FontAwesome CDN, Google Analytics and Adobe TypeKit and others), adding 966 KiB and 55 ms of main-thread time.

  • Font display

    100 ms

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

  • Minify CSS

    31 KiB

    31 KiB could be saved by minifying CSS.

  • Document request latency

    17 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

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

  • Server response: 47 ms

    47 ms

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

Core Web Vitals

4 to fix67
  • Largest Contentful Paint: 31.1 s

    31.1 s

    Your largest element takes 31.1 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: 31.1 s

    31.1 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Speed Index: 6.2 s

    6.2 s

    Visually, the page fills in at 6.2 s (Speed Index). Good is under 3.4 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.01

    0.01

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

1 to fix70
  • Page weight: 5.4 MB in 59 requests

    5.4 MB

    Your homepage downloads 5.4 MB in 59 requests on a phone: images 4.1 MB (10), fonts 898 KiB (25) and scripts 255 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 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.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • 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

6 to fixGoogle 8389
  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

    All page content should be contained by landmarks: 2 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.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 8 links without text

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

  • Headings should not be empty (8 elements)

    Headings should not be empty: 8 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 4 images in the HTML carry an alt attribute.

  • 25 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 31 WCAG 2.2 A/AA and best-practice rules on the phone render: 25 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

8 to fixGoogle 8357
  • 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.

  • Title is short (13 characters)

    Your title is only 13 characters: “GARCES - Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 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 (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://garcesgroup.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at garcesgroup.com/robots.txt, the first file search crawlers ask for.

  • 2 links with vague text

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

  • No X (Twitter) card tag

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

  • 45 internal links, 12 external

    The homepage links to 45 pages on garcesgroup.com and 12 external pages.

1 checks passed
  • Canonical URL set

    The canonical URL is http://garcesgroup.com/.

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://garcesgroup.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

5 to fix63
  • 2 pages without a title

    https://garcesgroup.com/grgforms/view.php and https://garcesgroup.com/recipes have no <title>, so Google invents the link text in results.

  • 2 pages share a title

    / and https://garcesgroup.com/home all use the title “GARCES - Home”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://garcesgroup.com/garces-events, https://garcesgroup.com/gift-and-loyalty, https://garcesgroup.com/grgforms/view.php, https://garcesgroup.com/happenings, https://garcesgroup.com/employment and https://garcesgroup.com/chef-garces and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://garcesgroup.com/gift-and-loyalty, whose canonical is https://garcesgroup.com/rewards. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 13 pages without an H1

    https://garcesgroup.com/garces-events, https://garcesgroup.com/grgforms/view.php, https://garcesgroup.com/happenings, https://garcesgroup.com/employment, https://garcesgroup.com/chef-garces and https://garcesgroup.com/about and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://garcesgroup.com/grgforms/view.php and https://garcesgroup.com/press-contacts 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.

  • 1 page slow to respond

    https://garcesgroup.com/accolades took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 7387
  • 3 small tap targets

    3 of 9 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 “Mixed Content: The page at 'https://garcesgroup.com/' was loaded over HTTPS, but requested an insecure script 'http://g…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • No social proof

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

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

  • Only about 216 words

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

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “BOOK AN EVENT”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Book an Event”, “contact us” and “Join The Family”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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 garcesgroup.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
Bolt
Framework
jQuery
Analytics
Google Analytics
Hosting
Inmotion

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on garcesgroup.com, including 11 speed issues, 8 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